Requirements

ESBO_SWAnfSpez_Anl_Sub026: 2014-03-12T10:00:39 version: 1.0 (Rev_valid_G)
ESBO_SWAnfSpez_Anl_Sub040: 2014-03-11T12:52:10 version: 4.0 (Rev_valid_G)	

SUB026

Chapter 3

TEST APPROACH:
Note: The track description is verified via a mode independent test interface if not stated otherwise.
		

Chapter 3.4

#REQ-UNISIG-SUB026-1000#REF# 3.4.1.1
A balise group shall consist of between one and eight balises.
#TEST-VAL-SUB026-3404#REF# EET CFX00035144 Repeated reception of same balise of a BG, last balise of BG found again after more than 1m
#TEST-VAL-SUB026-3405#REF# EET CFX00035144 Repeated reception of same balise of a BG, last balise of BG found again after less than 1m
#TEST-VAL-SUB026-5692#REF# EET CFX00035144 Repeated reception of same balise of a BG, last balise of BG found only once
#TEST-VAL-SUB026-3000#REF# BVA basic function Fahrt ueber Single BG, Fahrt ueber 8er BG

#REQ-UNISIG-SUB026-0003#REF# 3.4.2.2.1
The origin of the co-ordinate system for each balise group shall be given by the balise number 1 (called location reference) in the balise
group.
#TEST-VAL-SUB026-3B01#REF# FCT basic function Balise Nr.1 ist location reference

#REQ-UNISIG-SUB026-0396#REF# 3.4.2.2.2
The nominal direction of each balise group is defined by increasing internal balise numbers.
see following figure 1
#DSC-UNISIG-SUB026-000688#REF#

Figure 1: Orientation of the balise group
#TEST-VAL-SUB026-3002#REF# FCT basic function Direction identification based on single balise group and multiple balise group

#REQ-UNISIG-SUB026-0397#REF# 3.4.2.3.2.2
For balise groups consisting of a single balise, the information "direction with which the linked balise group will be passed over"
received from a previous balise group shall assign a co-ordinate system to the balise.
see following figure 2
#DSC-UNISIG-SUB026-000702#REF#

Figure 2: Assignment of a co-ordinate system to a single balise group by linking
#TEST-VAL-SUB026-5693#REF# FCT basic function Assignment of co-ordinate system, reference for linking data single balise group two balise group

#REQ-UNISIG-SUB026-0005:01#REF# 3.4.2.3.3.1
If the ERTMS/ETCS on-board equipment cannot evaluate the orientation of the last balise group detected, being a single balise group, i.e. no
linking information is available to identify the orientation of the co-ordinate system of this single balise group, the ERTMS/ETCS on-board
equipment shall report its position by means of a position report based on two balise groups reporting the train position in reference to the
LRBG and the “previous LRBG”, if any.
TEST APPROACH:
The following aspects have been identified:
1) P0 - LRBG unknown
2) P0 - LRBG known
3) P0 - single balise group after M45
4) P1 - no previous BG
5) P1 - previous BG N_TOTAL = 0
6) P1 - previous BG N_TOTAL > 0
#TEST-VAL-SUB026-3338#REF# FCT 1, 2 , CFX00034867 position report, if packet 58 was received with reference LRBG_unknown (without location dependency)
#TEST-VAL-SUB026-3668#REF# FCT 3 Train Location Information - Assignment of coordinate system
#TEST-VAL-SUB026-3005#REF# FCT 4, 5 Position Report for single balise groups
#TEST-VAL-SUB026-3281#REF# FCT 6 PR parameter - after passing BG (N_TOTAL /=0) and BG (N_TOTAL =0)
#TEST-VAL-SUB026-8288#REF# EET error expectation Orientation of single balise group

#REQ-UNISIG-SUB026-3216#REF# 3.4.2.3.3.2
When a single balise group is detected and the previous LRBG is known, the position report based on two balise groups shall use as direction
reference a move from the “previous LRBG” towards this single balise group (being the new LRBG): directional information in the position report
pointing in the same direction as the direction reference shall be reported as “nominal”, otherwise as “reverse”.
realised by: #REQ-UNISIG-SUB026-3241:01#REF#

#REQ-UNISIG-SUB026-3217#REF# 3.4.2.3.3.3
If the “previous LRBG “ is not known, the “previous LRBG” and all directional information of the position report based on two balise groups
shall be reported as “unknown”.
realised by: #REQ-UNISIG-SUB026-3241:01#REF#
realised by: #REQ-UNISIG-SUB026-3243#REF#

#REQ-UNISIG-SUB026-3218#REF# 3.4.2.3.3.4
If a new single balise group (BG2), different from the current LRBG (BG1), becomes LRBG while the running direction of the train is opposite to
the running direction when this current LRBG (BG1) was last passed, the “previous LRBG” and all directional information of the position report
based on two balise groups shall be reported as “unknown” (see Figure 2a).
see following figure 2a
#DSC-UNISIG-SUB026-000718#REF#

Figure 2a: Position report based on two balise groups versus train running direction
realised by: #REQ-UNISIG-SUB026-3241:01#REF#
realised by: #REQ-UNISIG-SUB026-3243#REF#

#REQ-UNISIG-SUB026-3242:01#REF# zu.3.4.2.3.3.4 #ANA-UNISIG-PR-0004#REF#
Wenn die previous LRBG sowie die "direction information" aufgrund einer Änderung der Fahrtrichtung zwischen previous und aktueller
LRBG auf UNKNOWN gesetzt wurde, so sind auch bei allen folgenden Positionreports mit diesen beiden LRBGs die previous LRBG sowie "direction
information" auf UNKNOWN zu belassen.
#TEST-VAL-SUB026-4517#REF# FCT basic function previous LRBG and all PR directional information set to unknown after passing new BG with different running direction - orientation changed

#REQ-UNISIG-SUB026-3219#REF# 3.4.2.3.3.5
If a single balise group, being the LRBG, is detected again, the LRBG and the “previous LRBG” of the position report based on two balise groups
shall remain unchanged.
#TEST-VAL-SUB026-4497#REF# FCT train orientation changed SR/L1 - acceptance of message 45: Assignment of coordinate system
#TEST-VAL-SUB026-4498#REF# FCT train orientation unchanged NL/L2 - acceptance of message 45: Assignment of coordinate system

#REQ-UNISIG-SUB026-3220#REF# 3.4.2.3.3.6
The assignment of a co-ordinate system received from the RBC shall identify the balise group for which the assignment is given, and assign a
balise group orientation “nominal” or “reverse” to this balise group
define the use of message 42
#TEST-VAL-SUB026-7525#REF# FCT basic function Variablentest Q_ORIENTATION

#REQ-UNISIG-SUB026-3221#REF# 3.4.2.3.3.7
For single balise groups reported as LRBG and stored according to 3.6.2.2.2c, awaiting an assignment of a co-ordinate system, the ERTMS/ETCS
on-board equipment shall be able to discriminate if a single balise has been reported more than once and with different “previous LRBGs” to the
RBC.
#TEST-VAL-SUB026-4497#REF# FCT train orientation changed SR/L1 - acceptance of message 45: Assignment of coordinate system
#TEST-VAL-SUB026-4498#REF# FCT train orientation unchanged NL/L2 - acceptance of message 45: Assignment of coordinate system

#REQ-UNISIG-SUB026-3222#REF# 3.4.2.3.3.8 #REQ-UNISIG-SUB026-3223#REF#
A co-ordinate system assignment received from trackside shall be rejected by the ERTMS/ETCS on-board equipment if the referred LRBG is memorised
(see 3.6.2.2.2c) to have been reported more than once and with different “previous LRBGs”.
#TEST-VAL-SUB026-4497#REF# FCT train orientation changed SR/L1 - acceptance of message 45: Assignment of coordinate system
#TEST-VAL-SUB026-4498#REF# FCT train orientation unchanged NL/L2 - acceptance of message 45: Assignment of coordinate system

#REQ-UNISIG-SUB026-000738#REF# 3.4.2.4.1
A group of two balises duplicating each other shall be treated as a single balise group in case where only one balise is correctly read.
Rel. 8.0:
changed from Prosa to DEF
#TEST-VAL-SUB026-5745#REF# FCT basic function A group of two balises duplicating each other treated as a single BG in case where only one balise is correctly read

#REQ-DESIGN-CR-0372#REF# 3.4.4.2.1.1
"Linking information is used" shall be interpreted as when balise group(s) are announced and the minimum safe antenna position has not
yet passed the expectation window of the furthest announced balise group.
note for validation:
when the last bg of the linking information is read the state "no linking information available" is reached.
#TEST-VAL-SUB026-3888#REF# FCT RX P5 announced position not passed Validity of un-announced BG starts after reading of last expected BG of pkt5
#TEST-VAL-SUB026-3970#REF# FCT RX P5 announced position passed Applicability of Linking information

#REQ-DESIGN-CR-0610#REF# 3.4.4.2.2
Instead of the identity of a linked balise group it shall be possible to identify a following linked balise group as unknown but containing
repositioning information
realizes through 3.4.4.4.2.1
realised by: #REQ-UNISIG-SUB026-3000#REF#

#REQ-UNISIG-SUB026-0009#REF# 3.4.4.4.1
When no linking information is used on-board, all balise groups shall be taken into account.
#TEST-VAL-SUB026-3010#REF# FCT basic function ohne Linking-Info werden alle BGs akzeptiert

#REQ-UNISIG-SUB026-0410#REF# 3.4.4.4.2
When linking information is used on-board, only balise groups marked as linked and included in the linking information and balise groups marked
as unlinked shall be taken into account.
#TEST-VAL-SUB026-3313#REF# EET CFX00030893 angekündigte BG mit QLINK=0 wird akzeptiert
#TEST-VAL-SUB026-3011#REF# FCT basic function mit Linking-Info werden unlinked und linked+in_Info BGs akzeptiert
#TEST-VAL-SUB026-3009#REF# EET error expectation Single balise group Q_LINK 0/1, linking information available on board

#REQ-UNISIG-SUB026-3000#REF# 3.4.4.4.2.1 #REQ-DESIGN-CR-0610#REF#
When linking information is used on-board and the expected balise group is referred in the linking information with a balise group with ID
“unknown”, a balise group marked as linked shall only be taken into account if:
a)	the on-board equipment can determine the orientation of the linked balise group by information from the balise group itself (therefore
excluding for example single balise groups), AND
b)	the balise group contains repositioning information valid for the train orientation, AND
c)	the balise group is crossed with the direction announced in the linking information.
TEST APPROACH:
The following aspects have been identified:
1) Linking information accepted (BG marked as linked and conditions a, b, c fulfilled)
2) Linking information rejected
2.1) condition a) not fulfilled
2.2) condition b) not fulfilled
2.3) condition c) not fulfilled
2.4) condtitions a), b), c) fulfilled but BG marked as unlinked
#TEST-VAL-SUB026-3656#REF# FCT 1, 2.4 lnk repo BG announced, pass BG with repo info valid but Q_LINK=0 and valid repo BG
#TEST-VAL-SUB026-3641#REF# FCT 2.1, 2.2 , error expectation lnk repo BG announced, pass BG with repo info not valid for train orientation, valid repo BG and single balise with repo info
#TEST-VAL-SUB026-3643#REF# FCT 2.3 lnk repo BG announced, pass BG with repo info not valid for train orientation, repo BG crossing dir /= lnk info and valid repo BG
#TEST-VAL-SUB026-3097#REF# EET error expectation Aufwertung MA durch angekündigtes Pkt 16 - unangekündigtes Pkt 16 wird verworfen
#TEST-VAL-SUB026-3642#REF# EET error expectation lnk repo BG announced, pass single balise with repo info, valid repo BG and BG without repo info
#TEST-VAL-SUB026-5288#REF# EET error expectation Two balise BG, balise duplicated, BG with announced reposition information

#REQ-UNISIG-SUB026-0411#REF# 3.4.4.4.3 #REQ-UNISIG-SUB026-0106#REF#
#REQ-DESIGN-CR-0586#REF#
The on-board equipment shall accept a balise group marked as linked and included in the linking information (i.e. the balise giving the location
reference) from
  when the max safe front end of the train has passed the first possible location of the balise group
  the min safe front end of the train has passed the last possible location of the balise group
#TEST-VAL-SUB026-3012#REF# FCT basic function Acceptance of announced linked BGs according to the expectation window
#TEST-VAL-SUB026-3013#REF# EET error expectation Ankündigung auf Repositioning Balise
#TEST-VAL-SUB026-3859#REF# EET error expectation BG position outside expectation window

#REQ-UNISIG-SUB026-0412#REF# 3.4.4.4.4
In case of a balise group containing repositioning information, the first possible location shall start from the previously linked balise group.
#TEST-VAL-SUB026-3680#REF# FCT basic function first possible location for repo BG start from the previously linked balise group

#REQ-DESIGN-CR-0583#REF# 3.4.4.4.5
The on-board equipment shall expect balise groups one by one (i.e., it shall supervise only one expectation window at a time) according to the
order given by linking information.
#TEST-VAL-SUB026-3859#REF# FCT basic function BG position outside expectation window

#REQ-DESIGN-CR-0584#REF# 3.4.4.4.6
The ERTMS/ETCS on-board equipment shall stop expecting a balise group and shall expect the next one announced in the linking information (if
any) when:
a)	the balise group is found inside its expectation window
b)	a linking consistency error is found, see 3.16.2.3.1
#TEST-VAL-SUB026-5694#REF# FCT a) OBU stops to expect a already found BG
#TEST-VAL-SUB026-3859#REF# FCT b) BG position outside expectation window

#REQ-DESIGN-CR-0585#REF# 3.4.4.4.6.1
Linking consistency error due to early reception of balise group expected later (see 3.16.2.3.1 c)): if the balise group found is the next one
announced in the linking information, the ERTMS/ETCS on-board equipment shall check its linking consistency and apply again clause 3.4.4.4.6,
i.e. it will immediately expect the further next balise group announced in the linking information.
#TEST-VAL-SUB026-3311#REF# FCT Q_LINKREACTION !=2 BG not found in announced order
#TEST-VAL-SUB026-3859#REF# FCT Q_LINKREACTION=2 BG position outside expectation window

Chapter 3.5

#REQ-UNISIG-SUB026-0010#REF# 3.5.2.1
Each communication session managed by an entity shall allow the exchange of data with only one other entity.
is realized in SS SALSA outside ASW

#REQ-UNISIG-SUB026-000853#REF# 3.5.3.4
The on-board shall establish a communication session
a)	At Start of Mission (only if level 2 or 3).
b)	If ordered from trackside.
c)	If a mode change, not considered as an End of Mission, has to be reported to the RBC (only if level 2 or 3)
d)	If the driver has manually changed the level to 2 or 3
e)	When the train front reaches the end of an announced radio hole
f)	When the previous communication session is considered as terminated due to loss of safe radio connection (refer to 3.5.4.2.1)
g)	When a Start of Mission procedure, during which no communication session could be established, is completed in level 2 or 3
realised by: #REQ-DESIGN-CR-0363:01#REF#
realised by: #REQ-UNISIG-SUB026-3417#REF#
realised by: #REQ-UNISIG-SUB026-3062:01#REF#
realised by: #REQ-UNISIG-SUB026-3063:01#REF#
realised by: #REQ-UNISIG-SUB026-3065:01#REF#
realised by: #REQ-UNISIG-SUB026-010271#REF#
realised by: #REQ-UNISIG-SUB026-010272#REF#

#REQ-DESIGN-CR-0363:01#REF# 3.5.3.4.a) #REQ-UNISIG-SUB026-000853#REF#
#REQ-UNISIG-SUB026-000862#REF#
The on-board shall establish a communication session at Start of Mission (only if level 2 or 3).

Exception:
The on-board shall not establish a new communication session with a RBC in case a communication session is currently being established or is
already established with this RBC.
UNISIG clarification:
an exception is necessary, if the session is already established.
realised by: #REQ-DESIGN-CR-0536:03#REF#

#REQ-UNISIG-SUB026-3417#REF# 3.5.3.4.b) #REQ-UNISIG-SUB026-000853#REF#
#REQ-UNISIG-SUB026-000862#REF#
The on-board shall establish a communication session if ordered from the trackside.

Exception:
The on-board shall not establish a new communication session with a RBC/RIU in case a communication session is currently being established or is
already established with this RBC/RIU.
UNISIG clarification:
The former exception "unless currently being established or already established with the same RBC/ RIU" is furthermore valid.
TEST APPROACH:
The following aspects have been identified:
1) Type of order
1.1) P42
1.2) P131
2) Dependency on the status of the communication session
2.1) no session established
2.2) session already established
2.3) session being established
#TEST-VAL-SUB026-3731#REF# FCT 1.1 reception of pkt45/42 (new network and old RBC) while OBU equipment already in session with old RBC
#TEST-VAL-SUB026-3582#REF# FCT 1.2 , CFX00038025 A.3.4.1g) effect on RBC transition order
#TEST-VAL-SUB026-3023#REF# FCT 2.1 Order to establish communication session with given RBC ID and phone nr
#TEST-VAL-SUB026-5132#REF# FCT 2.2 , CFX00033410 Session establishment command after abortion of RBC/RBC-Handover
#TEST-VAL-SUB026-3016#REF# FCT 2.3 Order to establish communication session - ongoing establishemnt with the same RBC
#TEST-VAL-SyAnfSpezCR-0071#REF# EET error expectation OBU establishes communication session, unless currently being established or already established with the same RBC

#REQ-UNISIG-SUB026-3062:01#REF# 3.5.3.4.c) #REQ-UNISIG-SUB026-000853#REF#
#REQ-UNISIG-SUB026-000862#REF#
The on-board shall establish a communication session, if a mode change, not considered as an End of Mission, has to be reported to the RBC (only
if level 2 or 3).
UNISIG clarification:
only to the supervising RBC and if no session is established.

an existing session to an Accepting RBC is not relevant this case.
realised by: #REQ-UNISIG-SUB026-3547:01#REF#

#REQ-UNISIG-SUB026-3547:01#REF# to.3.5.3.4.c) #REQ-UNISIG-SUB026-3062:01#REF#
#REQ-UNISIG-SUB026-3069:01#REF#
#REQ-UNISIG-SUB026-010272#REF#
#ANA-UNISIG-CR0560-0002:01#REF#
The on-board shall establish a communication session to the supervising RBC, if
- no session with the supervising RBC is established or is currently being established
AND
- the on-board is in level 2/3 after a mode change
AND
- the mode is changed correspondingly #DSC-TBL-CR560-0001#REF#.

remark: The mode change is reported with the first position report after a successfull session establishment.
DSC-TBL-CR560-0001 defines the relevant mode changes and restrictions
TEST APPROACH:
The following aspects have been identified:
1) no session with the supervising RBC is established or is currently being established
1.1) session establsihed
1.2) session establsihment ongoing
2) the on-board is in level 2/3 after a mode change
3) the mode is changed correspondingly #DSC-TBL-CR560-0001#REF#.
3.1) NP -> SB session establishment is part of SoM procedure
3.2) SL -> SB
3.2.1) open desk
3.2.2) closed desk
3.3) SH -> SB
3.3.1) open desk
3.3.2) closed desk
3.4) SB -> SH
3.5) PT -> SH
3.6) xx -> FS
3.7) xx -> LS
3.8) xx -> SR
3.9) xx -> OS
3.10) xx -> NL
3.11) xx -> TR
3.12) xx -> PT
3.13) xx -> RV
3.14) xx -> SL
3.15) xx -> SN
3.16) xx -> UN
3.17) xx -> PS -> xx
The ETCS mode NP is not realised by the ASW refer realisation of #REQ-UNISIG-SUB026-004698#REF# 
the aspect 3.1 is hence omitted. 
#TEST-VAL-SUB026-8252#REF# FCT 1.1, 1.2 Mode change while session with the supervising RBC is established or currently being established
#TEST-VAL-SUB026-8253#REF# FCT 2 Concurrent mode and level change L2->L1 without communication session
#TEST-VAL-SUB026-7141#REF# FCT 3.2.1 Mode transition SL/L2 to SB/L2 due to cab opening
#TEST-VAL-SUB026-4661#REF# FCT 3.3.1 RBC ID/Phone Number unchanged when entering SH
#TEST-VAL-SUB026-3660#REF# FCT 3.3.2, 3.4 OBU establishes communication session and sends PR due to mode change SB->SH
#TEST-VAL-SUB026-3B13#REF# FCT 3.5 Establishing a communication session at mode transition SB -> SH (L2, not EoM)
#TEST-VAL-SUB026-3B14#REF# FCT 3.7 Establishing a communication session at mode transition to LS(L2), SB(L2, EoM)
#TEST-VAL-SUB026-4343#REF# FCT 3.8 OBU establishes communication session and sends PR due to mode change OS->SR
#TEST-VAL-SUB026-4338#REF# FCT 3.9, 3.6 OBU establishes communication session and sends PR due to mode change FS->OS, OS->FS
#TEST-VAL-SUB026-4342#REF# FCT 3.10 OBU establishes communication session and sends PR due to mode change SR->NL
#TEST-VAL-SUB026-4350#REF# FCT 3.11 OBU establishes communication session and sends PR due to mode change SH->TR
#TEST-VAL-SUB026-4346#REF# FCT 3.12 OBU establishes communication session and sends PR due to mode change FS->TR TR->PT
#TEST-VAL-SUB026-4345#REF# FCT 3.13 OBU establishes communication session and sends PR due to mode change OS->RV
#TEST-VAL-SUB026-4660#REF# FCT 3.14, 3.2.2 RBC ID/Phone Number unchanged when entering RV/SL/SB
#TEST-VAL-SUB026-4451#REF# FCT 3.15 Check establishment of communication session at transition to SN, TR
#TEST-VAL-SUB026-7173#REF# FCT 3.16 Mode transition OS/L2 -> UN/L2 without communication session
#TEST-VAL-SUB026-3B04#REF# FCT 3.17 NV not yet applicable remain unchanged at modes transitions (PS)
#TEST-VAL-SUB026-3B16#REF# EET error expectation Establishing a communication session after SoM (with no session established) in L2
#TEST-VAL-SUB026-4339#REF# EET error expectation OBU establishes communication session and sends PR due to mode change FS->OS->FS
#TEST-VAL-SUB026-4347#REF# EET error expectation OBU establishes communication session and sends PR due to mode change FS->TR->PT PT->SR
#TEST-VAL-SUB026-4351#REF# EET error expectation OBU establishes communication session and sends PR due to mode change SH->NL
#TEST-VAL-SUB026-4352#REF# EET error expectation OBU establishes communication session and sends PR due to mode change UN->TR(L2)
#TEST-VAL-SUB026-4353#REF# EET error expectation OBU establishes communication session and sends PR due to mode change UN->SR(L2)
#TEST-VAL-SUB026-4356#REF# EET error expectation Neither Level change nor processing Con. EM STOP leads to establishment of communication session FS(L1)->FS(L2)

#REQ-UNISIG-SUB026-3063:01#REF# 3.5.3.4.d) #REQ-UNISIG-SUB026-000853#REF#
The on-board shall establish a communication session, if the driver has manually changed the level to 2 or 3.
TEST APPROACH:
Levels 2/3 are considered as one equivalence class.
The following aspects are identified:
1. Level 0 -> Level 2/3
2. Level 1 -> Level 2/3
3. Level NTC -> Level 2/3
#TEST-VAL-SUB026-3587#REF# FCT 1 OBU establishes communication session due to manual level change L0->L2
#TEST-VAL-SUB026-3586#REF# FCT 2 OBU establishes communication session due to manual level change L1->L2
#TEST-VAL-SUB026-3658#REF# FCT 3 OBU establishes communication session due to manual level change STM->L2

#REQ-UNISIG-SUB026-3064#REF# to.3.5.3.4.d) #REQ-UNISIG-SUB026-000862#REF#
If the driver manually changes the level to 2 or 3 and if a communication session to the respective RBC already exists, the on-board shall
maintain this session.
#TEST-VAL-SUB026-5999#REF# EET CFX00037807 Driver manually changes the level to 2, communication session to the respective RBC already exists
#TEST-VAL-SUB026-3584#REF# FCT basic function driver manually changes to level 2 communication session to the respective RBC already exists - T_NVCONTACT expiry

#REQ-UNISIG-SUB026-3065:01#REF# 3.5.3.4.e) #REQ-UNISIG-SUB026-000853#REF#
#REQ-UNISIG-SUB026-000862#REF#
The on-board shall establish a communication session,
- when the train front reaches the end of an announced radio hole
AND
- no communication session is currently being established or is already established with the supervising RBC/RIU.
TEST APPROACH:
The following aspects have been identified:
When the train front reaches the end of an announced radio hole:
1) communication session is already established
2) no communication session is established
3) ongoing establishment of communication session
4) ongoing setup of safe connection
#TEST-VAL-SUB026-7020#REF# FCT 1, 2 Session establishment when train front reaches the end of an announced radio hole
#TEST-VAL-SUB026-7021#REF# FCT 3 Train front reaches the end of an announced radio hole, communication session is currently being established
#TEST-VAL-SUB026-7022#REF# FCT 4 Train front reaches the end of an announced radio hole, safe connection setup is currently being established
#TEST-VAL-SUB026-4400#REF# EET error expectation Communication session terminated because of a loss of safe radio connection inside an announced radio hole
#TEST-VAL-SUB026-5491#REF# EET error expectation RBC transition within announced radio hole - outage of safe connection

#REQ-UNISIG-SUB026-010271#REF# 3.5.3.4.f) #REQ-UNISIG-SUB026-000853#REF#
The on-board shall establish a communication session, when the previous communication session is considered as terminated due to loss of safe
radio connection (refer to 3.5.4.2.1).
#TEST-VAL-SUB026-3B15#REF# FCT basic function Establishing a communication session after previous session was considered terminated due to loss of safe radio connection
#TEST-VAL-SUB026-3983#REF# EET error expectation OBU establishes session with same RBC but new network

#REQ-UNISIG-SUB026-010272#REF# 3.5.3.4.g) #REQ-UNISIG-SUB026-000853#REF#
#ANA-UNISIG-SessionEstablishment-0005#REF#
The on-board shall establish a communication session, when a Start of Mission procedure, during which no communication session could be
established, is completed in level 2 or 3.
is realized through 3.5.3.4 c) - see analysis
realised by: #REQ-UNISIG-SUB026-3547:01#REF#

#REQ-DESIGN-CR-0567#REF# to.3.5.3.4 #ANA-UNISIG-SessionEstablishment-0003#REF#
If the on-board has been received an order to establish a communication session while there is a communication session with the same RBC/ RIU
currently being terminated, then the establishment of the communication session shall be performed after the successful termination of the
communication session.
#TEST-VAL-SUB026-4391#REF# EET CFX00040331 Order to establish communication session - connection to RBC not yet terminated after L1 transition
#TEST-VAL-SUB026-3895#REF# FCT basic function Order for new session with same RBC executed after termination if latter is in progress
#TEST-VAL-SUB026-3418#REF# EET error expectation Mode transition SL -> SB (SoM), session termination/establishment

#REQ-UNISIG-SUB026-000862#REF# 3.5.3.4.1 #REQ-UNISIG-SUB026-001778#REF#
In respect of a), b), c), d) and e) of 3.5.3.4, the on-board shall not establish a new communication session with an RBC/RIU in case a
communication session is currently being established or is already established with this RBC/RIU.
realised by: #REQ-DESIGN-CR-0363:01#REF#
realised by: #REQ-UNISIG-SUB026-3417#REF#
realised by: #REQ-UNISIG-SUB026-3062:01#REF#
realised by: #REQ-UNISIG-SUB026-3064#REF#
realised by: #REQ-UNISIG-SUB026-3065:01#REF#

#REQ-DESIGN-CR-0541:01#REF# 3.5.3.5.2
If the ERTMS/ETCS on-board equipment has to establish a communication session with an RBC whilst in session with another RBC, the existing
communication session shall be terminated (see 3.5.5.2 for details) and the new one shall be established. Exception: the order to contact an
Accepting RBC shall not terminate the communication session with the Handing Over RBC.
UNISIG clarification:
The exception relates to a RBC transition order (P131) only.
realised by: #REQ-DESIGN-CR-0749:02#REF#
realised by: #REQ-UNISIG-SUB026-000871#REF#

#REQ-DESIGN-CR-0749:02#REF# to.3.5.3.5.2 #REQ-DESIGN-CR-0541:01#REF#
#ANA-UNISIG-SessionEstablishment-0002#REF#
If a session establishment command is received and accepted from trackside (only P42) and
- a session exists to another RBC
OR
- a session exists to the new RBC, but this session is not the supervised session,
the existing communication sessions to other RBC(s) and the not supervised session to the new RBC, if available, shall be terminated (see
3.5.5.2 for details).

Exceptions:
- For an order to establish a communication session from trackside during a handover see #REQ-UNISIG-SUB026-010568#REF#.
TEST APPROACH:
The following aspects have been identified:
1) session to another RBC
2) non supervising session to the new RBC
3) supervising session to the new RBC and session to another RBC
4) Exception: order to establish a communication session from trackside during a handover is verified via #REQ-UNISIG-SUB026-010568#REF#
#TEST-VAL-SUB026-3976#REF# FCT 1 Effect of new Session establishment order on existing session
#TEST-VAL-SUB026-7175#REF# FCT 2 P42 establsh communication session to ACC-RBC
#TEST-VAL-SUB026-7179#REF# FCT 3 Session establishment after termination order from track side
#TEST-VAL-SUB026-3730#REF# EET error expectation reception of pkt45/42 (new network and RBC) while OBU equipment already in session with another RBC
#TEST-VAL-SUB026-4H33#REF# EET error expectation Reception of order to establish a communication session with an different RBC than the connected in combination with level transition

#REQ-UNISIG-SUB026-000871#REF# to.3.5.3.5.2 #REQ-DESIGN-CR-0541:01#REF#
#ANA-UNISIG-SessionEstablishment-0002#REF#
If a session, commanded from trackside or driver, is to be established and existing sessions should be commanded to termination at first (see
#REQ-DESIGN-CR-0749:02#REF# and #REQ-UNISIG-SUB026-3066:02#REF#), the new session shall be established as soon as one mobile is free.

Exception: If a communication session with the same is currently being terminated, #REQ-DESIGN-CR-0567#REF# shall be considered.
TEST APPROACH:
The following aspects have been identified:
1) commanded from trackside 
1.1) free mobile available when receiving session establishment command
1.2) communication session with the same RBC is currently being terminated
1.3) no communication session with the same RBC
2) commanded from driver 
2.1) free mobile available when receiving session establishment command
2.2) communication session with the same RBC is currently being terminated
2.3) no communication session with the same RBC
#TEST-VAL-SUB026-3976#REF# FCT 1.1 Effect of new Session establishment order on existing session
#TEST-VAL-SUB026-7179#REF# FCT 1.2, 1.3 Session establishment after termination order from track side
#TEST-VAL-SUB026-5612#REF# FCT 2.1 Driver manually changes the level to 2 while communication session to another RBC already exists
#TEST-VAL-SUB026-7180#REF# FCT 2.2, 2.3 Session establishment after termination order from driver

#REQ-UNISIG-SUB026-3066:02#REF# to.3.5.3.5.2 #ANA-UNISIG-SessionEstablishment-0007#REF#
If the driver manually changes the level to 2 or 3 and
- a session exists to another RBC
OR
- a session exists to the new RBC, but this session is not supervised,
the existing communication sessions to other RBC(s) and the not supervised session to the new RBC, if available, shall be terminated (see
3.5.5.2 for details).
TEST APPROACH:
The following aspects have been identified:
1) one session, session to another RBC
2) one session, session to the new RBC
3) two session, new RBC is not the supervising 
4) two session, new RBC is supervising
5) driver selects L2/L3 no level change
#TEST-VAL-SUB026-5612#REF# FCT 1 Driver manually changes the level to 2 while communication session to another RBC already exists
#TEST-VAL-SUB026-7174#REF# FCT 2 Communication session handling in case of LT L2->L1->L2
#TEST-VAL-SUB026-5544#REF# FCT 3 , CFX00038122 Degraded situation manual level change (L2->L0->L2) during RBC handover
#TEST-VAL-SUB026-7142#REF# FCT 4 Level change during RBC handover
#TEST-VAL-SUB026-7177#REF# FCT 5 , CFX00038122 Manual level change during RBC handover
#TEST-VAL-SUB026-5480#REF# EET error expectation Accidental loss of an already open session SoM (S20) - maximal time to consider the communication session still established exceeded

#REQ-UNISIG-SUB026-0420:01#REF# 3.5.3.7 #REQ-UNISIG-SUB026-007957#REF#
If the establishment of a communication session is initiated by the on-board, it shall be performed according to the following steps:
a)	The on-board shall request the set-up of a safe radio connection with the trackside. If this request is part of an on-going Start of
Mission procedure, it shall be repeated until successful or a defined number of times (see Appendix A.3.1).
If this request is not part of an on-going Start of Mission procedure, it shall be repeated until at least one of the following conditions is
met:
  Safe radio connection is set up
  End of Mission is performed
  Order to terminate communication session is received from trackside
  The train passes a level transition border (from level 2/3 to level 0, NTC, 1) with its front end.
  Order to establish communication session with a different RBC is received from trackside and the order does not request to contact an
Accepting RBC.
  The train passes a RBC/RBC border with its front end.
  The train front passes the start of an announced radio hole
  Regards RIUs only: Level 1 is left
b)	As soon as the safe radio connection is set-up, the on-board shall send the message Initiation of communication session to the
trackside.
c)	As soon as the trackside receives the information, it shall send the system version.
part c is only trackside

RIU is not realized
=> the last point "Regards RIUs only: Level 1 is left" is not relevant
#DSC-UNISIG-SUB026-000907#REF#

Figure 3: Establishment initiated by on-board
realised by: #REQ-UNISIG-SUB026-010273#REF#
realised by: #REQ-UNISIG-SUB026-010274#REF#
realised by: #REQ-UNISIG-SUB026-010275:01#REF#
realised by: #REQ-UNISIG-SUB026-010277#REF#

#REQ-UNISIG-SUB026-010273#REF# 3.5.3.7 #REQ-UNISIG-SUB026-0420:01#REF#
If the establishment of a communication session is initiated by the on-board, it shall be performed according to the following steps:
a) The on-board shall request the set-up of a safe radio connection with the trackside.
b) As soon as the safe radio connection is set-up, the on-board shall send the message Initiation of communication session to the trackside.

Remark: As soon as the trackside receives the information "Initiation of communication session", it has to be sended the system
version.
#TEST-VAL-SUB026-3B18#REF# FCT basic function Troubleshooting during establishment a communication session at SoM in A31

#REQ-UNISIG-SUB026-010274#REF# 3.5.3.7 #REQ-UNISIG-SUB026-0420:01#REF#
If the request to the set-up of a safe radio connection with the trackside is unsuccessful and this request is part of an on-going Start of
Mission procedure, it shall be repeated until successful or a defined number of times (see Appendix A.3.1).
#TEST-VAL-SUB026-3B16#REF# FCT a defined number of times Establishing a communication session after SoM (with no session established) in L2
#TEST-VAL-SUB026-3B18#REF# FCT request repeated until successfull Troubleshooting during establishment a communication session at SoM in A31

#REQ-UNISIG-SUB026-010275:01#REF# 3.5.3.7 #REQ-UNISIG-SUB026-0420:01#REF#
#ANA-UNISIG-SessionEstablishment-0010#REF#
If the request to the set-up of a safe radio connection with the trackside is unsuccessful this request is not part of an on-going Start of
Mission procedure, it shall be repeated until at least one of the following conditions is met:
∙	Safe radio connection is set up
∙	End of Mission is performed
∙	Order to terminate communication session is received from trackside
∙	The train passes a level transition border (from level 2/3 to level 0, NTC, 1) with its front end.
∙	Order to establish communication session with a different RBC is received from trackside and the order does not request to contact an
Accepting RBC.
∙	The train passes a RBC/RBC border with its max safe front end - only for Handing Over RBC
∙	The train front passes the start of an announced radio hole
∙	the handover is cancelled - only for Accepting RBC
UNISIG clarification:
the point "The train passes a RBC/RBC border with its front end" is only relevant for the HO RBC

additional point for ACC RBC
TEST APPROACH:
The following aspects have been identified:
1) Safe radio connection is set up
2) End of Mission is performed
3) Order to terminate communication session is received from trackside
4)The train passes a level transition border from L2/L3 to
4.1) L0
4.2) L1
4.3) NTC
5) Order to establish communication session with a different RBC is received
6) The train passes a RBC/RBC border with its front end
7) The train front passes the start of an announced radio hole
8) The handover is cancelled 
#TEST-VAL-SUB026-5998#REF# FCT 1 Session establishment, repetition of attempted to establish safe connection
#TEST-VAL-SUB026-3B21#REF# FCT 2 Safe radio connection set-up: End of Mission performed
#TEST-VAL-SUB026-3B19#REF# FCT 3 Safe radio connection set-up: terminate communication session received
#TEST-VAL-SUB026-3B23#REF# FCT 4.1 Safe radio connection set-up: pass LT border (L2 - L0)
#TEST-VAL-SUB026-3B22#REF# FCT 4.2 Safe radio connection set-up: pass LT border (L2 - L1)
#TEST-VAL-SUB026-3B24#REF# FCT 4.3 Safe radio connection set-up: pass LT border (L2 - NTC)
#TEST-VAL-SUB026-3B20#REF# FCT 5 Safe radio connection set-up: received establish communication session with other RBC
#TEST-VAL-SUB026-3B26#REF# FCT 6 Safe radio connection set-up: pass RBC/RBC border
#TEST-VAL-SUB026-3B25#REF# FCT 7 Safe radio connection set-up: pass start location of radio hole
#TEST-VAL-SUB026-8129#REF# FCT 8 Repetition of set-up of a safe radio connection

#REQ-UNISIG-SUB026-010277#REF# 3.5.3.7 #REQ-UNISIG-SUB026-0420:01#REF#
If a request to the set-up of a safe radio connection with the trackside is unsuccessful, the request shall be repeated immediately after
EURORADIO has indicated that setting up the safe radio connection has failed.

remark: a small time delay is possible between the single attempts (maximum 5 seconds).
UNISIG clarification: an immediately repetition can lead to problems.
#TEST-VAL-SUB026-3025#REF# FCT basic function Delay time to set-up safe radio connection

#REQ-UNISIG-SUB026-0421:01#REF# 3.5.3.8 #REQ-UNISIG-SUB026-0694:01#REF#
When the on-board receives the system version it shall consider the communication session established and:
a)	If one of its supported system versions is compatible with the one sent by trackside, it shall send a session established report,
including its telephone numbers, to the trackside.
b)	If none of its supported system versions is compatible with the one sent by trackside, it shall send a version independent message
indicating “No compatible version supported”. It shall inform the driver and shall terminate the communication session.
a) message 159 - session established
b) message 154 - no compatible session
#DSC-UNISIG-SUB026-000907#REF#

Figure 3: Establishment initiated by on-board
#TEST-VAL-SUB026-5429#REF# EET CFX00037121 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open with a future version
#TEST-VAL-SUB026-3018#REF# FCT basic function Connection establishment System Version supported/not supported

#REQ-UNISIG-SUB026-010278#REF# to.3.5.3.8 #REQ-DESIGN-CR-0093:01#REF#
#ANA-UNISIG-SessionEstablishment-0004#REF#
If no system version is received from trackside within a fixed waiting time (see appendix to chapter 3, List of Fixed Value Data) after sending
the message "Initiation of communication session", the message "Initiation of communication session" shall be repeated with
the fixed waiting time after each repetition.
#TEST-VAL-SUB026-3B18#REF# FCT basic function Troubleshooting during establishment a communication session at SoM in A31
#TEST-VAL-SUB026-3B28#REF# EET error expectation Initiation of Communication Session repetition not interrupted in case of losing safe radio connection

#REQ-UNISIG-SUB026-010279#REF# to.3.5.3.8 #ANA-UNISIG-SessionEstablishment-0004#REF#
After a defined number of repetitions (see Appendix A.3.1), and if no system version from RBC is received within the fixed waiting time from the
time of the last sending of "Initiation of communication session", the ERTMS/ETCS onboard equipment shall consider the communication
session terminated.
#TEST-VAL-SUB026-3B27#REF# FCT basic function Fixed waiting time for receiveing System Version at establishment of communication session

#REQ-UNISIG-SUB026-010307#REF# to.3.5.3.8 #ANA-UNISIG-SessionEstablishment-0004#REF#
When the on-board will answered of the received system version from the RBC and the safe radio connection is lost, the answer shall be sended
after the reestablishment of the safe radio connection.
TEST APPROACH:
The following aspects were identified (all aspects consider that safe radio connection is lost after receiving M32):
1. RBC sends M32 with version not compatible (OBU has to answer with M154/M156)
1.1 safe connection is not recovered before session maintaining time expires
1.2 safe connection is recovered before session maintaining time expires
2. RBC sends M32 with compatible version (OBU has to answer with M159)
2.1 safe connection is not recovered before session maintaining time expires
2.2 safe connection is recovered before session maintaining time expires
#TEST-VAL-SUB026-8149#REF# FCT 1.1 Lose safe radio connection after receiving not compatible System Version (connection is lost longer than session maintaining time)
#TEST-VAL-SUB026-3B29#REF# FCT 1.2, 2.2 Lose safe radio connection after receiving System Version (supported/not supported) from RBC
#TEST-VAL-SUB026-8148#REF# FCT 2.1 Lose safe radio connection after receiving compatible System Version (connection is lost longer than session maintaining time)

#REQ-UNISIG-SUB026-0423#REF# 3.5.3.10
If the establishment of a communication session is initiated by the RBC, it shall be performed according to the following steps:
a)	The trackside shall request the set-up of a safe radio connection with the on-board.
b)	As soon as the safe radio connection is set-up, the trackside shall send the message Initiation of communication session to the
on-board.
c)	When the on-board receives the information, it shall consider the communication session established and send a session established
report to the trackside.
d)	When the trackside receives the session established report, it shall consider the communication session established.
a), b), d) only trackside

see following figure 4
#DSC-UNISIG-SUB026-000915#REF#

Figure 4: Establishment initiated by the RBC
#TEST-VAL-SUB026-3019#REF# FCT basic function Initiation of a communication session by RBC

#REQ-UNISIG-SUB026-010347#REF# to.3.5.3.12 #ANA-UNISIG-SessionEstablishment-0006#REF#
In the case the RBC is the initiator of a session establishment, the OBU shall accept this initiation only if no session to a supervising RBC
exists, the id of the initiating RBC agrees with the stored RBC id and a negotiated system version with the initiating RBC is available.
If the OBU doesn't accept the session initiation, the OBU shall reject the safe radio connection to this RBC.
#TEST-VAL-SUB026-3B43#REF# FCT basic function Handling of RBC session initiation request if RBC RBC ID and negociated version is not available
#TEST-VAL-SUB026-3B44#REF# EET error expectation Handling of RBC session initiation request after transition to L0

#REQ-UNISIG-SUB026-010349#REF# to.3.5.3.12 #ANA-UNISIG-SessionEstablishment-0006#REF#
In the case the RBC is the initiator of a session establishment, the last system version negotiated with this RBC shall be used.
#TEST-VAL-SUB026-3B42#REF# FCT basic function RBC initiates session establishment, OBU uses last negotiated system version

#REQ-UNISIG-SUB026-0425:01#REF# 3.5.3.13
An order to contact the RBC may contain a special value for the RBC identity indicating that the on-board shall contact the last known RBC
(i.e., using the stored RBC ID/phone number, if any); the phone number indicated in the order shall be ignored by the on-board equipment.
#TEST-VAL-SUB026-3824#REF# FCT RBC ID TBR OBU receives order to contact the last known RBC - RBC ID/Phone number in state to be revalidated
#TEST-VAL-SUB026-3659#REF# FCT RBC ID valid OBU ignores phone number indicated in pkt42 with NID_RBC=Contact last known RBC
#TEST-VAL-SUB026-3782#REF# EET error expectation Order to contact last known RBC after level transition L2 to L1

#REQ-UNISIG-SUB026-3473#REF# 3.5.3.13.1
If there is no RBC ID/ phone number stored on-board, the order to contact the RBC shall be ignored.
#TEST-VAL-SUB026-3960#REF# FCT RBC ID deleted Communication Session Management order with NID_RBC='Contact last known RBC'
#TEST-VAL-SUB026-3021#REF# FCT RBC ID unknown (initial state) Request to contact last known RBC, RBC ID no RBC ID available

#REQ-UNISIG-SUB026-0427:01#REF# 3.5.3.15 #ANA-UNISIG-SessionEstablishment-0001#REF#
An order to contact the RBC may contain a special value for the RBC phone number indicating that the on-board shall use the on-board short
number.
note for validation:
KBS manage this special value (see analysis)
#TEST-VAL-SUB026-3022#REF# FCT basic function NID_RADIO = FFFF FFFF FFFF FFFF (Use the short number stored onboard)

#REQ-UNISIG-SUB026-0429:01#REF# 3.5.4.1
When a communication session is established, in case of a loss of the safe radio connection, i.e., if the disconnection has not been ordered
(see 3.5.5.1), the involved entities shall consider the communication session still established for a defined time. The defined time shall start
as soon as EURORADIO has indicated the loss of the safe radio connection.
TEST APPROACH:
The following aspects have been identified:
1) safe radio connection re-established within the defined time
2) safe radio connection not re-established within the defined time
#TEST-VAL-SUB026-4357#REF# FCT 1 Maintain session established for a defined time in case of losing safe radio connection
#TEST-VAL-SUB026-3B15#REF# FCT 2 Establishing a communication session after previous session was considered terminated due to loss of safe radio connection
#TEST-VAL-SUB026-3990#REF# EET error expectation RadioNetworkId - outage of safe connection
#TEST-VAL-SyAnfSpezCR-0044#REF# EET error expectation Repetition of MA request after lost of communication session

#REQ-UNISIG-SUB026-0430#REF# 3.5.4.2
When EURORADIO indicates the loss of the safe radio connection, the ERTMS/ETCS on-board equipment shall immediately try to set-up a new safe
radio connection.
#TEST-VAL-SUB026-3025#REF# FCT basic function Delay time to set-up safe radio connection

#REQ-UNISIG-SUB026-3061:01#REF# 3.5.4.2.1 #REQ-UNISIG-SUB026-3067#REF#
If the safe radio connection is not re-established after the defined time (as defined in A.3.1), both, on-board equipment and trackside, shall
consider the session as terminated.
TEST APPROACH:
The following aspects have been identified:
1) safe radio connection re-established within the defined time
2) safe radio connection not re-established within the defined time
#TEST-VAL-SUB026-4357#REF# FCT 1 Maintain session established for a defined time in case of losing safe radio connection
#TEST-VAL-SUB026-3B15#REF# FCT 2 Establishing a communication session after previous session was considered terminated due to loss of safe radio connection

#REQ-UNISIG-SUB026-000941#REF# 3.5.4.3
The attempts shall be repeated, until at least one of the following conditions is met:
  The safe radio connection is set-up.
  The session is considered as terminated.
  The train passes the location indicated in the RIU order “Terminate the communication session”
UNISIG clarification:
the repetition is stopped generally, when the session is consicered as terminated.
realised by: #REQ-UNISIG-SUB026-0431:01#REF#
realised by: #REQ-UNISIG-SUB026-010284#REF#

#REQ-UNISIG-SUB026-0431:01#REF# 3.5.4.3 #REQ-UNISIG-SUB026-000941#REF#
The attempts shall be repeated, until at least one of the following conditions is met:
• The safe radio connection is set-up.
OR
• the session is considered as terminated
TEST APPROACH:
The following aspects have been identified:
1) safe connection is set-up (before session maintaining time expires)
2) session is considered as terminated
2.1) before session maintaining time expires
2.2) after session maintaining time expires
Note: 
Regarding aspect 2.1: if a session has to be terminated and the safe radio connection is lost (aspect 2.1), OBU considers the session terminated
(ref. #REQ-UNISIG-SUB026-010284#)
Regarding aspect 2.2: if session maintaining time expires, OBU considers session as terminated, but should try to set-up a new communication
session, and consequently to re-establish the safe connection (ref. #REQ-UNISIG-SUB026-010271#).
#TEST-VAL-SUB026-4357#REF# FCT 1 Maintain session established for a defined time in case of losing safe radio connection
#TEST-VAL-SUB026-3B31#REF# FCT 2.1 Terminate communication session: no session is established, or session established but no safe connection
#TEST-VAL-SUB026-3B15#REF# FCT 2.2 Establishing a communication session after previous session was considered terminated due to loss of safe radio connection

#REQ-UNISIG-SUB026-0432:02#REF# 3.5.4.4
Exception to 3.5.4.2 and 3.5.4.3: the on-board equipment shall not try to set up a new safe radio connection and shall stop any on-going
attempts if the train front is inside an announced radio hole (see 3.12.1.3). The on-board equipment shall try to set it up again when the train
front reaches the end of the radio hole.
#TEST-VAL-SUB026-3026#REF# EET error expectation Loss of the safe radio connection, two radio hole area
#TEST-VAL-SUB026-4401#REF# EET error expectation Mode change FS->NL within announced radio hole (no safe radio connection available)
#TEST-VAL-SUB026-4400#REF# FCT loss of stable connection Communication session terminated because of a loss of safe radio connection inside an announced radio hole
#TEST-VAL-SUB026-3015#REF# FCT on-going attempt , CFX00035657 Re-try to establish connection after exit of radio hole area

#REQ-UNISIG-SUB026-3565#REF# 3.5.4.5
In case a message has to be sent during the loss of the safe radio connection, this message shall be considered as sent.
exception:
for train data 3.18.3.4.2 is valid
TEST APPROACH:
The requirement is not tested for each possible message as the function does not depend on the send message.
#TEST-VAL-SUB026-3443#REF# FCT M132 pkt 90 - MA request not memorized if no safe connection established
#TEST-VAL-SUB026-3663#REF# FCT M136 due to LT Outage of safe connection while passing level transition L0 location
#TEST-VAL-SUB026-3662#REF# FCT M136 due to mode change, M150 message sent during loss of the safe connection considered as sent msg136, repetition process goes on msg150
#TEST-VAL-SUB026-5247#REF# FCT M137/M138 M137/M138 and short outage of safe connection
#TEST-VAL-SUB026-3664#REF# FCT M147 Outage of safe connection during level transition to L2 with ES

#REQ-UNISIG-SUB026-3566#REF# to.3.5.4.5 #ANA-UNISIG-SafeConnection-0001:01#REF#
An ongoing repetition process shall not be interrupted or terminated by the loss of the safe radio connection.
TEST APPROACH:
The requirement is not tested for each possible message as the function does not depend on the send message.
#TEST-VAL-SUB026-3661#REF# FCT M129 valid train data sent again once the safe connection has been re-established
#TEST-VAL-SUB026-3665#REF# FCT M130 Outage of safe connection after sending Request for Shunting
#TEST-VAL-SUB026-3663#REF# FCT M136 due to leaving L2 Outage of safe connection while passing level transition L0 location
#TEST-VAL-SUB026-3694#REF# FCT M136 due to leaving RBC area Outage of safe connection when passing RBC transition border with min safe rear end
#TEST-VAL-SUB026-3662#REF# FCT M150 message sent during loss of the safe connection considered as sent msg136, repetition process goes on msg150
#TEST-VAL-SUB026-3B28#REF# FCT M155 Initiation of Communication Session repetition not interrupted in case of losing safe radio connection

#REQ-UNISIG-SUB026-3567#REF# to.3.5.4.5 #ANA-UNISIG-SafeConnection-0001:01#REF#
Repeating a message shall be understood as sending this message with an updated content, i.e. not re-sending the same message.
#TEST-VAL-SUB026-3694#REF# FCT basic function Outage of safe connection when passing RBC transition border with min safe rear end

#REQ-UNISIG-SUB026-000952#REF# 3.5.5.1 #REQ-UNISIG-SUB026-001829#REF#
The termination of a communication session shall be initiated only by the on-board and in the following cases:
a)	If an order is received from trackside (RBC, RIU or balise groups) (see sections 3.5.3.5 and 3.5.3.6 concerning the content of the
order).
b)	If an error condition requiring the termination of the communication session is detected on-board (e.g., not compatible system versions
between on-board and trackside).
c)	The train is rejected by RBC during Start of Mission.
d)	If the driver closes the desk during Start of Mission.
e)	In case the train has reported having exited from an RBC area and no order to terminate the session is received within a fixed waiting
time (see Appendix A.3.1) from the time the position report was sent, the ERTMS/ETCS on-board equipment shall repeatedly send a position report
with the fixed waiting time after each repetition, until the order to terminate the session is received, or the defined number of repetitions
(see Appendix A.3.1) has been reached. If no reply is received within the fixed waiting time after the last repetition, the ERTMS/ETCS on-board
equipment shall terminate the communication session.
f)	In case of communication session with an RIU: the Level 1 is left, or, an End of Mission is executed.
realised by: #REQ-UNISIG-SUB026-2401:02#REF#
realised by: #REQ-UNISIG-SUB026-010282#REF#
realised by: #REQ-UNISIG-SUB026-3681#REF#
realised by: #REQ-DESIGN-CR-0411#REF#
realised by: #REQ-UNISIG-SUB026-2326#REF#
realised by: #REQ-UNISIG-SUB026-0681:03#REF#
realised by: #REQ-UNISIG-SUB026-010283#REF#

#REQ-UNISIG-SUB026-2401:02#REF# 3.5.5.1.a) #REQ-UNISIG-SUB026-000952#REF#
If a termination order for a RBC is received from trackside, the on board unit shall initiate the termination of the communication session to
this RBC.

remark: The variable Q_SLEEPSESSION is only relevant for the session establishment order (see the definition of the variable).
UNISIG clarification: the variable Q_SLEEPSESSION is not relevant for an order to session termination
TEST APPROACH:
Radio infill not realized in R8 the aspect RIU is hence omitted.
#TEST-VAL-SUB026-3018#REF# FCT BG Connection establishment System Version supported/not supported
#TEST-VAL-SUB026-3409#REF# EET CFX00035651 korrektes Reset bei Verbindungsabbruch durch RBC
#TEST-VAL-SUB026-3832#REF# FCT RBC No further message send by the on-board after the message Termination of communication session

#REQ-UNISIG-SUB026-010282#REF# 3.5.5.1.a) #REQ-UNISIG-SUB026-000952#REF#
If a termination order for a RIU is received from trackside and the train has passed ther location inidicated in the RIU termination order, the
on board unit shall initiate the termination of the communication session to this RIU.
radio infill is not realized

#REQ-UNISIG-SUB026-010280#REF# to.3.5.5.1.a) #ANA-UNISIG-SessionTermination-0001#REF#
If an order to termination a session is received but no session is established to the relevant RBC/RIU, the termination order shall be ignored.
radio infill is not realized
TEST APPROACH:
Radio infill not realized in R8 the aspect RIU is hence omitted.
#TEST-VAL-SUB026-3B31#REF# FCT basic function Terminate communication session: no session is established, or session established but no safe connection
#TEST-VAL-SUB026-8130#REF# EET error expectation No further message send by the on-board after the message Termination of communication session

#REQ-UNISIG-SUB026-007076#REF# to.3.5.5.1.a) #ANA-UNISIG-SessionTermination-0001#REF#
If an order to termination a session with the special value "contact the last known RBC" is received, the on board unit shall initiate
the termination of the communication session with the stored RBC ID.
UNISIG clarification:
normally the trackside does'nt used this special value in termination command
#TEST-VAL-SUB026-5280#REF# FCT basic function Order to termination a session with special value contact the last known RBC (simple)
#TEST-VAL-SUB026-5239#REF# EET error expectation Reception of order to terminate communication session (NID_RBC=16383)
#TEST-VAL-SUB026-5278#REF# EET error expectation Order to termination a session with the special value contact the last known RBC (HO ongoing)
#TEST-VAL-SUB026-5279#REF# EET error expectation Order to termination a session with special value contact the last known RBC (HO executed)

#REQ-UNISIG-SUB026-3681#REF# 3.5.5.1.b) #REQ-UNISIG-SUB026-000952#REF#
If an error condition requiring the termination of the communication session is detected on-baord (e.g., not compatible system version between
on-board and trackside), the on board unit shall be initiated the termination of this communication session.

--- FINALISED ---
Das Terminieren der Session in den Fehlersituationen wird in den konkreten Anforderungen zur Fehlerreaktion definiert (z.B. der Abbau der
Session bei nicht kompatibler Version in 3.5.3.8 b)
#REQ-UNISIG-SUB026-3102:01#REF#, #REQ-UNISIG-SUB026-0844:01#REF#
#ANALYSE-VALUNISIG-4134#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-DESIGN-CR-0411#REF# 3.5.5.1.c) #REQ-UNISIG-SUB026-000952#REF#
If the train is rejected by RBC during Start of Mission, the on board unit shall initiate the termination of the communication session.
realizes through SoM, A39
realised by: #REQ-DESIGN-CR-0495#REF#

#REQ-UNISIG-SUB026-2326#REF# 3.5.5.1.d) #REQ-UNISIG-SUB026-000952#REF#
If the driver closes the desk during the start of mission, the on board unit shall initiate the termination of the current open communication
sessions, if available.
#TEST-VAL-SUB026-3831#REF# FCT established session Termination of a communication session due to driver closes desk during SoM [S10]
#TEST-VAL-SUB026-7075#REF# FCT session being established Termination of a communication session due to driver closes desk during SoM [A31]

#REQ-UNISIG-SUB026-0681:03#REF# 3.5.5.1.e) #REQ-UNISIG-SUB026-000952#REF#
#REQ-DESIGN-CR-0093:01#REF#
The position report "exited from a RBC area" shall be repeated with a defined waiting time (see fixed value) after each repetition, in
case
- a communication session to the RBC of the exited area is still open
AND
- no request to terminate the session to the RBC of the exited area is received from trackside.
AND
- no re-change to L2/3 is performed.

If no request to terminate the session to the RBC of the exited area is received after a defined number of repetitions (see fixed value), obu
shall terminate the session.
UNISIG clarification:
every termination command  to this rbc stops the repetition.
The "EXIT" procedure is stopped, when the train changes to L2/3 again.
TEST APPROACH:
The following aspects have been identified:
1) start
1.1) level transition L0
1.2) level transition L1
1.3) level transition NTC
1.4) RBC/RBC handover
2) repetition with a defined waiting time 
3) end
3.1) defined number of repetitions 
3.2) session terminated
3.3) re-change to L2/3 is performed
#TEST-VAL-SUB026-3616#REF# FCT 1.1, 2, 3.1 level transition L2->L0 RBC does not order termination of connection
#TEST-VAL-SUB026-3617#REF# FCT 1.2 level transition L2->L1 RBC does not order termination of connection
#TEST-VAL-SUB026-4489#REF# FCT 1.3 SN/STM - no response to PR when passing level transition location (min safe rear end) - reception of message 32 with incompatible version
#TEST-VAL-SUB026-8242#REF# FCT 1.4 Mode transition to FS, LS, OS in front of RBC transition border
#TEST-VAL-SUB026-3307#REF# FCT 3.2 Session establishment order to former supervising RBC when leaving L2/3 area
#TEST-VAL-SUB026-7174#REF# FCT 3.3 Communication session handling in case of LT L2->L1->L2

#REQ-UNISIG-SUB026-010283#REF# 3.5.5.1.f) #REQ-UNISIG-SUB026-000952#REF#
In case of communication session with an RIU, the on board unit shall initiate the termination of this session, if
- the Level 1 is left
OR
- an End of Mission is executed.
radio infill is not realized

#REQ-UNISIG-SUB026-0434#REF# 3.5.5.2 #REQ-UNISIG-SUB026-3694#REF#
In case a session is established, the on-board equipment shall terminate the communication session according to the following steps:
a)	The on-board equipment shall send a Termination of communication session message.
b)	As soon as this information is received, the trackside shall consider the communication session terminated and send an acknowledgement
to the on-board.
c)	When the acknowledgement is received the on-board shall consider the communication session terminated and request the release of the
safe radio connection with trackside.
b) only trackside

see following figure 5 also
#DSC-UNISIG-SUB026-000965#REF#

Figure 5: Termination of a communication session
#TEST-VAL-SUB026-3018#REF# FCT basic function Connection establishment System Version supported/not supported
#TEST-VAL-SUB026-3409#REF# EET error expectation korrektes Reset bei Verbindungsabbruch durch RBC

#REQ-UNISIG-SUB026-010284#REF# to.3.5.5.2 #REQ-UNISIG-SUB026-000941#REF#
If a termination of a communication session is to be initiated and a session is established but no safe connection is available, the session
shall be considered as terminated immediately.
UNISIG clarification:
if no safe connection is available, the termination steps haven't to be executed
TEST APPROACH:
The following aspects have been identified:
1) termination ordered by trackside
2) termination has to be initiated by OBU
#TEST-VAL-SUB026-3B31#REF# FCT 1 Terminate communication session: no session is established, or session established but no safe connection
#TEST-VAL-SUB026-3024#REF# FCT 2 P42 contact new RBC while safe connection for current section lost
#TEST-VAL-SUB026-7989#REF# EET error expectation loss of safe radio connection after sending PR with mode change to SH (safe connection not re-established)

#REQ-UNISIG-SUB026-0435#REF# 3.5.5.3
No further message shall be sent by the on-board after the message Termination of communication session.
#TEST-VAL-SUB026-3832#REF# FCT basic function No further message send by the on-board after the message Termination of communication session

#REQ-UNISIG-SUB026-000969#REF# 3.5.5.3.1
Exception: In case a communication session is established and no acknowledgement is received within a fixed waiting time (see Appendix A.3.1)
after sending the “Termination of communication session” message, the message shall be repeated with the fixed waiting time after each
repetition.
#TEST-VAL-SUB026-3832#REF# FCT basic function No further message send by the on-board after the message Termination of communication session

#REQ-UNISIG-SUB026-000971#REF# 3.5.5.3.2
After a defined number of repetitions (see Appendix A.3.1), and if no acknowledgment is received within the fixed waiting time from the time of
the last sending of “Termination of communication session”, the ERTMS/ETCS onboard equipment shall consider the communication session
terminated.
#TEST-VAL-SUB026-3832#REF# FCT basic function No further message send by the on-board after the message Termination of communication session

#REQ-UNISIG-SUB026-0437#REF# 3.5.5.6
Messages from the RBC received onboard after the message “Termination of communication session” has been sent shall be ignored with the
exception of the Acknowledgement of the termination of communication session.
#TEST-VAL-SUB026-3208#REF# FCT OBU initiated termination RBC message after OBU M154/M156
#TEST-VAL-SUB026-3031#REF# FCT P42 (from BG) initiated termination Messages ignorieren nach senden von termination of communication session
#TEST-VAL-SUB026-3833#REF# FCT P42 (from RBC) initiated termination No further message accepted by the on-board after the message Termination of communication session has been send

#REQ-UNISIG-SUB026-000979#REF# 3.5.5.7
In case an order to terminate the communication session is received, while the communication session is currently being established, the
on-board shall abort the process of establishing it and shall release the safe radio connection.
#TEST-VAL-SUB026-3B30#REF# FCT receive termination order after sending M155 Receive order to terminate the communication session while ongoing establishement process
#TEST-VAL-SUB026-3B19#REF# FCT safe connection not established yet Safe radio connection set-up: terminate communication session received

#REQ-UNISIG-SUB026-000983#REF# 3.5.6.1
ERTMS/ETCS on-board equipment shall order the registration of its connected Mobile Terminal(s) to a Radio Network:
a)	At power-up
b)	Following driver entry of a new Radio Network identity (only if level 2 or 3)
c)	If ordered from the trackside
the conditions for the activitation the driver entry is described in ERA SRS DMI
realised by: #REQ-DESIGN-CR-0432:01#REF#

#REQ-DESIGN-CR-0432:01#REF# 3.5.6.1 #REQ-UNISIG-SUB026-000983#REF#
ERTMS/ETCS on-board equipment shall order the registration of its connected Mobile Terminal(s) to a Radio Network:
a) At power-up
b) Following driver entry of a new Radio Network identity
c) If ordered from the trackside
TEST APPROACH:
The following aspects have been identified:
1) at power up
1.1) remanent storage
1.2) default network
1.3) usage of the remanent stored value in software hardware integration
2) following driver entry of a new Radio Network identity
2.1) manual level choice
2.2) at SoM
3) if ordered from the trackside
#TEST-VAL-SUB026-5536#REF# FCT 1.1, 2.2 RadioNetworkId - selection of a radio network from the list
#TEST-VAL-SUB026-5539#REF# FCT 1.2 RadioNetworkId default value 0xFFFFFF (automatic selection) configured
#TEST-VAL-SUB026-4213#REF# FCT 2.1 RBC contact information input possible during manual level transition to L2 - data memorized
#TEST-VAL-SUB026-3995#REF# FCT 3 Outage of safe connection after receiving new mnid
#TEST-SWHWINT-salsa-0006#REF# FCT 1.3 CR07 – Beibehaltung der eingegebenen DMI MN-Id

#REQ-DESIGN-CR-0433#REF# 3.5.6.2
When powered-off, ERTMS/ETCS on-board equipment shall memorize the last received Radio Network identity (from trackside or from driver) and
shall use it when powered-up again.
realised by: #REQ-DESIGN-CR-0446:02#REF#

#REQ-DESIGN-CR-0434#REF# 3.5.6.3
If no Radio Network identity received from trackside or from driver could have been memorized by ERTMS/ETCS on-board equipment (e.g. after a
System Failure or at very first power-up), this latter shall nevertheless order the registration of its Mobile Terminal(s) to a default Radio
Network.
#TEST-VAL-SUB026-5539#REF# FCT conf. automatic selection RadioNetworkId default value 0xFFFFFF (automatic selection) configured
#TEST-VAL-SUB026-5536#REF# FCT conf. specific value RadioNetworkId - selection of a radio network from the list

#REQ-DESIGN-CR-0435#REF# 3.5.6.5
On reception of the trackside order, ERTMS/ETCS on-board equipment shall immediately order the Radio Network registration of each Mobile
Terminal that fulfils the following conditions:
a)	it is not yet registered to the ordered Radio Network, AND
b)	it is not used for an established communication session, AND
c)	no safe radio connection is being set-up
#TEST-VAL-SUB026-3984#REF# FCT b) RX P45 no mobile available RadioNetworkId in RBC-RBC handover (1 mobile)
#TEST-VAL-SUB026-3989#REF# FCT b) RX P45 one out of two mobile available RadioNetworkId in RBC-RBC handover (2 mobiles)
#TEST-VAL-SUB026-3731#REF# FCT b) two mobiles available, a) reception of pkt45/42 (new network and old RBC) while OBU equipment already in session with old RBC
#TEST-VAL-SUB026-3850#REF# FCT c) Reception of new Radio Network registration during setup of safe connection

#REQ-UNISIG-SUB026-000999#REF# to.3.5.6.5
When a new Radio Network ID is entered by driver,  ERTMS/ETCS on-board equipment shall order the Radio Network registration of each Mobile
Terminal with the same conditions as reception from trackside, at the latest before the next safe radio connection establishement attempt is
started independ on an established session.
UNISIG clarification: the last extension is necessary, because the MN ID from driver should be immediately used.
TEST APPROACH:
The selection of a network by driver is associated with a scanning of the available radio networks.
The spanning process can unregister the mobile terminals und destroy existing safe connections.
A change of network registration of mobile is only possible without safe connection.

The following aspects have been identified:
1) Immediate registration without session
2) Registration during established session
3) Registration after session termination
#TEST-VAL-SUB026-5536#REF# FCT 1 RadioNetworkId - selection of a radio network from the list
#TEST-VAL-SUB026-7206#REF# FCT 2 Driver manually changes the level to 2 while communication session to another RBC already exists
#TEST-VAL-SUB026-5612#REF# FCT 3 Driver manually changes the level to 2 while communication session to another RBC already exists
#TEST-VAL-SUB026-3983#REF# EET error expectation OBU establishes session with same RBC but new network
#TEST-VAL-SUB026-4H98#REF# EET error expectation SoM PR with unknown position repeated with defined waiting time until RBC replies

#REQ-DESIGN-CR-0436#REF# 3.5.6.6
If a Mobile Terminal is not currently registered to the Radio Network ordered by trackside and if one of the conditions b) or c) is not
fulfilled, ERTMS/ETCS on-board equipment shall initiate the Radio Network registration once communication session is terminated and safe radio
connection is released.
#TEST-VAL-SUB026-3991#REF# FCT basic function Registration of RadioNetworkId - 1 mobile with existing connection

#REQ-DESIGN-CR-0437#REF# 3.5.6.7 #ANA-UNISIG-CR0007-0001:01#REF#
If no Mobile Terminal is duly registered to a Radio Network, any order to contact an RBC or an RIU received from trackside shall be rejected by
ERTMS/ETCS on-board equipment.

--- FINALISED ---
The case, that currently no Mobile Terminal is registered and no registration is enabled, cannot occur (see 3.5.6.3 and especailly note 2).
If no Mobile Terminal is duly registered, an order to contact an RBC or an RIU received from trackside should not be rejected - see analysis.
#ANA-UNISIG-CR0007-0001:01#REF#
realised by: #REQ-UNISIG-SUB026-3673:01#REF#
realised by: #REQ-DESIGN-CR-0767:01#REF#

#REQ-UNISIG-SUB026-3673:01#REF# to.3.5.6.7 #REQ-DESIGN-CR-0437#REF#
#ANA-UNISIG-CR0007-0001:01#REF#
If the on board receives an order to establish a connection to a RBC/RIU (P42, P131, P133) and no Mobile Terminal is duly registered to a Radio
Network, the establishment order shall be executed but the request to setup of safe radio connection shall be suppressed up until the network
registration is finished.

remark: The end criteria for repetition of request to setup the safe radio connection, which are defined in #REQ-UNISIG-SUB026-010275:01#REF#,
are valid in this case too.
UNISIG clarification:
see analysis
TEST APPROACH:
The following aspects have been identified:
1) P42 is received
2) P131 is received
3) P133 is received
The function radio infill is not part of R8, the verification of aspect 3 is hence omitted.
#TEST-VAL-SUB026-5807#REF# FCT 1 P42 establish communication session order is executed after network registration
#TEST-VAL-SUB026-5808#REF# FCT 2 P131 RBC transition order is executed after network registration
#TEST-VAL-SUB026-3983#REF# EET error expectation OBU establishes session with same RBC but new network

#REQ-DESIGN-CR-0767:01#REF# to.3.5.6.7 #REQ-DESIGN-CR-0437#REF#
#ANA-UNISIG-CR0007-0002#REF#
If radio network id is changed together with a session establishment order, a new radio network registration shall be started at first.
#TEST-VAL-SUB026-7945#REF# EET error expectation P42+P45 received right after P45(different radio network)
#TEST-VAL-SUB026-7144#REF# FCT one mobile (one engaged) Reception of P42/P45, changed data, communication session to other RBC up
#TEST-VAL-SUB026-3447#REF# FCT two mobiles (none engaged) processing of new pkt 41,42,45 while network registration (with another radio Network id) is running
#TEST-VAL-SUB026-3730#REF# FCT two mobiles (one engaged) reception of pkt45/42 (new network and RBC) while OBU equipment already in session with another RBC

#REQ-UNISIG-SUB026-001009#REF# 3.5.7.1
The ERTMS/ETCS on-board equipment shall inform the driver about the status of the safe radio connection. To that purpose, the following
indication statuses of the safe radio connection are defined: “No Connection”, “Connection Lost/Set-Up failed”, “Connection Up”.
#TEST-VAL-SUB026-3B33#REF# FCT basic function Connection Status on DMI: No Connection->Connection Lost[2]->Connection Up[4]

#REQ-UNISIG-SUB026-001011#REF# 3.5.7.2 #REQ-UNISIG-SUB026-010112#REF#
In addition, the ERTMS/ETCS on-board equipment shall use a “connection status” timer (see Appendix A.3.1), in order to manage properly the
transitions to the indication status “Connection Lost/Set-Up failed”.
realised by: #REQ-UNISIG-SUB026-001015#REF#
realised by: #REQ-UNISIG-SUB026-001019#REF#
realised by: #REQ-UNISIG-SUB026-010295#REF#

#REQ-UNISIG-SUB026-001015#REF# 3.5.7.3 #REQ-UNISIG-SUB026-001011#REF#
The ERTMS/ETCS on-board equipment shall start the “connection status” timer as soon as the first request to set-up a safe radio connection with
the relevant RBC/RIU is sent:
a)	for what regards the session establishment, see items b), c), d), e) in 3.5.3.4.
b)	for what regards maintaining a communication session, see 3.5.4.2 and 3.5.4.4
TEST APPROACH:
The following aspects were identified:
1) session establishment
1.1) 3.5.3.4 b)
1.2) 3.5.3.4 c)
1.3) 3.5.3.4 d)
1.4) 3.5.3.4 e)
2) maintain session 
2.1) 3.5.4.2
2.2) 3.5.4.4

Note: The timer supervision is started when the first request to set-up a safe radio connection is triggered. The actual sending of the request
is may delayed refer to remark in #REQ-UNISIG-SUB026-010277#REF#
#TEST-VAL-SUB026-3B33#REF# FCT 1.1 Connection Status on DMI: No Connection->Connection Lost[2]->Connection Up[4]
#TEST-VAL-SUB026-3B12#REF# FCT 1.2 Connection timer started when connection set-up begins due to mode change
#TEST-VAL-SUB026-3B36#REF# FCT 1.3 Connection timer started when connection set-up begins due to manual level change to L2
#TEST-VAL-SUB026-3B45#REF# FCT 1.4 Connection Status timer started at session establishment after leaving radio hole
#TEST-VAL-SUB026-3B37#REF# FCT 2.1 Connection Status on DMI: Connection Up->Connection Lost[2]->No Connection[3]
#TEST-VAL-SUB026-3B38#REF# FCT 2.2 Connection Status on DMI: Connection Up->No Connection[7]
#TEST-VAL-SUB026-3B41#REF# EET error expectation Connection Status on DMI: Connection Up->No Connection[6]

#REQ-UNISIG-SUB026-001019#REF# 3.5.7.4 #REQ-UNISIG-SUB026-001011#REF#
If the “connection status” timer is ongoing, it shall be stopped if the requests to set-up a safe radio connection are stopped with the relevant
RBC/RIU.
TEST APPROACH:
The following aspects have been identified, based on the state of the connection status at the time the connection status timer is started:
1) initial status: No Connection
2) initial status: Connection Up
#TEST-VAL-SUB026-3B47#REF# EET 1 Connection Status timer stopped if session establishment is stopped due to order to terminate session
#TEST-VAL-SUB026-3B38#REF# FCT 2 Connection Status on DMI: Connection Up->No Connection[7]
#TEST-VAL-SUB026-3B46#REF# EET error expectation Connection Status timer at session establishment with RBC1 stopped due to order to contact RBC2

#REQ-UNISIG-SUB026-001023#REF# 3.5.7.5
The ERTMS/ETCS on-board equipment shall execute the transitions between the different indication statuses of the safe radio connection with the
relevant RBC/RIU as described in Table 1 according to the conditions in Table 2 (see section 4.6.1 for details about the symbols).
"with the relevant RBC/RIU" means the supervising RBC/RIU
#DSC-UNISIG-SUB026-001025#REF#

Table 1: Transitions between the indication statuses of the safe radio connection #DSC-UNISIG-SUB026-001027#REF#
Table 2: Transition conditions for the indication statuses of the safe radio connection
realised by: #REQ-UNISIG-SUB026-010288#REF#
realised by: #REQ-UNISIG-SUB026-010289#REF#
realised by: #REQ-UNISIG-SUB026-010291#REF#
realised by: #REQ-UNISIG-SUB026-010290#REF#
realised by: #REQ-UNISIG-SUB026-010292#REF#
realised by: #REQ-UNISIG-SUB026-010293#REF#
realised by: #REQ-UNISIG-SUB026-010294#REF#
realised by: #REQ-UNISIG-SUB026-010295#REF#
realised by: #REQ-UNISIG-SUB026-010296#REF#
realised by: #REQ-UNISIG-SUB026-010297#REF#
realised by: #REQ-UNISIG-SUB026-010298#REF#
realised by: #REQ-UNISIG-SUB026-010299#REF#
realised by: #REQ-UNISIG-SUB026-010300#REF#

#REQ-UNISIG-SUB026-010288#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition table for indication status of the safe radio connection
from "No Connection" to "Connection Lost/Set-Up failed"
condition: 1, 2
priority: 2
#TEST-VAL-SUB026-3B34#REF# FCT [1] Connection Status on DMI: No Connection->ConnectionLost[1] at SoM
#TEST-VAL-SUB026-3B33#REF# FCT [2] Connection Status on DMI: No Connection->Connection Lost[2]->Connection Up[4]

#REQ-UNISIG-SUB026-010289#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition table for indication status of the safe radio connection
from "No Connection" to "Connection Up"
condition: 4
priority: 1
#TEST-VAL-SUB026-4337#REF# FCT basic function OBU establishes communication session and sends PR due to mode change FS->SR

#REQ-UNISIG-SUB026-010291#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition table for indication status of the safe radio connection
from "Connection Lost/Set-Up failed" to "No Connection"
condition: 3
priority: 2
#TEST-VAL-SUB026-3B37#REF# FCT basic function Connection Status on DMI: Connection Up->Connection Lost[2]->No Connection[3]

#REQ-UNISIG-SUB026-010290#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition table for indication status of the safe radio connection
from "Connection Lost/Set-Up failed" to "Connection Up"
condition: 4
priority: 1
#TEST-VAL-SUB026-3B33#REF# FCT basic function Connection Status on DMI: No Connection->Connection Lost[2]->Connection Up[4]

#REQ-UNISIG-SUB026-010292#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition table for indication status of the safe radio connection
from "Connection Up" to "No Connection"
condition: 5, 6, 7
priority: 1
#TEST-VAL-SUB026-4337#REF# FCT [5] OBU establishes communication session and sends PR due to mode change FS->SR
#TEST-VAL-SUB026-3B41#REF# FCT [6] Connection Status on DMI: Connection Up->No Connection[6]
#TEST-VAL-SUB026-3B38#REF# FCT [7] Connection Status on DMI: Connection Up->No Connection[7]

#REQ-UNISIG-SUB026-010293#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition table for indication status of the safe radio connection
from "Connection Up" to "Connection Lost/Set-Up failed"
condition: 2
priority: 2
#TEST-VAL-SUB026-3B37#REF# FCT basic function Connection Status on DMI: Connection Up->Connection Lost[2]->No Connection[3]

#REQ-UNISIG-SUB026-010294#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition condition for the indication status of the safe radio connection
condition[1]
(a Start of mission procedure is on-going) AND (the final attempt to set-up the safe radio connection failed)
#TEST-VAL-SUB026-3B34#REF# FCT basic function Connection Status on DMI: No Connection->ConnectionLost[1] at SoM

#REQ-UNISIG-SUB026-010295#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001011#REF#
#REQ-UNISIG-SUB026-001023#REF#
Transition condition for the indication status of the safe radio connection
condition[2]
(the “connection status” timer expires)
#TEST-VAL-SUB026-3B37#REF# FCT "Connection Up -> Connection Lost/Set-up Failed" Connection Status on DMI: Connection Up->Connection Lost[2]->No Connection[3]
#TEST-VAL-SUB026-3B33#REF# FCT "No Connection -> Connection Lost/Set-up Failed" Connection Status on DMI: No Connection->Connection Lost[2]->Connection Up[4]

#REQ-UNISIG-SUB026-010296#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition condition for the indication status of the safe radio connection
condition[3]
(no Start of mission procedure is on-going) AND (the requests to set-up a safe radio connection are stopped with the relevant RBC/RIU for reason
other than the successful set-up)
#TEST-VAL-SUB026-3B37#REF# FCT basic function Connection Status on DMI: Connection Up->Connection Lost[2]->No Connection[3]
#TEST-VAL-SUB026-7824#REF# EET error expectation Connection Status on DMI: No Connection->Connection Lost[1]->No Connection[3]
#TEST-VAL-SUB026-7825#REF# EET error expectation Connection Status on DMI: No Connection->Connection Lost[1]->No Connection[3]

#REQ-UNISIG-SUB026-010297#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition condition for the indication status of the safe radio connection
condition[4]
(the safe radio connection is set-up)
#TEST-VAL-SUB026-3B38#REF# FCT "Connection Lost/Set-up Failed -> Connection Up" Connection Status on DMI: Connection Up->No Connection[7]
#TEST-VAL-SUB026-4337#REF# FCT "No Connection -> Connection Up" OBU establishes communication session and sends PR due to mode change FS->SR

#REQ-UNISIG-SUB026-010298#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition condition for the indication status of the safe radio connection
condition[5]
(the safe radio connection is released)
"the safe radio connection is released" is interpreted as obu releases the connection
=> the answer from the other side is not more considered.
#TEST-VAL-SUB026-4337#REF# FCT basic function OBU establishes communication session and sends PR due to mode change FS->SR
#TEST-VAL-SUB026-3198#REF# EET error expectation NVCONTACT supervision, M_NVCONTACT=1 - Apply service brake

#REQ-UNISIG-SUB026-010299#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition condition for the indication status of the safe radio connection
condition[6]
(the safe radio connection is lost) AND (the requests to set-up a safe radio connection are stopped with the relevant RBC/RIU for reason other
than the successful set-up)
#TEST-VAL-SUB026-3B41#REF# FCT basic function Connection Status on DMI: Connection Up->No Connection[6]

#REQ-UNISIG-SUB026-010300#REF# 3.5.7.5 #REQ-UNISIG-SUB026-001023#REF#
Transition condition for the indication status of the safe radio connection
condition[7]
(the safe radio connection is lost) AND (the train front is inside an announced radio hole)
#TEST-VAL-SUB026-3B38#REF# FCT basic function Connection Status on DMI: Connection Up->No Connection[7]

#REQ-UNISIG-SUB026-001029#REF# 3.5.7.6
For the case of an RBC/RBC transition, the safe radio connection indicated to the driver shall switch from the indication status of the safe
radio connection with the Handing over RBC to the one with the Accepting RBC as soon as one of the following conditions is met:
a)	the ERTMS/ETCS on-board equipment sends a position report directly to the Accepting RBC with its maximum safe front end having passed
the border, see 3.15.1.3.5 (i.e. the Accepting RBC becomes the supervising RBC),
b)	the safe radio connection is released with the Handing over RBC and the minimum safe rear end of the train has crossed the border, see
3.5.5.1 e) and 3.15.1.2.7.
UNISIG clarification:
the change is only executed, when the RBC supervision is changed
realised by: #REQ-UNISIG-SUB026-001030:01#REF#

#REQ-UNISIG-SUB026-001030:01#REF# to.3.5.7.6 #REQ-UNISIG-SUB026-001029#REF#
For the case of an RBC/RBC transition, the safe radio connection indicated to the driver shall switch from the indication status of the safe
radio connection with the Handing over RBC to the one with the Accepting RBC as soon as one of the following conditions is met:
a) the supervision of the RBC is changed
b) the safe radio connection is released with the Handing over RBC and the max safe front end of the train has crossed the border.
TEST APPROACH:
Following aspects have been identified:
1) one mobile handover
1.1) connection to HO-RBC released before passing the RBC border with min safe rear end 
1.2) connection to HO-RBC released after passing the RBC border with min safe rear end 
1.3) connection to HO-RBC released when passing RBC border with max safe front end
1.4) connection to HO-RBC down when passing RBC border with max safe front end 
2) two mobile handover
2.1) outage of safe connection to HO-RBC
2.2) outage of safe connection to ACC-RBC 
#TEST-VAL-SUB026-3B49#REF# FCT 1.1 Safe Radio Connection indication: RTO(one mobile) lose safe radio connection with ACC-RBC before HO executed
#TEST-VAL-SUB026-3B39#REF# FCT 1.2 Safe Radio Connection indication status in case of RBC handover with one mobile
#TEST-VAL-SUB026-7181#REF# FCT 1.3 One mobile RBC/RBC handover HO-RBC orders session termination infront of RBC border
#TEST-VAL-SUB026-7182#REF# FCT 1.4 One mobile RBC/RBC handover connection to HO-RBC down when passing RBC border
#TEST-VAL-SUB026-3B40#REF# FCT 2.1 Safe Radio Connection indication in case of RBC handover with two mobiles
#TEST-VAL-SUB026-3B48#REF# FCT 2.2 Safe Radio Connection indication: RTO (two mobiles), lose safe connection to ACC RBC before handover executed
#TEST-VAL-SUB026-3B52#REF# EET error expectation Safe Radio Connection indication: RTO(one mobile) set-up failed with ACC-RBC after passing RT border

#REQ-UNISIG-SUB026-001035#REF# 3.5.7.7
For the case of safe radio connection with RIU’s, the safe radio connection indicated to the driver shall be the one related to the current
infill area.

Chapter 3.6

#REQ-UNISIG-SUB026-3354#REF# 3.6.1.3 #REQ-UNISIG-SUB026-1016:02#REF#
The Train Position information defines the position of the train front in relation to a balise group, which is called LRBG (the Last Relevant
Balise Group). It includes:
  The estimated train front end position, defined by the estimated distance between the LRBG and the front end of the train
  The train position confidence interval (see 3.6.4)
  Directional train position information in reference to the balise group orientation (see 3.4.2, also Figure 14) of the LRBG, regarding:
  A list of LRBGs, which may alternatively be used by trackside for referencing location dependent information (see 3.6.2.2.2 c)).
realised by: #REQ-UNISIG-SUB026-3147#REF#
realised by: #REQ-UNISIG-SUB026-3148#REF#
realised by: #REQ-UNISIG-SUB026-3149#REF#
realised by: #REQ-UNISIG-SUB026-3349#REF#
realised by: #REQ-UNISIG-SUB026-3151#REF#

#REQ-UNISIG-SUB026-3147#REF# to.3.6.1.3 #REQ-UNISIG-SUB026-3354#REF#
The Train Position information defines the position of the train front in relation to a balise group, which is called LRBG (last relevant balise
group).
#TEST-VAL-SUB026-4363#REF# FCT basic function PR at mode change to RV, PR at standstill in RV, determine train speed and location

#REQ-UNISIG-SUB026-3148#REF# to.3.6.1.3 #REQ-UNISIG-SUB026-3354#REF#
The Train Position information shall include the estimated train front end position, defined by the estimated distance between the LRBG and the
front end of the train.
#TEST-VAL-SUB026-4363#REF# FCT basic function PR at mode change to RV, PR at standstill in RV, determine train speed and location

#REQ-UNISIG-SUB026-3149#REF# to.3.6.1.3 #REQ-UNISIG-SUB026-3354#REF#
The Train Position information shall include the train position confidence interval (see 3.6.4).
#TEST-VAL-SUB026-4363#REF# FCT basic function PR at mode change to RV, PR at standstill in RV, determine train speed and location

#REQ-UNISIG-SUB026-3349#REF# to.3.6.1.3 #REQ-UNISIG-SUB026-3354#REF#
The Train Position Information shall include the directional train position information in reference to the balise group orientation (see 3.4.2,
also Figure 14) of the LRBG, regarding:
- the position of the train front end (nominal or reverse side of the LRBG)
- the train orientation
- the train running direction

Clarification:
In case of an LRBG being a single balise group with no co-ordinate system assigned, directional information is defined in reference to the pair
of LRBG and “previous LRBG”, see 3.4.2.3.3.
TEST APPROACH:
The following aspects have been identified:
1) single balise group 
1.1) with no co-ordinate system
1.2) with assigned co-ordinate system
2) multiple balise group
#TEST-VAL-SUB026-3668#REF# FCT 1.1 Train Location Information - Assignment of coordinate system
#TEST-VAL-SUB026-5848#REF# FCT 1.2 Train Position Information based on single balise group
#TEST-VAL-SUB026-4363#REF# FCT 2 PR at mode change to RV, PR at standstill in RV, determine train speed and location
#TEST-VAL-SUB026-3669#REF# EET error expectation Train location data - nominal/revers of LRBG
#TEST-VAL-SUB026-3677#REF# EET error expectation PR parameter and stored position according to last active cab in SL

#REQ-UNISIG-SUB026-3151#REF# to.3.6.1.3 #REQ-UNISIG-SUB026-3354#REF#
The Train Position information shall include a list of	LRBGs which may alternatively be used by trackside for referencing location dependent
information (see 3.6.2.2.2c).
TEST APPROACH:
The following aspects have been identified:
1) single balise group 
1.1) with no co-ordinate system
1.2) with assigned co-ordinate system
2) multiple balise group
#TEST-VAL-SUB026-3667#REF# FCT 1.1 Train Location Information - list of LRBGs (N_TOTAL =0)
#TEST-VAL-SUB026-3668#REF# FCT 1.2 Train Location Information - Assignment of coordinate system
#TEST-VAL-SUB026-3666#REF# FCT 2 Train Location Information - list of LRBGs (N_TOTAL !=0)
#TEST-VAL-SUB026-3915#REF# EET error expectation Validity of Last eight reported BG identities after closing of desk during SoM

#REQ-UNISIG-SUB026-3155#REF# to.3.6.1.3 #ANA-UNISIG-TLD-0005#REF#
The infomation about the balisegroups into the list of LRBGs which may alternatively be used by trackside shall be included the LRBG Data
referenced in #REQ-UNISIG-SUB026-3153#REF#.
#TEST-VAL-SUB026-3667#REF# FCT N_TOTAL =0 Train Location Information - list of LRBGs (N_TOTAL =0)
#TEST-VAL-SUB026-3666#REF# FCT N_TOTAL >0 Train Location Information - list of LRBGs (N_TOTAL !=0)

#REQ-UNISIG-SUB026-3156#REF# to.3.6.1.3 #ANA-UNISIG-TLD-0006#REF#
Aufgrund der Anforderung in SUBSET-026, 3.4.2.3.3.8 ist es notwendig, bei Senden eines Spezial-Positionreports an das RBC neben den in
#REQ-UNISIG-SUB026-3153#REF#  genannten Daten auch die mit gesendete previous LRBG in Bezug zur LRBG zu sichern.
#TEST-VAL-SUB026-7131#REF# FCT basic function Co-ordinate system assignment accepted depending on list of reported BGs

#REQ-UNISIG-SUB026-3152#REF# to.3.6.1.3 #ANA-UNISIG-TLD-0001#REF#
The Train position information shall be included the current LRBG and the previuos LRBG with their LRBG Data.
TEST APPROACH:
The following aspects have been identified:
1) single balise group
2) multiple balise group
#TEST-VAL-SUB026-7670#REF# FCT 1 LRBG and previous LRBG in position report
#TEST-VAL-SUB026-3666#REF# FCT 2 Train Location Information - list of LRBGs (N_TOTAL !=0)

#REQ-UNISIG-SUB026-3153#REF# to.3.6.1.3 #ANA-UNISIG-TLD-0002#REF#
The LRBG Data shall be included
- ETCS ID
- reference position
- orientation of the balisegroup
- train orientation during crossing the balisegroup
- direction of train movement during crossing the balisegroup
TEST APPROACH:
The following aspects have been identified:
1) single balise group 
1.1) with no co-ordinate system
1.2) with assigned co-ordinate system
2) multiple balise group
#TEST-VAL-SUB026-3667#REF# FCT 1.1 Train Location Information - list of LRBGs (N_TOTAL =0)
#TEST-VAL-SUB026-3668#REF# FCT 1.2 Train Location Information - Assignment of coordinate system
#TEST-VAL-SUB026-3666#REF# FCT 2 Train Location Information - list of LRBGs (N_TOTAL !=0)
#TEST-VAL-SUB026-3669#REF# EET error expectation Train location data - nominal/revers of LRBG
#TEST-VAL-SUB026-3677#REF# EET error expectation PR parameter and stored position according to last active cab in SL

#REQ-UNISIG-SUB026-3154#REF# to.3.6.1.3 #ANA-UNISIG-TLD-0003#REF#
The Train Position information shall be included their actual state. The state can be valid, invalid or unknown.
#TEST-VAL-SUB026-4211#REF# FCT state INVALID not stored SoM location invalid - set to unknown when leaving SB
#TEST-VAL-SUB026-4209#REF# FCT state UNKNOWN, state VALID train location information stored remanent at standstill

#REQ-UNISIG-SUB026-2302#REF# 3.6.1.4
Balise groups, which are marked as unlinked, shall never be used as LRBG.
#TEST-VAL-SUB026-3033#REF# FCT basic function Gelinkte und ungelinkte BGs

#REQ-UNISIG-SUB026-3729#REF# 3.6.1.5
If there is an active cab, this one defines the orientation of the train, i.e. the side of the active cab shall be considered as the front of
the train. If no cab is active, the train orientation shall be as when a cab was last active.
#TEST-VAL-SUB026-3827#REF# FCT basic function No cab is active - train orientation according to last active cab

#REQ-UNISIG-SUB026-3730#REF# zu.3.6.1.5
If the last active cab is not ascertainable, cab A shall be used as default value.
Remark:
A default CAB must be defined, when the last active cab cannot determined.
#TEST-VAL-SUB026-3828#REF# FCT basic function If the last active cab is not ascertainable, cab A used as default value

#REQ-UNISIG-SUB026-0013#REF# 3.6.2.1.1
All location and profile data transmitted by a balise shall refer to the location reference and orientation of the balise group to which the
balise belongs.
#TEST-VAL-SUB026-3036#REF# FCT basic function Processing information from different transmission sources in relation to Q_DIR

#REQ-UNISIG-SUB026-0014#REF# 3.6.2.2.1
All location and profile data transmitted from the RBC shall refer to the location reference and orientation of the LRBG given in the same
message.
#TEST-VAL-SUB026-3036#REF# FCT basic function Processing information from different transmission sources in relation to Q_DIR

#REQ-UNISIG-SUB026-0439:01#REF# 3.6.2.2.2
For the LRBG the following requirements have to be met:
a)	The on-board equipment shall use the last balise group passed as a reference when reporting its position to the RBC (in the following
termed as LRBGONB). Only
  balise groups marked as linked and contained in the previously received linking information, if linking information is used on-board
  the last balise group not marked as unlinked, if no linking was used when this balise group was passed
b)	The RBC shall use the last relevant balise group which was reported by the on-board equipment as a reference (in the following termed as
LRBGRBC). At a certain moment LRBGRBC and LRBGONB can be different.
c)	The on-board equipment shall be able to accept information referring to one of at least eight LRBGONB last reported to the RBC.

--- FINALISED ---
part b is only trackside
realised by: #REQ-UNISIG-SUB026-3157#REF#
realised by: #REQ-UNISIG-SUB026-3159#REF#

#REQ-UNISIG-SUB026-3157#REF# 3.6.2.2.2.a #REQ-UNISIG-SUB026-0439:01#REF#
The on-board equipment shall use the last balise group passed as a reference when reporting its position to the RBC. Only
∙	balise groups marked as linked and contained in the previously received linking information, if linking information is used on-board
or
∙	the last balise group not marked as unlinked, if no linking was used when this balise group was passed
shall be regarded.
#TEST-VAL-SUB026-3033#REF# FCT basic function Gelinkte und ungelinkte BGs

#REQ-UNISIG-SUB026-3159#REF# 3.6.2.2.2.c #REQ-UNISIG-SUB026-0439:01#REF#
The on-board equipment shall be able to accept information referring to one of at least eight LRBGONB last reported to the RBC.
#TEST-VAL-SUB026-5211#REF# EET error expectation Level transition L2, processing of buffered RBC message, ref BG for buffer message not in the list of the last 8 BGs anymore
#TEST-VAL-SUB026-3915#REF# FCT multiple balise BGs Validity of Last eight reported BG identities after closing of desk during SoM
#TEST-VAL-SUB026-3007#REF# FCT single balise BGs 1. von 8 ueberfahrenen SBG's wird als LRBG akzeptiert

#REQ-UNISIG-SUB026-3748#REF# 3.6.2.2.2.c #ANA-UNISIG-RBC-Message-Consistency-0001#REF#
Exception to #REQ-UNISIG-SUB026-3159#REF#
The acceptance check with the reported LRBG shall not be executed with following messages:
- Initiation of a communication session (Message 38)
- Configuration Determination (Message 32)
- Acknowledgement of termination of a communication session (Message 39)
- Unconditional Emregency Stop (Message 16)
TEST APPROACH:
The following aspects were identified:
1) Initiation of a communication session (Message 38)
2) Configuration Determination (Message 32)
3) Acknowledgement of termination of a communication session (Message 39)
4) Unconditional Emregency Stop (Message 16)
4.1) as normal priority data
4.2) as high priority data
#TEST-VAL-SUB026-3840#REF# FCT 1, 2, 3, 4.1 The acceptance check of the reported LRBG not executed for M38, M32, M39 and M16
#TEST-VAL-SUB026-8291#REF# FCT 4.2 Evaluation of ES with unknown NID_LRBG

#REQ-UNISIG-SUB026-3160#REF# zu.3.6.2.2.2.c #ANA-UNISIG-TLD-0007#REF#
Die Liste der an das RBC gesendeten LRBGs darf jede Balisengruppe nur einmal führen.
Bei erneuter Überfahrt einer Balisengruppe und Senden dieser als LRBG an das RBC  ist der bisherige Eintrag der Balisengruppe zu löschen und die
Balisengruppe als neue LRBG aufzunehmen.
Klarstellung: Diese Anforderung gilt trotz SUBSET-026, 3.4.2.3.3.8 und des daraus resultierenden notwendigen Erkennens des Sendens einer Single
Balise als LRBG mit unterschiedlichen previous LRBG.
#TEST-VAL-SUB026-3667#REF# FCT N_TOTAL =0 Train Location Information - list of LRBGs (N_TOTAL =0)
#TEST-VAL-SUB026-3666#REF# FCT N_TOTAL >0 Train Location Information - list of LRBGs (N_TOTAL !=0)

#REQ-DESIGN-CR-0069#REF# 3.6.2.2.2.1
Exception to a): When on-board position is unknown or when position data has been deleted during SoM procedure, the on-board equipment shall use
an LRBG identifier set to "unknown" until the onboard has validated its position again by passing a balise group.
#TEST-VAL-SUB026-4211#REF# FCT position deleted during SoM SoM location invalid - set to unknown when leaving SB
#TEST-VAL-SUB026-3946#REF# FCT position is unknown Message acceptability when NID_LRBG set as Un Known for the Packet 72

#REQ-DESIGN-CR-0070#REF# 3.6.2.2.2.3
Regarding c): From the time it has reported an unknown position, or an invalid position during SoM procedure, to the time it has received from
the RBC a message with an LRBG not set to “unknown”, the on-board equipment shall also be able to accept messages from the RBC containing LRBG
“unknown”.
#TEST-VAL-SUB026-3946#REF# FCT basic function Message acceptability when NID_LRBG set as Un Known for the Packet 72

#REQ-DESIGN-CR-0497:01#REF# to.3.6.2.2.2.3 #ANA-UNISIG-TLD-0008:01#REF#
The on board shall accepts the following information received from RBC with NID_LRBG=UNKNOWN:
-	SR Authorisation
(Note: The distance to run in SR in the SR-Authorisation refers to the estimated train front end, not to the LRBG).
-	Recognition of Exit from Trip Mode
-	Acknowledgement of Train Data
-	Unconditional Emergency Stop
-	Revocation of Emergency Stop
-	SH refused
-	SH authorized
-	Configuration Determination
-	Initiation of a Communication Session
-	Acknowledgement of termination of a communication session
-	Train Rejected
-	Train Accepted
-	SoM position report confirmed by RBC
-	National Values, if they are valid for both directions as well as to be performed upon receipt (D_VALIDNV=0 or now)
-	Level Transition Order, if it is valid for both directions as well as to be performed upon receipt (D_LEVELTR=now)
-	Session Management, if it is valid for both directions
-	Data used by applications outside the ETCS system, if it is valid for both directions
-	Radio Network Registration, if it is valid for both directions
-	List of balises for SH Area, if it is valid for both directions
-	MA Request Parameters, if they are valid for both directions
-	Position Report Parameters, if they are valid for both directions, unless they are defining at least one specific location for sending a
position report (N_ITER=0)
-	List of balises in SR Authority, if it is valid for both directions
-	Inhibition of revocable TSRs from Balise, if it is valid for both directions
-	Revocation of Temporary Speed Restriction, if it is valid for both directions
-	Plain Text message, if it is valid for both directions, unless the start condition is distance limited
-	Fixed Text Message, if it is valid for both directions, unless the start condition is distance limited
-	Train Running Number from RBC, if it is valid for both directions

The above-named information, if the conditions are not fullfilled, and all not named information shall be ignored without an error reaction,
when they are received from RBC with NID_LRBG=UNKNOWN.
Exception:  REQ-UNISIG-SUB026-008495 applies for  for optional packets in a shifted ma.
TEST APPROACH:
1.1) National Values, if they are valid for both directions as well as to be performed upon receipt (D_VALIDNV=0 or now)
1.1.1) D_VALIDNV=0
1.1.2) D_VALIDNV=now
1.2) Level Transition Order, if it is valid for both directions as well as to be performed upon receipt (D_LEVELTR=now)
1.2.1) D_LEVELTR=0
1.2.2) D_LEVELTR=now
1.3) Session Management, if it is valid for both directions
1.4) Data used by applications outside the ETCS system, if it is valid for both directions
1.5) Radio Network Registration, if it is valid for both directions
1.6) MA Request Parameters, if they are valid for both directions
1.7) Position Report Parameters, if they are valid for both directions as well as to be performed upon receipt("now"), unless they are defining
at least one specific location for sending a position report (N_ITER=0)
1.7.1) dependency on Q_DIR
1.7.2) dependency on D_LOC
1.8) List of balises in SR Authority, if it is valid for both directions
1.9) Inhibition of revocable TSRs from Balise, if it is valid for both directions
1.10) Revocation of Temporary Speed Restriction, if it is valid for both directions
1.11) Plain Text message, if it is valid for both directions, unless the start condition is distance limited
1.11.1) dependency on Q_DIR
1.11.2) dependency on start condition
1.12) Fixed Text Message, if it is valid for both directions, unless the start condition is distance limited
1.12.1) dependency on Q_DIR
1.12.2) dependecy on start condition
1.13) Train Running Number from RBC, if it is valid for both directions
1.14) SR Authorisation
1.15) Recognition of Exit from Trip Mode
1.16) Acknowledgement of Train Data
1.17) Unconditional Emergency Stop
1.18) Revocation of Emergency Stop
1.19) SH refused
1.20) SH authorized
1.21) List of balises for SH Area, if it is valid for both directions
1.22) RBC/RIU System Version
1.23) Initiation of a Communication Session
1.24) Acknowledgement of termination of a communication session
1.25) Train Rejected
1.26) Train Accepted
1.27) SoM position report confirmed by RBC
2) conditions are not fulfilled for the above-named information, but message is received with LRBG unknown
3) not named information received with LRBG unknown
3.1) Messages with D_REF, Conditional Emrgency Stop, MA with Shifted Location Reference, TAF Request covered by #REQ-UNISIG-SUB026-008495#REF#
3.2) Other information
3.2.1) Linking
3.2.2) Movement Authority
3.2.3) Gradient Profile 
3.2.4) International SSP 
3.2.5) Axle Load speed profile 
3.2.6) Temporary Speed Restriction
3.2.7) Route Suitability Data
3.2.8) Adhesion Factor
3.2.9) Geographical Position
3.2.10) RBC Transition Order 
3.2.11) Assignment of Co-ordinate system
3.2.12) Track Conditions excluding big metal masses
3.2.13) Co-operative shortening of MA
3.2.14) Reversing Area Information, Reversing Supervision Information
3.2.15) Permitted Braking Distance Information
3.2.16) Level Crossing information
#TEST-VAL-SUB026-3958#REF# FCT 1.1.1 Message acceptability when LRBG set to unknown using National Values
#TEST-VAL-SUB026-7795#REF# FCT 1.1.2 Message acceptability when LRBG set to unknown using National Values
#TEST-VAL-SUB026-3939#REF# FCT 1.2.1, 1.2.2 Message acceptability when LRBG set to unknown using level transition order
#TEST-VAL-SUB026-3940#REF# FCT 1.3 Message acceptability when LRBG set to unknown using session management
#TEST-VAL-SUB026-8145#REF# FCT 1.4 Message acceptability when NID_LRBG set as unknown for P44 (ATO)
#TEST-VAL-SUB026-3985#REF# FCT 1.5 Radio Network Registration acceptability when message has Unknown LRBG
#TEST-VAL-SUB026-3964#REF# FCT 1.6 Acceptance of MA request parameters with unknown LRBG
#TEST-VAL-SUB026-3943#REF# FCT 1.7.1 Message acceptability when LRBG set to unknown using Position Report Parameters
#TEST-VAL-SUB026-3679#REF# FCT 1.7.2 Reception of Position Report Parameter with unknown LRBG
#TEST-VAL-SUB026-3944#REF# FCT 1.8, 1.14 Message acceptability when NID_LRBG set as unknown for the Packet 63 in RadioMsg 2
#TEST-VAL-SUB026-7798#REF# FCT 1.9 Message acceptability when NID_LRBG set as unknown for P64
#TEST-VAL-SUB026-3945#REF# FCT 1.10 Message acceptability when LRBG set to unknown using TSR revocation packet
#TEST-VAL-SUB026-3946#REF# FCT 1.11.1, 1.11.2 Message acceptability when NID_LRBG set as Un Known for the Packet 72
#TEST-VAL-SUB026-3947#REF# FCT 1.12.1, 1.12.2 Message acceptability when NID_LRBG set as Un Known for the Packet 76
#TEST-VAL-SUB026-3948#REF# FCT 1.13 Message acceptability when NID_LRBG set as unknown for the Packet 140
#TEST-VAL-SUB026-3949#REF# FCT 1.15 Message acceptability when LRBG set to unknown using recognition of exit from trip mode
#TEST-VAL-SUB026-3950#REF# FCT 1.16 Message acceptability when NID_LRBG set as unknown for the RadioMsg 8
#TEST-VAL-SUB026-3952#REF# FCT 1.17, 1.18 Message acceptability when LRBG set to unknown using revocation of emergency stop
#TEST-VAL-SUB026-3953#REF# FCT 1.19 Message acceptability when NID_LRBG set as unknown for the RadioMsg 27
#TEST-VAL-SUB026-3954#REF# FCT 1.20 Message acceptability when NID_LRBG set as unknown for the RadioMsg 28
#TEST-VAL-SUB026-3941#REF# FCT 1.21 Message acceptability when NID_LRBG set as unknown for the Packet 49 in RadioMsg 28
#TEST-VAL-SUB026-7799#REF# FCT 1.22, 1.23, 1.24 Message acceptability when NID_LRBG set as unknown for M32, M38 and M39
#TEST-VAL-SUB026-3955#REF# FCT 1.25 Message acceptability when NID_LRBG set as Un Known for the RadioMsg 40
#TEST-VAL-SUB026-3956#REF# FCT 1.26 Message acceptability when NID_LRBG set as unknown for the RadioMsg 41
#TEST-VAL-SUB026-3957#REF# FCT 1.27 Message acceptability when NID_LRBG set as unknown for the RadioMsg 43
#TEST-VAL-SUB026-7796#REF# FCT 2 Message acceptability when LRBG set to unknown using level transition order
#TEST-VAL-SUB026-8273#REF# FCT 3.2.1, 3.2.3, 3.2.6, 3.2.7, 3.2.8, 3.2.9, 3.2.10, 3.2.13, 3.2.14, 3.2.15, 3.2.16 Information received from RBC with NID_LRBG=UNKNOWN
#TEST-VAL-SUB026-5849#REF# FCT 3.2.2, 3.2.4, 3.2.11, 3.2.12 Rejection of location depending messages with an LRBG set to 'unknown'
#TEST-VAL-SUB026-3942#REF# FCT 3.2.5 Message acceptability when LRBG set to unknown using Axle Load Speed Profile
#TEST-VAL-SUB026-7797#REF# EET error expectation Message acceptability when NID_LRBG set as unknown for P44
#TEST-VAL-SUB026-7900#REF# EET error expectation Message acceptability when NID_LRBG set as unknown for P64

#REQ-UNISIG-SUB026-0015#REF# 3.6.2.3.1 #REQ-UNISIG-SUB026-0366#REF#
All location and profile data transmitted as infill information shall refer to the location reference of the balise group at the next main
signal (identified by the infill information) and to the orientation given by the infill device. (See note after justification).
#TEST-VAL-SUB026-3316#REF# EET CFX00031905 Linking im Infill
#TEST-VAL-SUB026-8040#REF# EET CFX00034621 Fahrzeugreaktion auf Infill-Information
#TEST-VAL-SUB026-3035#REF# FCT basic function Acceptance of infill regarding the orientation and location of Infill Devices
#TEST-VAL-SUB026-3712#REF# EET error expectation Infill MA and related mode profile, end of the actual MA in front of Infill Location Reference Point
#TEST-VAL-SUB026-8005#REF# EET error expectation Infill information evaluated in relation to infill location reference

#REQ-UNISIG-SUB026-001124#REF# 3.6.2.4.2
The orientation of data transmitted by a loop is determined by the EOLM information which indicates how the directional information contained in
loop messages is to be interpreted.
#TEST-VAL-SUB026-7675#REF# FCT basic function Evaluation of orientation of data transmitted by a loop

#REQ-UNISIG-SUB026-0016#REF# 3.6.3.1.1
The direction for which transmitted information is valid shall refer to:
a)	the direction of the LRBG for information sent by radio
b)	the direction of the balise group sending the information.
#TEST-VAL-SUB026-3036#REF# FCT basic function Processing information from different transmission sources in relation to Q_DIR

#REQ-UNISIG-SUB026-0441:01#REF# 3.6.3.1.3 #REQ-UNISIG-SUB026-3120:01#REF#
When receiving information from any transmission medium, the ERTMS/ETCS on-board equipment shall only take into account information valid for
its orientation. Other information shall be ignored. Exception: for SL, PS and SH engines, balise group crossing direction shall be considered.
TEST APPROACH:
NOTE: the aspects in the test cases will be listed as pairs (mode, train_orientation, information_direction, crossing_direction), based on the
following equivalence classes:

Mode: Different_than_SL_PS_SH, SL, PS, SH
TrainOrientation: A, B
InfoOrientation: nominal, reverse
CrossingDir: nominal, reverse

For example (FS, A, nominal, nominal).
#TEST-VAL-SUB026-3350#REF# EET CFX00034192 Setzen der Positionevent für Leveltransition im SL Mode bei Rückwärtsfahrt
#TEST-VAL-SUB026-3346#REF# EET CFX00034196 BMM in Mode Shunting D_TRACKCOND/=0 - train running in nominal dir
#TEST-VAL-SUB026-3347#REF# EET CFX00034196 BMM in Mode Shunting D_TRACKCOND/=0 - train running in revers dir
#TEST-VAL-SUB026-7582#REF# EET CFX00035641 Auswertung D_TRACKCOND und D_VALIDNV in SH
#TEST-VAL-SUB026-7594#REF# EET CFX00035641 D_TRACKCOND (BG) in SL
#TEST-VAL-SUB026-5139#REF# EET CFX00035800 Level transition in SL, Orientierung A, BG in Nominalrichtung, D_LEVELTR=32767
#TEST-VAL-SUB026-5140#REF# EET CFX00035800 Level transition in SL, Orientierung B, BG in Nominalrichtung, D_LEVELTR=32767
#TEST-VAL-SUB026-5141#REF# EET CFX00035800 Level transition von L1 nach L2, SL, Orientierung A, BG in Nominalrichtung, D_LEVELTR=0
#TEST-VAL-SUB026-5142#REF# EET CFX00035800 Level transition von L1 nach L2, SL, Orientierung B, BG in Nominalrichtung, D_LEVELTR=0
#TEST-VAL-SUB026-5143#REF# EET CFX00035800 Level transition in Mode SL, Orientierung A, BG in Reverse-Richtung, D_LEVELTR=0
#TEST-VAL-SUB026-5144#REF# EET CFX00035800 Level transition in Mode SL, Orientierung B, BG in Reverse-Richtung, D_LEVELTR=0
#TEST-VAL-SUB026-5145#REF# EET CFX00035800 Level transition in Mode SL, Orientierung A, BG in Reverse-Richtung, D_LEVELTR=32767
#TEST-VAL-SUB026-5146#REF# EET CFX00035800 Level transition in Mode SL, Orientierung B, BG in Reverse-Richtung, D_LEVELTR=32767
#TEST-VAL-SUB026-3416#REF# EET CFX00035927 Wirksamkeit von D_VALIDNV aus P3 mit Q_DIR=reverse im Mode SH
#TEST-VAL-SUB026-3417#REF# EET CFX00035927 Usage of D_VALIDNV Q_DIR=reverse in SL
#TEST-VAL-SUB026-3549#REF# EET CFX00035927 BMM area, train orientation A, moving direction A, D_TRACKCOND=0
#TEST-VAL-SUB026-3550#REF# EET CFX00035927 BMM area, train orientation B, moving direction B, D_TRACKCOND=0
#TEST-VAL-SUB026-3551#REF# EET CFX00035927 BMM area, train orientation B, moving direction A, D_TRACKCOND=0
#TEST-VAL-SUB026-3552#REF# EET CFX00035927 BMM area, train orientation A, moving direction B, D_TRACKCOND=0
#TEST-VAL-SUB026-3555#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung A, Orientierung A, Mode SR
#TEST-VAL-SUB026-3556#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung B, Orientierung B, Mode SR
#TEST-VAL-SUB026-3557#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung A, Orientierung A, Mode SL
#TEST-VAL-SUB026-3560#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung B, Orientierung B, Mode SH
#TEST-VAL-SUB026-3561#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung B, Orientierung A, Mode SH
#TEST-VAL-SUB026-3562#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung A, Orientierung B, Mode SH
#TEST-VAL-SUB026-3563#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung A, Orientierung A, Mode SH
#TEST-VAL-SUB026-3564#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung B, Orientierung B, Mode SH
#TEST-VAL-SUB026-3565#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung B, Orientierung A, Mode SH
#TEST-VAL-SUB026-3566#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung A, Orientierung B, Mode SH
#TEST-VAL-SUB026-3567#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung A, Orientierung A, Mode SL
#TEST-VAL-SUB026-3568#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung B, Orientierung B, Mode SL
#TEST-VAL-SUB026-3571#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung A, Orientierung A, Mode SL, BG in Reverse-Richtung
#TEST-VAL-SUB026-3572#REF# EET CFX00035927 Uebernahme neuer National values bei D_VALIDNV>0, Fahrtrichtung B, Orientierung B, Mode SL, BG in Reverse-Richtung
#TEST-VAL-SUB026-3353#REF# EET CFX00038911 Balisenempfang im Stillstand (Ortungsfehler)
#TEST-VAL-SUB026-3036#REF# ECT FS, A, *, * Processing information from different transmission sources in relation to Q_DIR
#TEST-VAL-SUB026-4H95#REF# ECT FS, B, *, * Train orientation considered for information received in FS mode
#TEST-VAL-SUB026-7705#REF# FCT PS, A, reverse, reverse Balise group crossing direction shall be considered when receiving information in PS mode
#TEST-VAL-SUB026-7704#REF# FCT PS, B, *, * Balise group crossing direction shall be considered when receiving information in PS mode
#TEST-VAL-SUB026-3576#REF# FCT SH, A, nominal, * , CFX00035927 Auswertung Packet 132 bei BG in Nominal direction, Fahrtrichtung A+B, Orientierung A, Mode SH
#TEST-VAL-SUB026-3574#REF# FCT SH, A, reverse, * , CFX00035927 Auswertung Packet 132 bei BG in Reverse direction Fahrtrichtung A, Fahrtrichtung A+B, Orientierung A, Mode SH
#TEST-VAL-SUB026-3577#REF# FCT SH, B, nominal, * , CFX00035927 Auswertung Packet 132 bei BG in Nominal direction, Fahrtrichtung A+B, Orientierung B, Mode SH
#TEST-VAL-SUB026-3575#REF# FCT SH, B, reverse, * , CFX00035927 Auswertung Packet 132 bei BG in Reverse direction Fahrtrichtung A, Fahrtrichtung A+B, Orientierung B, Mode SH
#TEST-VAL-SUB026-3929#REF# FCT SL, A, nominal, * Balise group crossing direction is valid in SL mode
#TEST-VAL-SUB026-3569#REF# FCT SL, A, reverse, * , CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung A+B, Orientierung A, Mode SL
#TEST-VAL-SUB026-3558#REF# FCT SL, B, nominal, * , CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung B+A, Orientierung B, Mode SL
#TEST-VAL-SUB026-3570#REF# FCT SL, B, reverse, * , CFX00035927 Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung B+A, Orientierung B, Mode SL
#TEST-VAL-SUB026-3407#REF# EET error expectation Direction evaluation for RBC messages in SL
#TEST-VAL-SUB026-3559#REF# EET error expectation Uebernahme neuer National values bei D_VALIDNV=0, Fahrtrichtung A, Orientierung A, Mode SH
#TEST-VAL-SUB026-4318#REF# EET error expectation PT/L2 acceptence (Q_DIR evaluation) of MA, SSP, GP
#TEST-VAL-SUB026-4322#REF# EET error expectation RV/L1 acceptence (Q_DIR evaluation) of NV
#TEST-VAL-SUB026-4329#REF# EET error expectation PT/L2 acceptence (Q_DIR evaluation) of Level Transition Order and Position Report Parameters

#REQ-UNISIG-SUB026-001143#REF# 3.6.3.1.3.1
If the train position is unknown, data received from any transmission medium valid for one direction only (nominal or reverse) shall be rejected
by the ERTMS/ETCS on-board equipment. Data valid for both directions shall be evaluated (see section 4.8).
realised by: #REQ-DESIGN-CR-0317#REF#

#REQ-DESIGN-CR-0317#REF# to.3.6.3.1.3.1 #REQ-UNISIG-SUB026-001143#REF#
#REQ-UNISIG-SUB026-0442:01#REF#
If the train location in relation to the orienatation of the reference balise group is unknown, data received from any transmission medium valid
for one direction only (nominal or reverse) shall be rejected by the ERTMS/ETCS on-board equipment. Data valid for both directions shall be
evaluated (see section 4.8).
UNISIG clarification: train psoition is too unspecific
The 2 relevant points (single balise without orientation and unknown train position) are covered with this clarification
TEST APPROACH:
The following aspects have been identified:
1) information from single balise group
2) information from RBC reference single balise group
3) information from RBC reference two balise group treated as single balise group (3.4.2.4.1) 
#TEST-VAL-SUB026-3037#REF# FCT 1 Q_DIR-Test single balise BG(mit Q_LINK=1)
#TEST-VAL-SUB026-5850#REF# FCT 2 Acceptance of RBC data with reference single balise group without co-ordinate system
#TEST-VAL-SUB026-5852#REF# FCT 3 Two balises duplicating each other treated as a single balise group in case only one balise is correctly read
#TEST-VAL-SUB026-3252#REF# EET CFX00031244 Linkdaten übernehmen bei Single BG ohne Koordinatensystem (Q_DIR=BOTH)
#TEST-VAL-SyAnfSpezCR-0081#REF# EET error expectation No co-ordinate system has been assigned, reception of Information with Q_DIR=2 from BG/RBC in SL
#TEST-VAL-SyAnfSpezCR-0082#REF# EET error expectation No co-ordinate system has been assigned, reception of Information with Q_DIR=1 from BG in SL
#TEST-VAL-SyAnfSpezCR-0083#REF# EET error expectation No co-ordinate system has been assigned, reception of Information with Q_DIR=1 from BG in SL
#TEST-VAL-SyAnfSpezCR-0084#REF# EET error expectation No co-ordinate system has been assigned, reception of Information with Q_DIR=0 from BG in SL
#TEST-VAL-SyAnfSpezCR-0085#REF# EET error expectation No co-ordinate system has been assigned, reception of Information with Q_DIR=0 from RBC in SL

#REQ-UNISIG-SUB026-0442:01#REF# 3.6.3.1.4
If no co-ordinate system has been assigned to a single balise group, data transmitted by trackside, which refers to that balise group requiring
the co-ordinate system to be known (i.e. all data which are only valid for one direction (nominal or reverse)) shall be rejected by the
ERTMS/ETCS on-board equipment. Data valid for both directions shall be evaluated (see section 4.8).
realised by: #REQ-DESIGN-CR-0317#REF#

#REQ-UNISIG-SUB026-001148#REF# 3.6.3.1.4.1
Exception: if not rejected due to balise group message consistency check (see 3.16.2.4.4.1 and 3.16.2.5.1.1), data to be forwarded to a National
System (see section 3.15.6) shall be accepted. Justification: the co-ordinate system of the balise group might be known to the National System
by other means inherent to the National System itself.
Rel. 8.0:
P44 to be forwarded to a NTC should be ignored

UNISIG clarification:
this exception is related not only for balise information,

P44 to be forwarded to NTC from RBC and RIU are meant too.

#REQ-UNISIG-SUB026-0017#REF# 3.6.3.2.1
Location and profile data shall have the structure shown in Figure 12 below
see figure 12 also
#DSC-UNISIG-SUB026-001155#REF#

Figure 12: General Structure of location and profile data
realised by: #REQ-UNISIG-SUB026-0443:01#REF#
realised by: #REQ-UNISIG-SUB026-0444#REF#
realised by: #REQ-UNISIG-SUB026-0445#REF#
realised by: #REQ-UNISIG-SUB026-0447#REF#

#REQ-UNISIG-SUB026-0443:01#REF# 3.6.3.2.2 #REQ-UNISIG-SUB026-0017#REF#
With regard to Figure 12 the following applies to continuous profile data:
a)	Value (n) shall be valid for distance (n+1)
b)	For distance (1) the previously received data shall be used (in case of an SSP this includes train length delay, refer to 3.11.3.1.3).
c)	Distances shall be given as unsigned incremental values representing the distance between value(n) and value(n-1).
d)	The last value (n) transmitted shall be valid for an unlimited distance unless value(n) represents a special "end of profile"
value.
e)	If distance (n+1) = 0 then the corresponding profile value n shall still be taken into account.
see figure 12 also

is relevant for GA, SSP and Route Suitability information

point e)
former comment remains valid: 
"Wenn Nulllängenabschnitte kommandiert werden, werden sie in einen Abschnitt minimaler Länge von 1 cm umgewandelt und der nachfolgende
Abschnitt wird dahingehend verkürzt.
"
#DSC-UNISIG-SUB026-001155#REF#

Figure 12: General Structure of location and profile data
#TEST-VAL-SUB026-4H44#REF# EET CFX00037582 Revocation of slippery area by P71 M_ADHESION=1 with same start point as former commanded slippery area
#TEST-VAL-SUB026-3038#REF# ECT a), c) Continuous Profile Data
#TEST-VAL-SUB026-3925#REF# FCT b) Train length effect on Static speed pofile elements
#TEST-VAL-SUB026-3062#REF# FCT d MA acceptance depending on SSP/GP coverage
#TEST-VAL-SyAnfSpezCR-0015#REF# ECT e mehrteiliges SSP senden, wobei einmal die Distanz 0 vorkommt

#REQ-UNISIG-SUB026-0444#REF# 3.6.3.2.3 #REQ-UNISIG-SUB026-0017#REF#
With regard to Figure 12 the following shall apply to location data:
a)	Distances shall be given as unsigned incremental values representing the distance between value(n) and value(n-1).
b)	For distance (1) the previously received data shall be used.
c)	Each value (n) may represent a single value or a set of data.
see figure 12 also

is relevant for packet 58
#TEST-VAL-SUB026-3039#REF# ECT basic function Locations

#REQ-UNISIG-SUB026-0445#REF# 3.6.3.2.4 #REQ-UNISIG-SUB026-0017#REF#
According to Figure 12 the structure for non-continuous profile data shall allow to contain multiple elements (value(n) for length(n)) inside
the profile.
a)	Distance to the start of each element (value(n) for length(n)) shall be given as unsigned incremental values, each increment
representing the distance between  starts of element (n) and element (n-1).
b)	For distance (1) the previously received data (or initial data/default values, see section 3.7) shall be used.
c)	Each value (n) may represent a single value or a set of data.
d)	Note: There is no relationship between length of element (n-1) and distance (n), i.e., elements may overlap.
see figure 12 also
TEST APPROACH:
Non-continuous profile data comprises information from packets P51, P52, P67, P68, P69, P70, P80.

Point a) is tested comprehensively via multiple iterations in the same packet.
Point b) is covered by verification of #REQ-UNISIG-SUB026-0468:01#REF#.
Point c) and d) distinguish between overlapping and non-overlapping elements.

P68: Same kind and different kind of TCs is distinguished. 
The aspect P68 with overlapping TCs of same kind is covered by verification of #REQ-UNISIG-SUB026-3644#REF#. The verification of this aspect is
omitted here.

P80: Same kind and different kind of MPs is distinguished.
The aspect P80 with overlapping MPs is covered by verification of #REQ-UNISIG-SUB040-3040:01#REF#. The verification of this aspect is omitted
here.

P70: If at least one unsuitability exists, the closest location corresponding to the unsuitability is considered as both the EOA and SvL.
Unsuitability's behind this location are of no interested. The aspect P70 is covered by the verification of #REQ-UNISIG-SUB026-0552:03#REF#. The
verification of this aspect is omitted here.

P69 is omitted, as TC 'Station Platforms' is not part of R8.0
#TEST-VAL-SUB026-3B07#REF# FCT P51 Considering axle load speed restrictions based on train axle load
#TEST-VAL-SUB026-5928#REF# FCT P52 - non-overlapping New PBD replaces old PBD taking D_PBDSR/D_TRACKINIT into account
#TEST-VAL-SUB026-3B09#REF# FCT P52 - overlapping overlapping PBDSR profiles
#TEST-VAL-SUB026-3B10#REF# FCT P67 TC BMM given as non-continuous profile data
#TEST-VAL-SUB026-3B08#REF# ECT P68 Same/different kind of track conditions given as non-continuous profile data
#TEST-VAL-SUB026-5949#REF# FCT P80(different kind) - non-overlapping Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind
#TEST-VAL-SUB026-5948#REF# FCT P80(same kind) non-overlapping Evaluation of MP acknowledgment requests for two non overlapping MP areas of same kind
#TEST-VAL-SUB026-3999#REF# EET error expectation Shifted location reference for (non) continuous profile data

#REQ-UNISIG-SUB026-010556#REF# to.3.6.3.2.4
In case the trackside commands a non continuous speed profile with length zero, the onboard shall supervise the shortest length (greater zero)
it can internally handle, instead of zero length.
UNISIG clarification: a non contionouos profile element with length 0 have to be taken into account also

separate requirements exists for tc and mode profile
#TEST-VAL-SUB026-7076#REF# ECT basic function Managment of P52 with L_PBDSR = 0

#REQ-UNISIG-SUB026-0446#REF# 3.6.3.2.5
It shall be possible for the RBC to shift the location reference, e.g., after a change of train orientation or running direction.
#TEST-VAL-SUB026-3402#REF# EET CFX00034324 Shifted MA and Linking
#TEST-VAL-SUB026-3403#REF# EET CFX00034324 Shifted MA and Linking (2)
#TEST-VAL-SUB026-3596#REF# EET error expectation MA with Shifted Location Reference - ref. BG passed with different train orientation (with antenna switch)
#TEST-VAL-SUB026-3295#REF# FCT shift the location reference after a change of running direction Message 33 in PT
#TEST-VAL-SUB026-3595#REF# FCT shift the location reference after a change of train orientation Linking in MA with Shifted Location Reference - ref. BG passed with different train orientation (with antenna switch)
#TEST-VAL-SUB026-3928#REF# FCT shift the location reference without change of train orientation or running direction MA with shifted location reference - no change of orientation,direction

#REQ-UNISIG-SUB026-0447#REF# 3.6.3.2.6 #REQ-UNISIG-SUB026-0017#REF#
With regards to Figure 12 the following applies to linking information
a)	The distance (1) shall be given to the first balise group included in the linking information
b)	The distance (n) shall be given as the distance between two consecutive balise groups
c)	Each value (n) shall represent the linking information related to that balise group.

#DSC-UNISIG-SUB026-001155#REF#

Figure 12: General Structure of location and profile data
#TEST-VAL-SUB026-3039#REF# FCT basic function Locations

#REQ-UNISIG-SUB026-3482#REF# 3.6.4.1
All location related information transmitted from trackside equipment shall be used by the on-board equipment taking into account the confidence
interval to the train position, if required for safe operation.
realised by: #REQ-UNISIG-SUB026-005901:01#REF#

#REQ-UNISIG-SUB026-005901:01#REF# to.3.6.4.1 #REQ-UNISIG-SUB026-3482#REF#
#REQ-UNISIG-SUB026-0448:01#REF#
#REQ-DESIGN-CR-0588:01#REF#
#ANA-UNISIG-Location-0101#REF#
To determine the distance between a location reference and the current train front end position the algorithm defined in
#DSC-ACT-SWAnf_Distance-0016:01#REF# and #DSC-TBL-SWAnf_Distance-0016:01#REF# must be used.
TEST APPROACH:
Following aspects have been identified:
1) location reference
1.1) unlinked BG
1.2) linked BG no linking information available
1.3) linked BG linking information available
2) distance calcultaion for 
2.1) min safe front end
2.2) estimated front end
2.3) max front end
3) distance calculation for 
3.1) cab A
3.2) cab B
4) movement direction, train orientation
4.1) not changed
4.2) changed
#TEST-VAL-SUB026-3700#REF# FCT 1.1, 1.2 no linking information available - supervision track condition and Svl/EoA Q_LINK=0/1
#TEST-VAL-SUB026-3683#REF# FCT 1.3 Measured distance unequal D_Link - forward synchronization
#TEST-VAL-SUB026-3701#REF# EET 2.1, 2.3 supervision EoA/SvL and TC - ODO variance smaller than Q_POSACC/Q_LOCACC (default Q_POSACC< Q_LOCACC)
#TEST-VAL-SUB026-3375#REF# FCT 2.2 Backward reference without error, linked BG1 and BG2 between L2 announcment and transition location
#TEST-VAL-SUB026-3547#REF# FCT 3.1 Supervision TC from L2(RBC)/orientation A
#TEST-VAL-SUB026-3548#REF# FCT 3.2 Supervision TC from L2(RBC)/orientation B
#TEST-VAL-SUB026-3697#REF# FCT 4.1 mixed track (linked/unlinked) BG supervision level transition location and SvL/EoA
#TEST-VAL-SUB026-3698#REF# FCT 4.2 supervision of level transition location, SvL/EoA and TC ref. BG passed with different train orientation
#TEST-VAL-SUB026-3371#REF# EET CFX00035058 Backward reference, D_REF=100, BG1L BG2L BG5NL Levelt., BG3L, BG4L, Pos. BG3L++ <D_LINK
#TEST-VAL-SUB026-3372#REF# EET CFX00035058 Backward reference, D_REF=100, BG1L BG2L BG5NL Levelt., BG3L, BG4L, Pos. BG3L-- <D_LINK
#TEST-VAL-SUB026-3373#REF# EET CFX00035058 Backward reference without error, no balise beween L2 announcment and transition location
#TEST-VAL-SUB026-3374#REF# EET CFX00035058 Backward reference without error, linked BG1 beween L2 announcment and transition location
#TEST-VAL-SUB026-3376#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L BG2L BG5NL level transition, BG3L, BG4L
#TEST-VAL-SUB026-3377#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L, BG5NL, BG2L, level transition., BG3L, BG4L
#TEST-VAL-SUB026-3378#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L BG2L BG5NL level transition., BG3L, BG4L, Pos. BG3L++ >D_LINK
#TEST-VAL-SUB026-3379#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L BG2L BG5NL level transition., BG3L, BG4L, Pos. BG3L-- >D_LINK
#TEST-VAL-SUB026-3383#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L, BG2L, BG5NL, leveltransition, BG3L, BG4L, Pos. BG3++ <D_LINK
#TEST-VAL-SUB026-3384#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L, BG2L, BG5NL, level transition, BG3L, BG4L, Pos. BG3-- <D_LINK
#TEST-VAL-SUB026-3385#REF# EET CFX00035058 Backward reference, D_REF=0, level transition, BG3L, BG4L, Pos. BG3++ <D_LINK
#TEST-VAL-SUB026-3386#REF# EET CFX00035058 Backward reference, D_REF=0, level transition., BG3L, BG4L, Pos. BG3-- <D_LINK
#TEST-VAL-SUB026-3387#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L, BG5NL, BG2L, level transition, BG3L, BG4L, Pos. BG3++ <D_LINK
#TEST-VAL-SUB026-3388#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L, BG5NL, BG2L, level transition, BG3L, BG4L, Pos. BG3-- <D_LINK
#TEST-VAL-SUB026-3389#REF# EET CFX00035058 Backward reference, D_REF=0, BG1L BG2L BG5NL level transition, new MA, BG3L, BG4L
#TEST-VAL-SUB026-3539#REF# EET CFX00038703 Supervision TSR from L1(Balise)/orientation A
#TEST-VAL-SUB026-3639#REF# EET CFX00038703 TSR in L1(Balise)/train orientation A, reset of confidence interval
#TEST-VAL-SUB026-3851#REF# EET error expectaion processing of linking information if confidence interval greater than linking distance
#TEST-VAL-SUB026-3380#REF# EET error expectation Shifted Location Reference with D_REF=0
#TEST-VAL-SUB026-3381#REF# EET error expectation Shifted Location Reference with D_REF>0
#TEST-VAL-SUB026-3382#REF# EET error expectation Shifted Location Reference with D_REF<0
#TEST-VAL-SUB026-3536#REF# EET error expectation Confidence interval and position calculation, orientation B, L1 MA
#TEST-VAL-SUB026-3695#REF# EET error expectation Measured distance unequal D_Link - forward/backward synchronization
#TEST-VAL-SUB026-3696#REF# EET error expectation EoA, SVL and TC supervision with broken link chain
#TEST-VAL-SUB026-3702#REF# EET error expectation Impact ODO_RES on confidence interval
#TEST-VAL-SUB026-3704#REF# EET error expectation SSP supervision - SSP from BG and RBC (different BG ref.)
#TEST-VAL-SUB026-3853#REF# EET error expectation Reception of MA with Shifted Location Reference in SB - L_ENDSECTION smaller than D_REF
#TEST-VAL-SUB026-4323#REF# EET error expectation Processing of MA from unlinked BG
#TEST-VAL-SUB026-4H35#REF# EET error expectation Repositioning BG reference for L_SECTION
#TEST-VAL-SUB026-5841#REF# EET error expectation Distance calculation based on changing Q_NVLOCACC

#REQ-UNISIG-SUB026-0448:01#REF# 3.6.4.2
The confidence interval to the train position shall refer to the distance to the LRBG and shall take into account
a)	On-board over-reading amount and under-reading amount (odometer accuracy plus the error in detection of the balise group location
reference)
b)	The location accuracy of the LRBG.
realised by: #REQ-UNISIG-SUB026-005901:01#REF#
realised by: #REQ-UNISIG-SUB026-005904#REF#

#REQ-DESIGN-CR-0588:01#REF# 3.6.4.2.1
Distance information received from trackside shall be evaluated on-board as nominal information (without taking into account any tolerances).
realised by: #REQ-UNISIG-SUB026-005901:01#REF#

#REQ-UNISIG-SUB026-005904#REF# to.3.6.4.2 #REQ-UNISIG-SUB026-0448:01#REF#
#ANA-UNISIG-Location-0100#REF#
As position accuracy of a balise group the following sum must be used:
Q_POSACC = Q_LOCACC + Q_DETACC + ODO_RES
Q_LOCACC is the location accuracy for the balise group according to UNISIG
Q_DETACC is the detection accuracy of the balise channel (1m)
ODO_RES is the value from the odometry for the location of the balise group
TEST APPROACH:
Following aspects have been identified:
1) dependency on ODO_RES
2) dependency on Q_LOCACC
2.1) Q_NVLOCACC
2.2) Q_LOCACC from P5
#TEST-VAL-SUB026-3702#REF# FCT 1 Impact ODO_RES on confidence interval
#TEST-VAL-SUB026-5838#REF# FCT 2.1, 2.2 Variable test Q_NVLOCACC

#REQ-DESIGN-CR-0107:01#REF# 3.6.4.2.3
The value of the Location Accuracy shall be determined by Linking information if available, if not, by the corresponding National Value, or the
corresponding Default Value if the National Value is not applicable.
TEST APPROACH:
Following aspects have been identified:
1) Q_LOCACC according to Q_NVLOCACC
2) Q_LOCACC according to Q_LOCACC from P5
#TEST-VAL-SUB026-5838#REF# FCT 1, 2 Variable test Q_NVLOCACC
#TEST-VAL-SUB026-5839#REF# EET error expectation Q_NVLOCACC and Q_LOCACC
#TEST-VAL-SUB026-5854#REF# EET error expectation Distance calculation based on changing P5 Q_LOCACC from reference BG

#REQ-UNISIG-SUB026-001191#REF# 3.6.4.3
When another balise group becomes the LRBG or when evaluating (see section 4.8) location related trackside information, which is referred to a
previously received balise group different from the LRBG, all the location related information shall be relocated by subtracting from the
distances that are counted from the reference balise group of the location related information:
a)	the distance between the reference balise group of the location related information and the LRBG, retrieved from linking information if
it is available and it includes both the reference balise group and the LRBG, OR
b)	in all other cases, the estimated travelled distance between the reference balise group of the location related information and the
LRBG.
UNISIG clarification:for repo BGs  point b is relevant (see UNISIG notes from 12.03.2012, 4.25)

new resynchronisation of the location is not to be realized. The current realization should remain applicable.
#DSC-UNISIG-SUB026-001206#REF#

Figure 13a: Reset of confidence interval and relocation, on change of LRBG
realised by: #REQ-UNISIG-SUB026-0449#REF#

#REQ-UNISIG-SUB026-0449#REF# 3.6.4.3.(old) #REQ-UNISIG-SUB026-001191#REF#
The confidence interval shall be reset taking the location accuracy into account, when the next linked balise group has been read.
TEST APPROACH:
Following aspects have been identified:
1) confidence interval after passing unlinked BG
2) confidence interval after passing linked BG no linking information available
3) confidence interval after passing linked BG linking information available
#TEST-VAL-SUB026-3547#REF# FCT 1, 2 Supervision TC from L2(RBC)/orientation A
#TEST-VAL-SUB026-3043#REF# FCT 3 Dependency of location accuraccy on P5 Q_LOCACC

#REQ-UNISIG-SUB026-3658#REF# to.3.6.4.3.(old) #ANA-UNISIG-Location-0001#REF#
Exception to 3.6.4.3:
If received new linking information, the location of the overrunning annunced balisegroups and the confidence interval shall be recalculated.
dient dazu, die Rückwärtssynchronisation auszulösen. Wie die Berechnung erfolgt, legen die Req. der Ortungsprinzipien fest
#DSC-UNISIG-SUB026-001208#REF#

Figure 13b: Relocation of trackside information referred to previously passed balise group, different from the current LRBG
TEST APPROACH:
Following aspects have been identified:
1) messured distance euquals D_LINK (test focus confidence interval recalculated)
2) messured distance does not agrees with linking distance (test focus location recalculated)
2.1) messured distance greater than D_LINK
2.2) measured distance smaller than D_LINK
#TEST-VAL-SUB026-8260#REF# FCT 1 Backward snchronisation D_LINK agrees with messured distance
#TEST-VAL-SUB026-8261#REF# FCT 2.1 Backward snchronisation D_LINK greater than messured distance
#TEST-VAL-SUB026-8262#REF# FCT 2.2 Backward snchronisation D_LINK smaller than messured distance

#REQ-UNISIG-SUB026-0450:01#REF# 3.6.4.4
The train front end position shall be identified in the following way
a)	The estimated front end position.
b)	The max(imum) safe front end position, differing from the estimated position by the under-reading amount in the distance measured from
the LRBG plus the location accuracy of the LRBG.
I.e. in relation to the orientation of the train this position is in advance of the estimated position.
c)	The min(imum) safe front end position, differing from the estimated position by the over-reading amount in the distance measured from
the LRBG plus the location accuracy of the LRBG.
I.e. in relation to the orientation of the train this position is in rear of the estimated position.

#DSC-UNISIG-SUB026-001217#REF#

Figure 13c: Train confidence interval and train front end position
realised by: #REQ-UNISIG-SUB026-005905#REF#
realised by: #REQ-UNISIG-SUB026-005951#REF#
realised by: #REQ-UNISIG-SUB026-005952:01#REF#
realised by: #REQ-UNISIG-SUB026-005959:01#REF#
realised by: #REQ-UNISIG-SUB026-005960:01#REF#
realised by: #REQ-UNISIG-SUB026-006147#REF#
realised by: #REQ-UNISIG-SUB026-006148#REF#
realised by: #REQ-UNISIG-SUB026-006149#REF#
realised by: #REQ-UNISIG-SUB026-006150#REF#
realised by: #REQ-UNISIG-SUB026-005961:01#REF#

#REQ-UNISIG-SUB026-005905#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0200#REF#
Coordinates of locations must have the following properties:
Backward, Middle, Forward
TEST APPROACH:
Following aspects have been identified:
1) usage of Backward
2) usage of Middle
3) usage of Forward
#TEST-VAL-SUB026-8263#REF# FCT 1, 2, 3 Supervision based on location coordinates and current train front end position (Q_LINK=1)

#REQ-UNISIG-SUB026-005951#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0201#REF#
The current train front end position must be represented by the following values:
MinSafeFrontEnd, EstimatedFrontEnd, MaxSafeFrontEnd
TEST APPROACH:
Following aspects have been identified:
1) usage of MinSafeFrontEnd
2) usage of EstimatedFrontEnd
3) usage of MaxSafeFrontEnd
#TEST-VAL-SUB026-8263#REF# FCT 1, 2, 3 Supervision based on location coordinates and current train front end position (Q_LINK=1)

#REQ-UNISIG-SUB026-005952:01#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0210:01#REF#
The condition "Did the train travel safely less than a supervised distance from a reference location" must be checked by calculating
the difference between MaxSafeFrontEnd and Backward of the reference location.
MaxSafeFrontEnd < Backward_Reference + SupervisedDistance
TEST APPROACH:
Following aspects have been identified:
1) reference BG Q_LINK=0 
2) reference BG Q_LINK=1 
#TEST-VAL-SUB026-8264#REF# FCT 1 Supervision based on location coordinates and current train front end position (Q_LINK=0)
#TEST-VAL-SUB026-8263#REF# FCT 2 Supervision based on location coordinates and current train front end position (Q_LINK=1)
#TEST-VAL-SUB026-3358#REF# EET error expectation BMM area supervision in SR Modus Level 1 (P67 from BG with Q_LINK=0)

#REQ-UNISIG-SUB026-005959:01#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0211:01#REF#
The condition "Did the train travel safely more than a supervised distance from a reference location" must be checked by calculating
the difference between MinSafeFrontEnd and Forward of the reference location.
Forward_Reference + SupervisedDistance < MinSafeFrontEnd
TEST APPROACH:
Following aspects have been identified:
1) reference BG Q_LINK=0 
2) reference BG Q_LINK=1 
#TEST-VAL-SUB026-8264#REF# FCT 1 Supervision based on location coordinates and current train front end position (Q_LINK=0)
#TEST-VAL-SUB026-8263#REF# FCT 2 Supervision based on location coordinates and current train front end position (Q_LINK=1)
#TEST-VAL-SUB026-3358#REF# EET error expectation BMM area supervision in SR Modus Level 1 (P67 from BG with Q_LINK=0)
#TEST-VAL-SUB026-3852#REF# EET error expectation Reception of MA with Shifted Location Reference in SB - min safe front end has passed EoA already

#REQ-UNISIG-SUB026-005960:01#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0212:01#REF#
The condition "Did the train travel nominal the supervised distance from a reference location" must be checked by calculating the
difference between EstimatedFrontEnd and Middle of the reference location.
Middle_Reference + SupervisedDistance == EstimatedFrontEnd
TEST APPROACH:
Following aspects have been identified:
1) reference BG Q_LINK=0 
2) reference BG Q_LINK=1 
#TEST-VAL-SUB026-8264#REF# FCT 1 Supervision based on location coordinates and current train front end position (Q_LINK=0)
#TEST-VAL-SUB026-8263#REF# FCT 2 Supervision based on location coordinates and current train front end position (Q_LINK=1)

#REQ-UNISIG-SUB026-006147#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0220#REF#
The reference location that is used as LRBG is called the current reference location.
For the current reference location the values of Backward, Middle, and Forward must always have the same value.
TEST APPROACH:
Following aspects have been identified:
1) 'Did the train travel safely less than a supervised distance from a reference location' 
2) 'Did the train travel nominal the supervised distance from a reference location'
3) 'Did the train travel safely more than a supervised distance from a reference location'
#TEST-VAL-SUB026-8265#REF# FCT 1, 2, 3 Reference location that used for current reference location

#REQ-UNISIG-SUB026-006148#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0221#REF#
The value for Backward, Middle, and Forward of all reference locations that are connected through linking information must not change when a new
reference location is added and becomes the current reference location, if this new reference location is connected through linking information
with the other reference locations.
TEST APPROACH:
Following aspects have been identified:
1) 'Did the train travel safely less than a supervised distance from a reference location' 
2) 'Did the train travel nominal the supervised distance from a reference location'
3) 'Did the train travel safely more than a supervised distance from a reference location'
#TEST-VAL-SUB026-8266#REF# FCT 1, 2, 3 Reference location that used for current reference location

#REQ-UNISIG-SUB026-006149#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0222#REF#
The value for Middle of all reference locations must not change when a new reference location is added (even if it becomes the current reference
location), if this new reference location is not connected through linking information with any other reference location.
#TEST-VAL-SUB026-8265#REF# FCT basic function Reference location that used for current reference location

#REQ-UNISIG-SUB026-006150#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0223#REF#
It must be considered, that the values of Backward, Middle, and Forward for reference locations may change when additional information about the
reference locations is used (e.g. a new reference location is added or linking information for existing reference locations becomes valid).
TEST APPROACH:
Following aspects have been identified:
1) new reference location
2) new linking information
#TEST-VAL-SUB026-8263#REF# FCT 1 Supervision based on location coordinates and current train front end position (Q_LINK=1)
#TEST-VAL-SUB026-3695#REF# FCT 2 Measured distance unequal D_Link - forward/backward synchronization
#TEST-VAL-SUB026-3699#REF# FCT CFX00039740 linking backward synchronization due to mode change

#REQ-UNISIG-SUB026-005961:01#REF# to.3.6.4.4 #REQ-UNISIG-SUB026-0450:01#REF#
#ANA-UNISIG-Location-0230#REF#
To calculate the coordinates of the reference locations and the current train front end position the algorithm defined in
#DSC-ACT-SWAnf_Coordinate-0017#REF# and #DSC-TBL-SWAnf_Coordinate-0017:01#REF# must be used.
TEST APPROACH:
Following aspects have been identified:
1) reference BG Q_LINK=0 
2) reference BG Q_LINK=1
#TEST-VAL-SUB026-8264#REF# FCT 1 Supervision based on location coordinates and current train front end position (Q_LINK=0)
#TEST-VAL-SUB026-8263#REF# FCT 2 Supervision based on location coordinates and current train front end position (Q_LINK=1)
#TEST-VAL-SUB026-3696#REF# EET error expectation EoA, SVL and TC supervision with broken link chain

#REQ-UNISIG-SUB026-001225#REF# 3.6.4.7.1
By exception to clause 3.6.1.3, the train position is referred to this balise group marked as unlinked. The ERTMS/ETCS on-board equipment shall
temporarily apply by analogy clauses 3.6.4.2, 3.6.4.2.1, 3.6.4.2.3 and 3.6.4.4 to determine an additional confidence interval, until a further
received balise group becomes the LRBG or the location related information is deleted on-board.
new resynchronisation of the location is not to be realized. The current realization should remain applicable.

#REQ-UNISIG-SUB026-001227#REF# 3.6.4.7.2
If another balise group marked as unlinked is received before the additional confidence interval is deleted:
a)	the additional confidence interval shall be reset in relation to this new balise group marked as unlinked
b)	the location related information referred to the previous balise group marked as unlinked shall be relocated by subtracting the
estimated travelled distance between both balise groups from the distances that are counted from this previous balise group marked as unlinked.
new resynchronisation of the location is not to be realized. The current realization should remain applicable.

#REQ-UNISIG-SUB026-0019#REF# 3.6.5.1.1
The position shall refer to the front end of the respective engine with regards to the train orientation.
#TEST-VAL-SUB026-3667#REF# FCT N_TOTAL =0 Train Location Information - list of LRBGs (N_TOTAL =0)
#TEST-VAL-SUB026-3666#REF# FCT N_TOTAL >0 Train Location Information - list of LRBGs (N_TOTAL !=0)

#REQ-UNISIG-SUB026-0453:01#REF# 3.6.5.1.2
The position report shall contain at least the following position and direction data
a)	The distance between the LRBG and the estimated front end of the train.
b)	The distance from the estimated front end position to the min safe front end position and the distance from the estimated front end
position to the max safe front end position.
c)	The identity of the location reference, the LRBG.
d)	The orientation of the train in relation to the LRBG orientation.
Note: Driver selected running direction is only handled by the on-board system.
e)	The position of the front end of the train in relation to the LRBG (nominal or reverse side of the LRBG).
f)	The estimated speed
g)	Train integrity information.
h)	Direction of train movement in relation to the LRBG orientation
i)	Optionally, the previous LRBG (see 3.4.2.3.3).
see following figure 14 also
#DSC-UNISIG-SUB026-001250#REF#

Figure 14: Information given in a position report (two examples to show the relation between LRBG and train orientation)
#TEST-VAL-SUB026-3666#REF# FCT P0 Train Location Information - list of LRBGs (N_TOTAL !=0)
#TEST-VAL-SUB026-3281#REF# FCT P1 PR parameter - after passing BG (N_TOTAL /=0) and BG (N_TOTAL =0)

#REQ-UNISIG-SUB026-3240:01#REF# to.3.6.5,.Figure.14 #ANA-UNISIG-PR-0002:01#REF#
The direction information for Positionreport Paket 0 shall be determined accordingly Decision Table #DSC-TBL-SendPR-0002:01#REF#.
Rel. 6.4: Festlegung der Ermittlung der Q-Werte für Paket 0
TEST APPROACH:
The table defined by #DSC-TBL-SendPR-0002:01#REF# consists of 44 lines each line is one test aspect.
The normal operation scenarios are covered by specific test cases outline here (line 1-33). The special scenarios are covered by module test
(line 34-44).
#ANALYSE-VALUNISIG-5266#REF# FCT The module linking determines the direction information of balise groups with a known orientation according to decision table #DSC-TBL-SendPR-0002:01#REF#. Verification takes place via linking module test.
#TEST-VAL-SUB026-3669#REF# FCT 1 Train location data - nominal/revers of LRBG
#TEST-VAL-SUB026-3674#REF# FCT 2, 3, 4, 5, 6, 7, 8, 9 position report direction information in pkt0 - nominal BG orientation (2, 3, 4, 5, 6, 7, 8, 9, 45)
#TEST-VAL-SUB026-3671#REF# FCT 10, 11, 12, 13, 14, 15, 16, 17 position report direction information in pkt0 - nominal BG orientation (10, 11, 12, 13, 14, 15, 16, 17)
#TEST-VAL-SUB026-3666#REF# FCT 18 Train Location Information - list of LRBGs (N_TOTAL !=0)
#TEST-VAL-SUB026-3673#REF# FCT 18, 19, 20, 21, 22, 23, 24, 25 position report direction information in pkt0 - reverse BG orientation (18, 19, 20, 21, 22, 23, 24, 25)
#TEST-VAL-SUB026-3672#REF# FCT 26, 27, 28, 29, 30, 31, 32, 33 position report direction information in pkt0 - reverse BG orientation (26, 27, 28, 29, 30, 31, 32, 33)
#TEST-VAL-SUB026-3670#REF# FCT 34 position report direction information in pkt0 - nominal BG orientation D_LRBG=0, pkt58 with T_CYCLOC=0
#TEST-VAL-SUB026-7599#REF# EET CFX00038141 Orientation information within PR pkt 1 based on in SL passed balise
#TEST-VAL-SUB026-7600#REF# EET error expectation PR (pkt0) - active cab A/B - one antenna for both cabs configured

#REQ-UNISIG-SUB026-3241:01#REF# to.3.6.5 #REQ-UNISIG-SUB026-3216#REF#
#REQ-UNISIG-SUB026-3217#REF#
#REQ-UNISIG-SUB026-3218#REF#
#ANA-UNISIG-PR-0003:01#REF#
The direction information for Positionreport Paket 1 shall be determined accordingly Decision Table #DSC-TBL-SendPR-0003:01#REF#.
Festlegung der Ermittlung der Q-Werte für Paket 1
TEST APPROACH:
The table defined by #DSC-TBL-SendPR-0003:01#REF# consists of 26 lines each line is one test aspect.
The normal operation scenarios are covered by specific test cases outline here (line 1-17). The special scenarios are covered by module test
(line 18-26).
#TEST-VAL-SUB026-3668#REF# FCT 1 Train Location Information - Assignment of coordinate system
#TEST-VAL-SUB026-3675#REF# FCT 2, 3, 4, 5, 6, 7, 8, 9 position report direction information in pkt1 (2, 3, 4, 5, 6, 7, 8, 9)
#TEST-VAL-SUB026-3676#REF# FCT 10, 11, 12, 13, 14, 15, 16, 17 position report direction information in pkt1 (10, 11, 12, 13, 14, 15, 16, 17, 21)
#TEST-VAL-SUB026-7595#REF# EET CFX00038141 Orientation information within PR pkt 1 based on in SL passed balise
#TEST-VAL-SUB026-7596#REF# EET CFX00038141 Orientation information within PR pkt 1 based on in PT passed balise
#TEST-VAL-SUB026-7597#REF# EET CFX00038141 Orientation information within PR pkt 1 based on in SH passed balise
#TEST-VAL-SUB026-7598#REF# EET CFX00038141 Orientation information within PR pkt 1 based on in RV passed balise
#TEST-VAL-SUB026-3678#REF# EET error expectation position report direction information in pkt1 - D_LRBG=0
#TEST-VAL-SUB026-4516#REF# EET error expectation previous LRBG and all PR directional information set to unknown after passing new BG with different running direction - orientation unchanged
#TEST-VAL-SUB026-4517#REF# EET error expectation previous LRBG and all PR directional information set to unknown after passing new BG with different running direction - orientation changed
#TEST-VAL-SUB026-4518#REF# EET error expectation PR parameter after passing single BG after change of running direction and trian orientation

#REQ-UNISIG-SUB026-3243#REF# to.3.6.5.1.2 #REQ-UNISIG-SUB026-3217#REF#
#REQ-UNISIG-SUB026-3218#REF#
#ANA-UNISIG-PR-0005#REF#
If the LRBG unknown the value for the variables D_LRBG and L_DOUBTOVER/ L_DOUTUNDER shall be set UNKWOWN.
#TEST-VAL-SUB026-4516#REF# FCT LRBG deletetd previous LRBG and all PR directional information set to unknown after passing new BG with different running direction - orientation unchanged
#TEST-VAL-SUB026-3338#REF# FCT no BG passed yet position report, if packet 58 was received with reference LRBG_unknown (without location dependency)

#REQ-UNISIG-SUB026-0455:01#REF# 3.6.5.1.4
The on-board equipment shall send position reports as requested by the RBC in the position report parameters. In addition, it shall also send a
position report if at least one of the events listed hereafter occurs:
a)	The train reaches standstill, if applicable to the current mode.
b)	The mode changes.
c)	The driver confirms train integrity.
d)	A loss of train integrity is detected.
e)	The train passes a RBC/RBC border with its min safe rear end.
f)	The train passes a level transition border (from level 2/3 to level 0, NTC, 1) with its min safe rear end.
g)	The level changes.
h)	A communication session is successfully established.
i)	Intentionally moved.
j)	The train passes an LRBG compliant balise group (see 3.6.2.2.2), if no position report parameters are stored on-board.
k)	The train passes a RBC/RBC border with its max safe front end.
point i means "intentionally deleted"
realised by: #REQ-UNISIG-SUB026-3070#REF#
realised by: #REQ-UNISIG-SUB026-3071#REF#
realised by: #REQ-UNISIG-SUB026-3072#REF#
realised by: #REQ-UNISIG-SUB026-3073#REF#
realised by: #REQ-UNISIG-SUB026-3074#REF#
realised by: #REQ-UNISIG-SUB026-3025#REF#
realised by: #REQ-UNISIG-SUB026-3075#REF#
realised by: #REQ-DESIGN-CR-0318#REF#
realised by: #REQ-DESIGN-CR-0007#REF#
realised by: #REQ-UNISIG-SUB026-3076#REF#

#REQ-UNISIG-SUB026-3070#REF# 3.6.5.1.4.a #REQ-UNISIG-SUB026-0455:01#REF#
When the train reaching standstill, if applicable to the current mode, the on-board equipment shall send a position report.
realised by: #REQ-DESIGN-CR-0019:02#REF#

#REQ-UNISIG-SUB026-3071#REF# 3.6.5.1.4.b #REQ-UNISIG-SUB026-0455:01#REF#
If the mode has changed, the on-board equipment shall send a position report.
realised by: #REQ-UNISIG-SUB026-1020:01#REF#

#REQ-UNISIG-SUB026-3072#REF# 3.6.5.1.4.c #REQ-UNISIG-SUB026-0455:01#REF#
If the driver confirms the train integrity, the on-board equipment shall send a position report.
is realized with 4.5.2
realised by: #REQ-UNISIG-SUB026-1021:01#REF#

#REQ-UNISIG-SUB026-3073#REF# 3.6.5.1.4.d #REQ-UNISIG-SUB026-0455:01#REF#
If loss of train integrity has been detected, the on-board equipment shall send a position report.
is realized with 4.5.2
realised by: #REQ-UNISIG-SUB026-1022:01#REF#

#REQ-UNISIG-SUB026-3074#REF# 3.6.5.1.4.e #REQ-UNISIG-SUB026-0455:01#REF#
If the train has passed a RBC/RBC border with its min safe rear end, the on-board equipment shall send a position report.
realised by: #REQ-UNISIG-SUB026-0889#REF#
realised by: #REQ-UNISIG-SUB026-0892#REF#

#REQ-UNISIG-SUB026-3025#REF# 3.6.5.1.4.f #REQ-UNISIG-SUB026-0455:01#REF#
#REQ-UNISIG-SUB026-0297#REF#
#REQ-UNISIG-SUB026-0301#REF#
#REQ-UNISIG-SUB026-2404#REF#
If the train has passed a level transition border (from level 2/3 to level 0,STM,1) with its min safe rear end, the on-board equipment shall
send a position report.
is realized with 4.5.2
realised by: #REQ-UNISIG-SUB026-010460#REF#

#REQ-UNISIG-SUB026-3075#REF# 3.6.5.1.4.g #REQ-UNISIG-SUB026-0455:01#REF#
If the level has changed, the on-board equipment shall send a position report.
is realized with 4.5.2
realised by: #REQ-UNISIG-SUB026-1025:02#REF#
realised by: #REQ-UNISIG-SUB026-1026:02#REF#

#REQ-DESIGN-CR-0318#REF# 3.6.5.1.4.h #REQ-UNISIG-SUB026-0455:01#REF#
#REQ-UNISIG-SUB026-3079:01#REF#
The on-board equipment shall send a position report
following the successful establishment of a communication session.
TEST APPROACH:
Mode NP is not realised by the ASW (see #REQ-UNISIG-SUB026-004698#REF#). Mode IS is realized by hardware and the EVC In is powered off in
isolation (see #REQ-UNISIG-SUB026-004676#REF#). OBU does permanently command the Emergency Brakes in the ETCS mode SF. Balise as well as RBC
messages are ignored in IS and SF (see #REQ-UNISIG-SUB026-3008#REF# and #REQ-UNISIG-SUB026-3009#REF#). In SH and PS the RBC ID/phone number are
stored without establishment of communication session. The verification for modes NP, IS, SF, SH and PS is hence omitted.
#TEST-VAL-SUB026-4364#REF# FCT FS PR at level change, standstill in FS, determine train speed and location
#TEST-VAL-SUB026-4574#REF# FCT LS PR at level, standstill in LS, determine train speed and location in LS
#TEST-VAL-SUB026-3860#REF# FCT NL NL - position report when passing single balise BG, no position report for BG with Q_LINK=0
#TEST-VAL-SUB026-4365#REF# FCT OS PR at level, standstill in OS, determine train speed and location
#TEST-VAL-SUB026-4372#REF# FCT PT PR when establishing a session with RBC, determine train speed and location in PT
#TEST-VAL-SUB026-4373#REF# FCT RV PR when establishing a session with RBC, determine train speed and location in RV
#TEST-VAL-SUB026-4367#REF# FCT SB PR at level change, when establishing a session with RBC, determine train speed and location
#TEST-VAL-SUB026-4368#REF# FCT SL PR when establishing a session with RBC, determine train speed and location in SL
#TEST-VAL-SUB026-4728#REF# FCT SN SN/STM - PR/MA parameter
#TEST-VAL-SUB026-4529#REF# FCT SR initiation/termination of communication session in SR
#TEST-VAL-SUB026-4371#REF# FCT TR PR when establishing a session with RBC, determine train speed and location in TR
#TEST-VAL-SUB026-4370#REF# FCT UN PR when establishing a session with RBC, determine train speed and location in UN
#TEST-VAL-SUB026-3019#REF# EET error expectation Initiation of a communication session by RBC

#REQ-DESIGN-CR-0007#REF# 3.6.5.1.4.j #REQ-UNISIG-SUB026-0455:01#REF#
if no position report parameters are stored on-board, the on-board equipment shall send a position report at every passage of LRBG compliant
balise group (see 3.6.2.2.2).
realised by: #REQ-DESIGN-CR-0123:02#REF#

#REQ-UNISIG-SUB026-3076#REF# 3.6.5.1.4.k #REQ-UNISIG-SUB026-0455:01#REF#
If the train has passed a RBC/RBC border with its max safe front end, the on-board equipment shall send a position report.
realised by: #REQ-UNISIG-SUB026-0887#REF#
realised by: #REQ-UNISIG-SUB026-0891#REF#

#REQ-UNISIG-SUB026-001267#REF# 3.6.5.1.4.1
If the position report results from one or more events listed in 3.6.5.1.4, its content shall reflect the consequences of these events.
realised by: #REQ-UNISIG-SUB026-3633:01#REF#
realised by: #REQ-UNISIG-SUB026-3634#REF#

#REQ-DESIGN-CR-0165#REF# 3.6.5.1.5
For the position report parameters requested by the RBC the following possibilities shall be available, individually or in combination
a)	Periodically in time.
b)	Periodically in space.
c)	When the max safe front end or min safe rear end of the train has passed a specified location.
d)	At every passage of an LRBG compliant balise group (see 3.6.2.2.2).
e)	Immediately.
#TEST-VAL-SUB026-3055#REF# FCT basic function Position Reports entsprechend Position Report Parametern
#TEST-VAL-SUB026-3978#REF# EET error expectation Cyclic Train Position Reports
#TEST-VAL-SUB026-5851#REF# EET error expectation Combination of position report parameter

#REQ-DESIGN-CR-0575:02#REF# to.3.6.5.1.5 #ANA-UNISIG-PR-0006:02#REF#
The starting point of the periods of  "Periodically in time" or  "Periodically in space" shall be defined by the internal
time or location when the periodical reporting is activated.
#TEST-VAL-SUB026-5797#REF# EET CFX00109539 Reference for PR (M136) cycle
#TEST-VAL-SUB026-5798#REF# EET CFX00109539 Reference for PR (M157) cycle
#TEST-VAL-SUB026-3682#REF# FCT Periodically in space starting point of the periods of Periodically in space
#TEST-VAL-SUB026-3681#REF# FCT Periodically in time starting point of the periods of Periodically in time

#REQ-UNISIG-SUB026-010222#REF# to.3.6.5.1.5 #ANA-UNISIG-PR-0010#REF#
If position report parameters from trackside are valid and a new session is to be established, any ongoing PR-cycle shall be restarted with the
position report after establishing a session with a RBC.
clarification: this is relevant for the establishment of the supervising session only
#TEST-VAL-SUB026-3B50#REF# FCT distance cycle Reference for PR (M136) cycle
#TEST-VAL-SUB026-7826#REF# EET error expectation RBC handover, session with the Accepting RBC established before handover location
#TEST-VAL-SUB026-7827#REF# EET error expectation RBC handover, session with the Accepting RBC established after passing the handover location
#TEST-VAL-SUB026-5797#REF# FCT time cycle Reference for PR (M136) cycle

#REQ-UNISIG-SUB026-007621#REF# to.3.6.5.1.5 #ANA-UNISIG-PR-0009#REF#
If the obu received position report parameters with specific locations and a part of these locations is already passed, a position report shall
be send immediately and than the next location in front of the train shall be supervised.
The several specific locations are supervised on after the other. A parallel supervision is'nt realized.
#TEST-VAL-SUB026-5282#REF# FCT basic function Position report parameters with specific locations, part of the indicated locations already passed
#TEST-VAL-SUB026-5851#REF# FCT error expectation Combination of position report parameter
#TEST-VAL-SUB026-5945#REF# EET error expectation Parallel supervision of PR locations ordered via P58

#REQ-UNISIG-SUB026-0457#REF# 3.6.5.1.7
The given position report parameters shall be valid until new parameters are given from the RBC.
#TEST-VAL-SUB026-3055#REF# FCT basic function Position Reports entsprechend Position Report Parametern

#REQ-UNISIG-SUB026-3029:01#REF# to.3.6.5.7.1 #ANA-UNISIG-PR-0007:01#REF#
If new PR-Parameter are given from the RBC and a PR-Cycle is going on, the old cycle shall be stopped, a position report shall be send and then
the new cycle shall be started.

Exception: In mode SB no position report shall be send after stopping the old cycle.
#TEST-VAL-SUB026-3682#REF# FCT Periodically in space starting point of the periods of Periodically in space
#TEST-VAL-SUB026-3681#REF# FCT Periodically in time starting point of the periods of Periodically in time
#TEST-VAL-SUB026-3978#REF# EET error expectation Cyclic Train Position Reports
#TEST-VAL-SUB026-5797#REF# FCT exception: SB Reference for PR (M136) cycle

#REQ-DESIGN-CR-0570#REF# 3.6.5.1.8
The mode and level reported in a position report shall be consistent (e.g., no mode that relates to the previous level).
#TEST-VAL-SUB026-4263#REF# FCT entering L2 (from L0) transition UN -> TR(L2) [39] - MA rejected (Train Data has been sent to the RBC and the Ack. Train Data has not been received yet)
#TEST-VAL-SUB026-4410#REF# FCT entering L2 (from L1) switch from SR/L1 to OS/L2 - border BG includes L1 MA - LT buffer includes CES, L2 MA + MP-OS SSP/GP, CES
#TEST-VAL-SUB026-4557#REF# FCT entering L2 (from NTC) mode transition SN->LS(L2)[71]->TR[16]
#TEST-VAL-SUB026-4121#REF# FCT leaving L2 Mode transition from FS to UN

#REQ-UNISIG-SUB026-001286#REF# 3.6.5.2.1
Train integrity information shall be given by external device or by driver.
TI signal isn't realized

DMI Part is realized with enabling conditions for the button "Train integrity" in ERA SRS DMI

#REQ-UNISIG-SUB026-3551#REF# 3.6.5.2.2
Driver input of train integrity shall only be permitted at standstill.
is realized with enabling conditions for the button "Train integrity" in ERA SRS DMI

#REQ-UNISIG-SUB026-3552#REF# 3.6.5.2.3
The train integrity information shall consist of
a)	Train integrity status information
  No train integrity information
  Train integrity information confirmed by integrity monitoring device
  Train integrity information confirmed (entered) by driver
  Train integrity lost
b)	Safe train length information (only valid if train integrity is confirmed at the same time).

#REQ-UNISIG-SUB026-3553#REF# 3.6.5.2.4
The safe train length information shall represent the distance between the min safe rear end (by subtracting the train length from the min. safe
front end position at the time when integrity was established last time) and the estimated position of the train front.

#DSC-UNISIG-SUB026-001302#REF#

Figure 15: Calculation of Safe Train Length when train integrity was established

#REQ-UNISIG-SUB026-3554#REF# 3.6.5.2.5
The safe train length information shall be re-calculated for every position report using the same last value of min safe rear end position until
a new min safe rear end position is established on-board taking into account the time to detect train integrity.

#REQ-UNISIG-SUB026-0020:01#REF# 3.6.6.1 #REQ-DESIGN-CR-0598:01#REF#
The ERTMS/ETCS on-board equipment shall display, only on driver request, the geographical position of the estimated front end of the train in
relation to the track kilometre. The display of the geographical position shall also be stopped on driver request.
#TEST-VAL-SUB026-7058#REF# FCT basic function Geographical indicated in relation to estimated front end on driver request

#REQ-UNISIG-SUB026-0458#REF# 3.6.6.2
The resolution of the position indication shall be 1 metre (sufficient to allow the driver to report the train position when communicating with
the signalman).

#REQ-UNISIG-SUB026-0459:01#REF# 3.6.6.3
When receiving new geographical position information (from radio or from balise group), the ERTMS/ETCS on-board equipment shall replace the
currently stored geographical position information (if any) by this new received one, continuing the on-going geographical position calculation
until at least one of the condition of 3.6.6.9 applies.
#TEST-VAL-SUB026-7001#REF# EET CFX00032932 Geographical Position mit N_ITER!=0
#TEST-VAL-SUB026-7032#REF# EET CFX00032932 P79 from unlinked BG
#TEST-VAL-SUB026-3059#REF# FCT basic function Last received P79 relevant for DMI indication of geographical position
#TEST-VAL-SUB026-3603#REF# EET error expectation Geographical Position Information from BG and Radio with same ref. NID_BG
#TEST-VAL-SUB026-3652#REF# FCT error expectation Once a track kilometre reference is no longer applicable, it is deleted (No more geographical position calculation) + lnk

#REQ-DESIGN-CR-0150:01#REF# 3.6.6.4.1
In case the information is received by radio and at least one of the announced geographical position reference balise group(s) is part of the
last reported balise groups memorised on-board, the on-board equipment shall use the data related to the most recently reported balise group.
#TEST-VAL-SUB026-3604#REF# FCT basic function Geographical Position Information from Radio NID_BG within list of reported BGs
#TEST-VAL-SUB026-3605#REF# EET error expectation Geographical Position Information jumbled list
#TEST-VAL-SUB026-7012#REF# EET error expectation Geographical Position Information N_ITER=31

#REQ-DESIGN-CR-0151:01#REF# 3.6.6.4.2
From the currently stored geographical position information, the track kilometre reference given for a geographical reference location shall
become applicable if the train has detected the related geographical reference balise group and has travelled the offset distance from this
reference balise group.
#TEST-VAL-SUB026-3057#REF# FCT basic function Geographical position
#TEST-VAL-SUB026-3451#REF# EET error expectation Two track reference values with downward counting sent in the same BG but different reference BGs
#TEST-VAL-SUB026-3452#REF# EET error expectation Two track reference values with downward counting sent in the same BG with the same reference BG
#TEST-VAL-SUB026-7010#REF# EET error expectation Geographical position reference unequal NID_BG of transmitting BG

#REQ-UNISIG-SUB026-3476#REF# 3.6.6.4.3
The announced and not applicable geographical references shall be deleted on-board if the train changes orientation.
#TEST-VAL-SUB026-7520#REF# FCT basic function Not applicable geographical position reference is deleted when train changes orientation

#REQ-UNISIG-SUB026-0461#REF# 3.6.6.5
The distance travelled from the geographical reference location shall be taken into account when calculating the geographical position.
#TEST-VAL-SUB026-3057#REF# FCT basic function Geographical position

#REQ-UNISIG-SUB026-0463:01#REF# 3.6.6.7
In cases where single balise groups are used as a reference for geographical position information and where no linking information is available
(and therefore no orientation can be assigned to the balise group), the on-board equipment shall ignore the geographical position information
related to these single balise groups.
#TEST-VAL-SUB026-5853#REF# FCT basic function Geographical position information based on single balise group
#TEST-VAL-SUB026-5745#REF# EET error expectation A group of two balises duplicating each other treated as a single BG in case where only one balise is correctly read

#REQ-UNISIG-SUB026-0464:01#REF# 3.6.6.9
The on-board equipment shall continue calculating the position from a track kilometre reference (i.e. this track kilometre reference shall
remain applicable) until:
a)	a new track kilometre reference becomes applicable, OR
b)	it is told not to do so, OR
c)	the calculated geographical position becomes negative, OR
d)	no more geographical position information is available (e.g., deleted according to conditions in SRS chapter 4)
#TEST-VAL-SUB026-7009#REF# EET CFX00037015 Geographical Position mit N_ITER=1 (beide GeoPos fuer eine BG)
#TEST-VAL-SUB026-7011#REF# EET CFX00037015 Geographical position reference - update just before zero crossing
#TEST-VAL-SUB026-7008#REF# EET CFX00037015 , c) Geographical Position mit N_ITER=1
#TEST-VAL-SUB026-3368#REF# EET CFX00039607 Level transitition L1->L2 - Reception of P79 with reference to border BG
#TEST-VAL-SUB026-3605#REF# FCT a) Geographical Position Information jumbled list
#TEST-VAL-SUB026-3061#REF# FCT b) Geographical position stopped and restarted
#TEST-VAL-SUB026-4264#REF# FCT d) Geographical Position Information FS->OS->FS->SH->SB
#TEST-VAL-SUB026-3451#REF# EET error expectation Two track reference values with downward counting sent in the same BG but different reference BGs
#TEST-VAL-SUB026-3603#REF# EET error expectation Geographical Position Information from BG and Radio with same ref. NID_BG

#REQ-UNISIG-SUB026-3477#REF# 3.6.6.9.1
Once a track kilometre reference is no longer applicable, it shall be deleted.
TEST APPROACH:
The following aspects have been identified:
1) a new track kilometre reference becomes applicable (3.6.6.9 a))
2) it is told not to do so (3.6.6.9 b) )
3) the calculated geographical position becomes negative (3.6.6.9 c)) 
4) no more geographical position information is available (3.6.6.9 d)) 
#TEST-VAL-SUB026-3653#REF# FCT 1 Once a track kilometre reference is no longer applicable, it is deleted (new track kilometer ref.)
#TEST-VAL-SUB026-3652#REF# FCT 2 Once a track kilometre reference is no longer applicable, it is deleted (No more geographical position calculation) + lnk
#TEST-VAL-SUB026-3651#REF# FCT 3 deletion of track kilometer reference due to zero-crossing
#TEST-VAL-SUB026-4264#REF# ECT 4 Geographical Position Information FS->OS->FS->SH->SB

#REQ-DESIGN-CR-0152#REF# 3.6.6.10
The following data shall be included in a message for geographical position (for every track kilometre reference):
  Identity of the geographical position reference balise group
  Distance from geographical position reference balise group to the track kilometre reference (offset)
  Value of the track kilometre reference
  Counting direction of the track kilometre in relation to the geographical position reference balise group orientation.
see figure 16 also
#DSC-UNISIG-SUB026-001345#REF#

Figure 16: Geographical position example
realised by: #REQ-DESIGN-CR-0187:01#REF#

Chapter 3.7

#REQ-DESIGN-CR-0499#REF# 3.7.2.3 #REQ-UNISIG-SUB026-0734#REF#
#REQ-UNISIG-SUB026-005008#REF#
#REQ-UNISIG-SUB026-3361#REF#
#REQ-DESIGN-CR-0501#REF#
The MA and the related mode profile, if any, shall not be accepted by the on-board equipment if the SSP and gradient already available on-board
or given together with the MA do not cover the full length of the MA.
TEST APPROACH:
The following aspects have been identified:
1) dependency on profile continuity
1.1) gap in GP coverage
1.2) gap in SSP coverage
2) handling of buffered MA
2.1) buffered MA L0
2.2) buffered MA L1
2.3) buffered MA L2
2.4) buffered MA NTC
3) MA extension via P16
#TEST-VAL-SUB026-4413#REF# FCT 1.1 MA rejected due to gap in GP coverage
#TEST-VAL-SUB026-4414#REF# FCT 1.2 MA rejected due to gap in SSP coverage
#TEST-VAL-SUB026-4859#REF# FCT 2.1 level transition L0->L1->L2, MA not covered
#TEST-VAL-SUB026-4864#REF# FCT 2.2 MP rejected if MA not covered by SSP/GP (L1->L2)
#TEST-VAL-SUB026-4858#REF# FCT 2.3 level transition L2->L1, L1 MA not covered
#TEST-VAL-SUB026-4767#REF# FCT 2.4 Acception of GP via balises while Level is STM (no L1 transition is given)
#TEST-VAL-SUB026-3305#REF# FCT 3 GP und SSP überdecken die Repositioning Informationen nicht
#TEST-VAL-SUB026-3008#REF# EET CFX00036745 Accepting new GP with starting point bevor stored GP
#TEST-VAL-SUB026-4984#REF# EET error expectation Check 4.8.3 --> Acceptance of MA, MP packets
#TEST-VAL-SUB026-4H34#REF# EET error expectation None of the information within not accepted MA taken into account
#TEST-VAL-SyAnfSpezCR-0053#REF# EET error expectation MA rejected if SSP/GP do not cover full length

#REQ-DESIGN-CR-0114#REF# 3.7.2.3.1 #REQ-UNISIG-SUB026-0734#REF#
#REQ-UNISIG-SUB026-005008#REF#
#REQ-UNISIG-SUB026-3361#REF#
Note: Full length means at least from the estimated front end of the train to the supervised location.
#TEST-VAL-SUB026-3062#REF# FCT basic function MA acceptance depending on SSP/GP coverage
#TEST-VAL-SUB026-3686#REF# EET error expectation SR/L1->FS/L2 - linking information and MA with Shifted Location Reference in transition buffer
#TEST-VAL-SyAnfSpezCR-0053#REF# EET error expectation MA rejected if SSP/GP do not cover full length

#REQ-UNISIG-SUB026-010401#REF# to.3.7.2.3 #ANA-UNISIG-AccInformation-0005#REF#
clarification to 3.7.2.3:
The information "signalling related speed restriction" in the level 1 ma shall be accepted independent from the check over the full
cover by track description.
see analysis
#TEST-VAL-SUB026-5756#REF# FCT basic function Acceptance of signalling related speed restriction if MA not covered by SSP/GP
#TEST-VAL-SUB026-7035#REF# EET error expectation Acceptance of buffered signalling speed restriction
#TEST-VAL-SUB026-7041#REF# EET error expectation Signalling related speed restriction not taken into account in SR

#REQ-UNISIG-SUB026-3550#REF# zu.3.7.2.3 #ANA-UNISIG-MAData-0006#REF#
If the onboard received new SSP and/or gradient profiles and the actual including the new profiles do not cover the full length of the actual
MA, the actual MA shall be deleted and a Train Trip shall be triggered.
TEST APPROACH:
The following aspects have been identified:
1) GP
2) SSP
3) handling of infill profile data
#TEST-VAL-SUB026-3062#REF# FCT 1 MA acceptance depending on SSP/GP coverage
#TEST-VAL-SUB026-3685#REF# FCT 2 Train trip due to reception of GP/SSP which does not cover current MA
#TEST-VAL-SUB026-4159#REF# FCT 3 Current MA gets invalid due to reception of new infill SSP/GP
#TEST-VAL-SUB026-4411#REF# EET CFX00038386 transition FS->TR due to GP/SSP shortening
#TEST-VAL-SUB026-3688#REF# EET error expectation End of the actual SSP or GA is shorter than the start of the new SSP or GA
#TEST-VAL-SUB026-4160#REF# EET error expectation Transition to TR due to new SSP/GP not covering current MA, following infill MA has no relevance

#REQ-UNISIG-SUB026-0022:02#REF# 3.7.3.1
New track description and linking information shall replace (in the ERTMS/ETCS on-board equipment) stored information as detailed below:
a)	New Static Speed Profile information shall replace all stored Static Speed Profile information from the start location of the new
information.
b)	New Gradient Profile information shall replace all stored Gradient Profile information from the start location of the new information.
c)	New Axle Load Speed Profile information shall replace all stored Axle Load Speed Profile information from the start location of the
first element of the new information.
d)	New Speed Restriction to ensure Permitted Braking Distance information shall replace all stored Speed Restriction to ensure Permitted
Braking Distance information from the start location of the first element of the new information.
e)	New track condition Change of Traction System information shall replace all stored Change of Traction System information.
f)	New track condition Big Metal Masses information shall replace all stored Big Metal Masses information from the start location of the
first element of the new information.
g)	New track condition information of at least one of the types listed here, i.e., sound horn, non stopping area, tunnel stopping area,
powerless section - lower pantograph, powerless section - switch off the main power switch, radio hole, air tightness, switch off regenerative
brake, switch off eddy current brake for service brake, switch off eddy current brake for emergency brake, switch off magnetic shoe brake, shall
replace all stored track condition information of the listed types from the start location of the first element of the new information.
h)	New route suitability loading gauge information shall replace all stored route suitability loading gauge information.
i)	New route suitability traction system information shall replace all stored route suitability traction system information.
j)	New route suitability axle load information shall replace all stored route suitability axle load information.
k)	New reversing area information shall replace all stored reversing area information.
l)	New adhesion factor information shall replace all stored adhesion factor information from the start location of the new information.
m)	New linking information received as non-infill information shall replace all stored linking information from the LRBG.
n)	New linking information received as infill information shall replace all stored linking information from the reference location of the
infill information (i.e. the balise group at next main signal).
realised by: #REQ-UNISIG-SUB026-010253#REF#
realised by: #REQ-UNISIG-SUB026-010254#REF#
realised by: #REQ-UNISIG-SUB026-010255#REF#
realised by: #REQ-UNISIG-SUB026-010256#REF#
realised by: #REQ-UNISIG-SUB026-010257#REF#
realised by: #REQ-UNISIG-SUB026-010258#REF#
realised by: #REQ-UNISIG-SUB026-010259#REF#
realised by: #REQ-UNISIG-SUB026-010260#REF#
realised by: #REQ-UNISIG-SUB026-010261#REF#
realised by: #REQ-UNISIG-SUB026-010262#REF#
realised by: #REQ-UNISIG-SUB026-010263#REF#
realised by: #REQ-UNISIG-SUB026-010264#REF#
realised by: #REQ-UNISIG-SUB026-010265#REF#
realised by: #REQ-UNISIG-SUB026-010266#REF#

#REQ-UNISIG-SUB026-010253#REF# 3.7.3.1.a) #REQ-UNISIG-SUB026-0022:02#REF#
New Static Speed Profile information shall replace all stored Static Speed Profile information from the start location of the new information.
#TEST-VAL-SUB026-3063#REF# FCT basic function New SSP/GP replace stored SSP/GP taking D_STATIC/D_GRADIENT into account

#REQ-UNISIG-SUB026-010254#REF# 3.7.3.1.b) #REQ-UNISIG-SUB026-0022:02#REF#
New Gradient Profile information shall replace all stored Gradient Profile information from the start location of the new information.
#TEST-VAL-SUB026-3063#REF# FCT basic function New SSP/GP replace stored SSP/GP taking D_STATIC/D_GRADIENT into account

#REQ-UNISIG-SUB026-010255#REF# 3.7.3.1.c) #REQ-UNISIG-SUB026-0022:02#REF#
New Axle Load Speed Profile information shall replace all stored Axle Load Speed Profile information from the start location of the first
element of the new information.
#TEST-VAL-SUB026-3B06#REF# FCT basic function New ASP replaces existing ASP taking D_AXLELOAD/D_TRACKINIT into account

#REQ-UNISIG-SUB026-010256#REF# 3.7.3.1.d) #REQ-UNISIG-SUB026-0022:02#REF#
New Speed Restriction to ensure Permitted Braking Distance information shall replace all stored Speed Restriction to ensure Permitted Braking
Distance information from the start location of the first element of the new information.
#TEST-VAL-SUB026-5928#REF# FCT basic function New PBD replaces old PBD taking D_PBDSR/D_TRACKINIT into account

#REQ-UNISIG-SUB026-010257#REF# 3.7.3.1.e) #REQ-UNISIG-SUB026-0022:02#REF#
#REQ-UNISIG-SUB040-3019:01#REF#
New track condition Change of Traction System information shall replace all stored Change of Traction System information.
#TEST-VAL-SUB026-7723#REF# FCT basic function Replacement of TC "Change of traction power" by new TC
#TEST-VAL-SUB026-7078#REF# EET error expectation New track condition Change of Traction System information as infill information

#REQ-UNISIG-SUB026-010258#REF# 3.7.3.1.f) #REQ-UNISIG-SUB026-0022:02#REF#
New track condition Big Metal Masses information shall replace all stored Big Metal Masses information from the start location of the first
element of the new information.
#TEST-VAL-SUB026-7720#REF# FCT basic function New track condition BMM information replaces all stored BMM information from the start location of the new information

#REQ-UNISIG-SUB026-010259#REF# 3.7.3.1.g) #REQ-UNISIG-SUB026-0022:02#REF#
New track condition information of at least one of the types listed here, i.e., sound horn, non stopping area, tunnel stopping area, powerless
section - lower pantograph, powerless section - switch off the main power switch, radio hole, air tightness, switch off regenerative brake,
switch off eddy current brake for service brake, switch off eddy current brake for emergency brake, switch off magnetic shoe brake, shall
replace all stored track condition information of the listed types from the start location of the first element of the new information.
#TEST-VAL-SUB026-3934#REF# EET CFX00036009 OBU receives two TCs (in two messages) of different type with same start point
#TEST-VAL-SUB026-4304#REF# FCT basic function TC Excluding Big Metal Masses FS/NL
#TEST-VAL-SUB026-3095#REF# EET error expectation New MA replaces old MA

#REQ-UNISIG-SUB026-010260#REF# 3.7.3.1.h) #REQ-UNISIG-SUB026-0022:02#REF#
New route suitability loading gauge information shall replace all stored route suitability loading gauge information.
#TEST-VAL-SUB026-4H71#REF# FCT basic function Route suitability Loading Gauge information overwrite

#REQ-UNISIG-SUB026-010261#REF# 3.7.3.1.i) #REQ-UNISIG-SUB026-0022:02#REF#
New route suitability traction system information shall replace all stored route suitability traction system information.
#TEST-VAL-SUB026-4H73#REF# FCT basic function Route suitability Traction System information overwrite

#REQ-UNISIG-SUB026-010262#REF# 3.7.3.1.j) #REQ-UNISIG-SUB026-0022:02#REF#
New route suitability axle load information shall replace all stored route suitability axle load information.
#TEST-VAL-SUB026-4H72#REF# FCT basic function Route suitability Axle Load information overwrite

#REQ-UNISIG-SUB026-010263#REF# 3.7.3.1.k) #REQ-UNISIG-SUB026-0022:02#REF#
New reversing area information shall replace all stored reversing area information.
is already defined in 3.15.4.1.1
realised by: #REQ-UNISIG-SUB026-3113#REF#

#REQ-UNISIG-SUB026-010264#REF# 3.7.3.1.l) #REQ-UNISIG-SUB026-0022:02#REF#
New adhesion factor information shall replace all stored adhesion factor information from the start location of the new information.
#TEST-VAL-SUB026-3B51#REF# FCT basic function Evaluation of new adhesion factor information

#REQ-UNISIG-SUB026-010265#REF# 3.7.3.1.m) #REQ-UNISIG-SUB026-0022:02#REF#
New linking information received as non-infill information shall replace all stored linking information from the LRBG.
#TEST-VAL-SUB026-3932#REF# FCT basic function Replacement of linking information

#REQ-UNISIG-SUB026-010266#REF# 3.7.3.1.n) #REQ-UNISIG-SUB026-0022:02#REF#
New linking information received as infill information shall replace all stored linking information from the reference location of the infill
information (i.e. the balise group at next main signal).
#TEST-VAL-SUB026-3064#REF# FCT basic function Overwriting of old Linking Information with new Linking Information

#REQ-UNISIG-SUB026-3541#REF# to.3.7.3.1 #ANA-UNISIG-TrackDescription-0001#REF#
If the end of the actual SSP or GA profile is shorter than the start of the new SSP or GA profile, the new information shall be ignored.
In this case a basic diagnostic event shall be created.
#TEST-VAL-SUB026-3790#REF# FCT basic function New SSP/GP profile ignored if end of the actual SSP or GP is shorter than the start of the new SSP or GP
#TEST-VAL-SUB026-7042#REF# EET error expectation SSP/GP gap in rear of buffered MA

#REQ-UNISIG-SUB026-0468:01#REF# 3.7.3.2
When requested by trackside, the ERTMS/ETCS on-board equipment shall resume initial states beyond a given location individually:
a)	for stored Speed Restriction to ensure Permitted Braking Distance information (for initial state, refer to 3.11.11.7)
b)	for stored axle load speed profile information (for initial state, refer to 3.11.4.5)
c)	through a single request, for all stored track condition information of the following types: sound horn, non stopping area, tunnel
stopping area, powerless section - lower pantograph, powerless section - switch off the main power switch, radio hole, air tightness, switch off
regenerative brake, switch off eddy current brake for service brake, switch off eddy current brake for emergency brake and switch off magnetic
shoe brake (for initial states, refer to 3.12.1.3)
d)	through a single request, for all stored route suitability information (for initial state, refer to 3.12.2.10).
realised by: #REQ-UNISIG-SUB026-010267#REF#
realised by: #REQ-UNISIG-SUB026-010268#REF#
realised by: #REQ-UNISIG-SUB026-010269#REF#
realised by: #REQ-UNISIG-SUB026-010270#REF#

#REQ-UNISIG-SUB026-010267#REF# 3.7.3.2.a) #REQ-UNISIG-SUB026-0468:01#REF#
When requested by trackside, the ERTMS/ETCS on-board equipment shall resume initial states beyond the given location for stored Speed
Restriction to ensure Permitted Braking Distance information (for initial state, refer to 3.11.11.7).
clarification:
if the given location fells together with a start point of a PBD, this PBD is to be deleted.
#TEST-VAL-SUB026-5928#REF# FCT basic function New PBD replaces old PBD taking D_PBDSR/D_TRACKINIT into account

#REQ-UNISIG-SUB026-010268#REF# 3.7.3.2.b) #REQ-UNISIG-SUB026-0468:01#REF#
When requested by trackside, the ERTMS/ETCS on-board equipment shall resume initial states beyond the given location for stored axle load speed
profile information (for initial state, refer to 3.11.4.5).
clarification:
if the given location fells together with a start point of a ASP, this ASP is to be deleted.
#TEST-VAL-SUB026-3B06#REF# FCT basic function New ASP replaces existing ASP taking D_AXLELOAD/D_TRACKINIT into account

#REQ-UNISIG-SUB026-010269#REF# 3.7.3.2.c) #REQ-UNISIG-SUB026-0468:01#REF#
When requested by trackside, the ERTMS/ETCS on-board equipment shall resume initial states beyond the given location through a single request,
for all stored track condition information of the following types: sound horn, non stopping area, tunnel stopping area, powerless section -
lower pantograph, powerless section - switch off the main power switch, radio hole, air tightness, switch off regenerative brake, switch off
eddy current brake for service brake, switch off eddy current brake for emergency brake and switch off magnetic shoe brake (for initial states,
refer to 3.12.1.3).
#TEST-VAL-SUB026-3065#REF# FCT basic function Evaluation of Q_TRACKINIT = 1 for P68
#TEST-VAL-SUB026-3834#REF# EET error expectation Reception of P68 with Q_TRACKINIT=1 D_TRACKINIT=0 within TC area
#TEST-VAL-SUB026-3835#REF# EET error expectation Reception of P68 with Q_TRACKINIT=1 for current position within TC area
#TEST-VAL-SUB026-5462#REF# EET error expectation Message with P68 Q_TRACKINIT=1, D_TRACKCOND, L_TRACKCOND... rejected
#TEST-VAL-SUB026-7788#REF# EET error expectation Q_TRACKINIT =1, D_TRACKINIT the same as D_TRACKCOND of former TC
#TEST-VAL-SUB026-7924#REF# EET error expectation Reception of P68 with Q_TRACKINIT=1 within Radio Hole area

#REQ-UNISIG-SUB026-010270#REF# 3.7.3.2.d) #REQ-UNISIG-SUB026-0468:01#REF#
When requested by trackside, the ERTMS/ETCS on-board equipment shall resume initial states beyond the given location through a single request,
for all stored route suitability information (for initial state, refer to 3.12.2.10).
#TEST-VAL-SUB026-4H74#REF# FCT basic function Route suitability Q_TRACKINIT=1

Chapter 3.8

#REQ-UNISIG-SUB026-0471:03#REF# 3.8.2.3
In level 2/3, the following possibilities shall be available:
a)	A defined time before the train reaches the pre-indication location (see section 3.13) for the EOA/LOA assuming it is running at the
warning speed.
b)	A defined time before the Section timer (not the End Section timer, not the Overlap timer) for any section of the MA expires, or before
the LOA speed timer expires.
see also defined values in packet 57
#TEST-VAL-SUB026-3074#REF# FCT a), b)-LoA speed timer MA-Requests according to T_MAR
#TEST-VAL-SUB026-3075#REF# FCT b)-section timer MA-Requests entsprechend T_TIMEOUTRQST
#TEST-VAL-SUB026-7666#REF# EET error expectation Storage of LX not protected information in rear of the train, transition to mode where LX information is deleted

#REQ-UNISIG-SUB026-009835#REF# to.3.8.2.3
Clarification to 3.8.2.3:
The warning speed used in the calculation shall be the warning speed limit of the MRSP-element used for calculating the Pre-Indication location.
If there is no Pre-Indication location for an LOA (e.g. because the speed of the LOA is above the MRSP), the following condition shall be used:
a2) A defined time before the train reaches the LOA location assuming it is running at the warning speed of the MRSP-element at the
LOA-location.
UNISIG clarification:
a clarification is necessary, when no pre indication location is available
#TEST-VAL-SUB026-3074#REF# FCT basic function MA-Requests according to T_MAR

#REQ-UNISIG-SUB026-3080#REF# 3.8.2.3.1
Regards to the above possibilities, the MA request shall be triggered when the train front has passed the resulting location (regards a)/ time
(regards b)
TEST APPROACH:
1) A defined time before the train reaches the pre-indication location (see section 3.13) for the EOA/LOA assuming it is running at the warning
speed.
1.1) EoA
1.2) LoA
2) A defined time before the Section timer (not the End Section timer, not the Overlap timer) for any section of the MA expires, or before the
LOA speed timer expires
2.1) EoA
2.2) LoA
#TEST-VAL-SUB026-4885#REF# FCT 1.1 MA-Requests according to T_MAR in OS
#TEST-VAL-SUB026-3074#REF# FCT 1.2, 2.2 MA-Requests according to T_MAR
#TEST-VAL-SUB026-3075#REF# FCT 2.1 MA-Requests entsprechend T_TIMEOUTRQST
#TEST-VAL-SUB026-4140#REF# EET CFX00033918 sending MA request to RBC according to Pkt. 57 in conjunction with Level/mode change

#REQ-UNISIG-SUB026-0472:01#REF# to.3.8.2.4 #REQ-UNISIG-SUB026-0474#REF#
#ANA-UNISIG-MARequest-0005#REF#
A MA request shall be repeated until a new movement authority has been accepted by the OBU.
The time between each repetition is defined in the MA Request Parameter. If the MA Request parameter are not available the fixed value
T_CYCRQSTD shall be used.

Exception: The MA-Request with reason ""TAF up to level 2/3 transition location" shall not be repeated.
TEST APPROACH:
The following aspects have been identified:
1) basic function, P57
2) fixed value T_CYCRQSTD
3) Exception: MA-Request with reason 'TAF up to level 2/3 transition location'
#TEST-VAL-SUB026-7029#REF# FCT 1 MA request until a new movement authority has been accepted by the OBU
#TEST-VAL-SUB026-3078#REF# FCT 2 MA request repetition cycle, default fixed value T_CYCRQSTD
#TEST-VAL-SUB026-4B00#REF# FCT 3 Check table 4.5.2/4.8.4 Information->Track ahead free up to leve l2/3 transition location, Mode LS
#TEST-VAL-SUB026-7694#REF# EET error expectation Cyclical MA-Request not stopped when train exits section

#REQ-UNISIG-SUB026-0473#REF# 3.8.2.5
The given data shall be valid until new MA request parameters are given from the RBC.
#TEST-VAL-SUB026-3076#REF# FCT basic function Wiederholung von MA-Requests entsprechend T_CYCRQST

#REQ-UNISIG-SUB026-3030#REF# to.3.8.2.5 #ANA-UNISIG-MARequest-0001#REF#
If new MA-Request-Parameter are given from the RBC and a MA-Request-Cycle is going on, the old cycle shall be stopped, a MA-Request shall be
send and than the new cycle shall be started.
TEST APPROACH:
The following aspects have been identified:
1) MA request due to MA request parameter
2) MA request due to START
3) MA request due to deletion of track description
#TEST-VAL-SUB026-3691#REF# FCT 1 New MA Request Parameters after MA request due to approaching target indication point
#TEST-VAL-SUB026-3689#REF# FCT 2 New MA Request Parameters while MA request cycle due to START running
#TEST-VAL-SUB026-3690#REF# FCT 3 New MA Request Parameters after MA request due to deletion of track description

#REQ-UNISIG-SUB026-0474#REF# 3.8.2.6 #REQ-UNISIG-SUB026-007977#REF#
In case no MA request parameters are stored on-board and following an MA request no MA has been received, the request shall be repeated with a
repetition cycle according to a fixed value (see appendix).
realised by: #REQ-UNISIG-SUB026-0472:01#REF#

#REQ-UNISIG-SUB026-0475#REF# 3.8.2.7 #REQ-UNISIG-SUB026-0190:01#REF#
#REQ-UNISIG-SUB026-1098:01#REF#
In level 2/3: an MA request shall be sent to the RBC when the driver selects start.
TEST APPROACH:
The start button is available only in modes SB, PT and SR. Hence the verification of this requirement is limited to these modes only.
#TEST-VAL-SUB026-4027#REF# EET CFX00036091 new MA request in SR
#TEST-VAL-SUB026-4202#REF# EET CFX00036091 SR Distance extension - Availability of the Start button while the train is moving
#TEST-VAL-SUB026-5883#REF# EET CFX00036091 Availability of the Start button while infinite D_SR is valid on-board
#TEST-VAL-SUB026-4523#REF# FCT PT Movement Authority Request Parameters in PT
#TEST-VAL-SUB026-4520#REF# FCT SB Movement Authority Request Parameters in SB
#TEST-VAL-SUB026-4521#REF# FCT SR Movement Authority Request Parameters in SR

#REQ-DESIGN-CR-0516#REF# 3.8.2.7.1
In level 0, 1, NTC: if a level 2/3 transition is announced and a communication session is already established, an MA request shall be sent to
the RBC when the information "Track ahead free up to level 2/3 transition location" is received from balise group.
TEST APPROACH:
The following aspects have been identified:
1) Dependency on level
1.1) L0
1.2) L1
1.3) NTC
2) Dependency on session state
#TEST-VAL-SUB026-4954#REF# FCT 1.1, 1.2 Track Ahead Free up to level 2/3 transition location (pkt 90)
#TEST-VAL-SUB026-4270#REF# FCT 1.3 Track Ahead Free up to level 2/3 transition location (pkt 90) STM
#TEST-VAL-SUB026-5796#REF# FCT 2 Passing BG with P90 during communication session establishment

#REQ-DESIGN-CR-0517#REF# 3.8.2.7.2
In level 0, 1, NTC: the ERTMS/ETCS on-board equipment shall also inform the RBC about the identity of the level 2/3 transition location balise
group, as received through the information "Track ahead free up to level 2/3 transition location".
#TEST-VAL-SUB026-4954#REF# FCT L0, L1 Track Ahead Free up to level 2/3 transition location (pkt 90)
#TEST-VAL-SUB026-4270#REF# FCT NTC Track Ahead Free up to level 2/3 transition location (pkt 90) STM

#REQ-UNISIG-SUB026-010525#REF# 3.8.2.7.3
In level 2/3: An MA request shall be sent to the RBC when any part of the track description is deleted according to A.3.4, except for situations
a, b, f, k.
realised by: #REQ-UNISIG-SUB026-3244:01#REF#

#REQ-UNISIG-SUB026-3244:01#REF# 3.8.2.7.3 #REQ-UNISIG-SUB026-010525#REF#
#ANA-UNISIG-MARequest-0003:01#REF#
In level 2/3: An MA request with reason "the track description has been deleted" shall be sent to the RBC when the EoA or SvL of the
current ma is shortened according to A.3.4, except for situations a, b, f, k.

remark: This includes the case of shortening a LoA to an EoA.
#TEST-VAL-SUB026-5811#REF# FCT A.3.4 a, b, c MA request and Q_MARQSTREASON accumulation
#TEST-VAL-SUB026-3070#REF# FCT A.3.4 d MA-Request triggered by MA shortening
#TEST-VAL-SUB026-4E23#REF# FCT A.3.4 e, f, k, n MA request sent when section timer/LOA speed timer expires
#TEST-VAL-SUB026-3187#REF# FCT A.3.4 g Missing balise in unlinked BG
#TEST-VAL-SUB026-4E24#REF# FCT A.3.4 h, l MA request sent when RAMS supervision led to a service brake and train reaches standstill
#TEST-VAL-SUB026-4E26#REF# FCT A.3.4 i MA request sent when driver selects Start
#TEST-VAL-SUB026-3073#REF# FCT A.3.4 j MA-Request after change of train data
#TEST-VAL-SUB026-4E27#REF# FCT A.3.4 m MA request sent at standstill after service brake due to error in linked BG and no linking used on board
#TEST-VAL-SUB026-3088#REF# EET error expectation SvL: Overlap=>DP

#REQ-UNISIG-SUB026-0476:01#REF# 3.8.2.8
Together with the MA request the on-board shall inform the RBC about the reason(s) why the MA request is sent:
a)	Start selection by driver,
b)	Time before reaching pre-indication location for the EOA/LOA reached,
c)	Time before a section timer or the LOA speed timer expires reached,
d)	The track description has been deleted,
e)	Track ahead free up to level 2/3 transition location.
#TEST-VAL-SUB026-4E26#REF# FCT a MA request sent when driver selects Start
#TEST-VAL-SUB026-4E28#REF# FCT b MA-Requests according to T_MAR
#TEST-VAL-SUB026-4E30#REF# FCT c MA-Requests according to T_TIMEOUTRQST
#TEST-VAL-SUB026-4E24#REF# FCT d MA request sent when RAMS supervision led to a service brake and train reaches standstill
#TEST-VAL-SUB026-4E29#REF# FCT e MA Request when passing BG with Track Ahead Free up to level 2/3 transition location

#REQ-UNISIG-SUB026-010176#REF# to.3.8.2.8 #ANA-UNISIG-MARequest-0004#REF#
If more than one reason is accumulated, all reasons shall be transmitted with the MA request.
Example:
A Ma request with reason "Time before a section timer or the LOA speed timer expires reached" is send cyclic and then, after the timer
is expired, a new MA request must be sended. In this case both reasons are transmitted.
TEST APPROACH:
The accumulation of MA request reasons as well as the removal of no longer valid reasons has to be tested.
The following aspects have been identified:
1) Accumulation of reasons
2) Deletion of invalid reason
2.1) xxxx1
2.2) xxx1x
2.3) xx1xx
2.4) x1xxx
2.5) 1xxxx
#TEST-VAL-SUB026-4E25#REF# FCT 1 More MA request reasons
#TEST-VAL-SUB026-4E26#REF# FCT 2.1 MA request sent when driver selects Start
#TEST-VAL-SUB026-4E28#REF# FCT 2.2 MA-Requests according to T_MAR
#TEST-VAL-SUB026-4E30#REF# FCT 2.3 MA-Requests according to T_TIMEOUTRQST
#TEST-VAL-SUB026-4E24#REF# FCT 2.4 MA request sent when RAMS supervision led to a service brake and train reaches standstill
#TEST-VAL-SUB026-4E29#REF# FCT 2.5 MA Request when passing BG with Track Ahead Free up to level 2/3 transition location
#TEST-VAL-SUB026-5804#REF# EET error expectation MA request according to P57 for L1 MA

#REQ-UNISIG-SUB026-0478#REF# 3.8.3.3
In addition, the End Section of the MA may include;
a)	End Section time-out value and distance from the End Section timer start location to the end of the last section
b)	Danger point information (distance from end of section to danger point, release speed related to danger point)
c)	Overlap information (distance from end of section to end of overlap, time-out, distance from Overlap timer start location to end of
section, release speed related to overlap)
see also figure 17
#DSC-UNISIG-SUB026-001500#REF#

Figure 17: Structure of an MA
TEST APPROACH:
This general requirement is tested in detailed in the following section a exhaustive test is hence omitted here.
#TEST-VAL-SUB026-3705#REF# FCT a) MA repetition while end section timer running (timer value increased)
#TEST-VAL-SUB026-3088#REF# FCT b), c) SvL: Overlap=>DP
#TEST-VAL-SUB026-5613#REF# EET error expectation Time-out start location and section time.out stop location outside corresponding section

#REQ-UNISIG-SUB026-001499#REF# to.3.8.3.3
The value 0 of a release speed received from trackside shall be interpreted as "no release speed is to be used".
UNISIG clarification:
a clarification for V_NVREL, V_RELEASEDP and V_RELEASEOL = 0 is necessary
TEST APPROACH:
The following aspects have been identified:
1) V_RELEASEDP 
2) V_RELEASEOL 
3) V_NVREL
#TEST-VAL-SUB026-3A07#REF# FCT 1, 2 Processing of track side defined release speed 0
#TEST-VAL-SUB026-3228#REF# FCT 3 Variable test V_NVREL
#TEST-VAL-SUB026-5234#REF# EET error expectation On-board calculated release speed

#REQ-UNISIG-SUB026-0480#REF# 3.8.3.6
When an MA is transmitted by a balise group, the length of the first section shall refer to the balise co-ordinate system of that balise group.
#TEST-VAL-SUB026-3535#REF# FCT CAB A L1 MA supervision after passing linked and unlinked BGs
#TEST-VAL-SUB026-3536#REF# FCT CAB B Confidence interval and position calculation, orientation B, L1 MA

#REQ-UNISIG-SUB026-2304#REF# 3.8.3.8
In case the main signal is at danger in level 1, the on-board shall supervise the given distance (specified in section 3.8.3.7) as the distance
to EOA.
#TEST-VAL-SUB026-3126#REF# FCT basic function Infill Trip Order from loop

#REQ-UNISIG-SUB026-0482#REF# 3.8.3.9
When an MA is transmitted by radio from the RBC, the length of the first section shall refer to the balise co-ordinate system of the LRBG given
in the same message.
#TEST-VAL-SUB026-4557#REF# FCT basic function mode transition SN->LS(L2)[71]->TR[16]

#REQ-UNISIG-SUB026-0028#REF# 3.8.4.1.1
The End Section timer shall be started on-board when the train passes the End Section timer start location given by trackside with its max safe
front end.
#TEST-VAL-SUB026-3081#REF# FCT basic function MA with end section timer FS/L2
#TEST-VAL-SUB026-5468#REF# EET error expectation End section timer supervision - L1 MA shortened to location in front of infill location reference
#TEST-VAL-SUB026-5469#REF# EET error expectation End section timer supervision - L1 MA shortened to location in rear of infill location reference

#REQ-UNISIG-SUB026-006961#REF# zu.3.8.4.1.1 #ANA-UNISIG-MAData-0010#REF#
An end section timer shall be ignored, when
- a MA is shortened because A3.4
AND
- the end section timer start location is behind the new stop location.
#TEST-VAL-SUB026-5284#REF# FCT basic function End section timer start location behind the new stop location

#REQ-UNISIG-SUB026-010510#REF# 3.8.4.1.2
When the End Section timer value becomes greater than the time-out value given by trackside, the following shall apply:
a)	The EOA/LOA shall be withdrawn to the current position of the train. Refer to appendix A.3.4 for the exhaustive list of location based
information stored on-board, which shall be deleted accordingly;
b)	if any, a non zero target speed value at the EOA/LOA shall be set to zero.
second part of a is realized with A3.4 e
realised by: #REQ-UNISIG-SUB026-0484#REF#
realised by: #REQ-UNISIG-SUB026-2205#REF#

#REQ-UNISIG-SUB026-0484#REF# 3.8.4.1.2 #REQ-UNISIG-SUB026-010510#REF#
When the End Section timer value becomes greater than the time-out value given by trackside, the following shall apply:
a) The EOA/LOA shall be withdrawn to the current position of the train.
b) if any, a non zero target speed value at the EOA/LOA shall be set to zero.
#TEST-VAL-SUB026-3796#REF# EET CFX00040095 Overlap and End Section outside of end section
#TEST-VAL-SUB026-3705#REF# FCT a) EoA MA repetition while end section timer running (timer value increased)
#TEST-VAL-SUB026-3081#REF# FCT a) LoA, b) MA with end section timer FS/L2

#REQ-UNISIG-SUB026-3656:01#REF# 3.8.4.1.3
In case no End Section timer is running when the on-board receives a new MA with an End Section timer start location in rear of the max safe
front end of the train, the on-board shall consider that the End Section timer value became greater than its time-out value and apply 3.8.4.1.2.
TEST APPROACH:
The following aspects have been identified:
1) min safe front end < timer start location < max safe front end
2) timer start location < min safe front end < max safe front end
#TEST-VAL-SUB026-3707#REF# FCT 1 New valid MA is received - min safe front end < End Section timer start location < max safe front end
#TEST-VAL-SUB026-3708#REF# FCT 2 New valid MA is received - End Section timer start location < min safe front end < max safe front end
#TEST-VAL-SUB026-3796#REF# EET error expectation Overlap and End Section outside of end section

#REQ-UNISIG-SUB026-3655:01#REF# 3.8.4.1.4
In case an End Section timer is already running when the on-board receives a new MA with an End Section timer start location in rear of the max
safe front end of the train, the on-board shall keep the End Section timer running but replace the time-out value with the value received with
the new MA.
TEST APPROACH:
The following aspects have been identified:
1) timer decreased to expired value (MA repetition)
2) timer decreased to not yet expired value (MA repetition)
3) timer increased (MA repetition)
4) reception of new MA
#TEST-VAL-SUB026-3792#REF# FCT 1 MA repetition while end section timer running (timer already expired with new timer value)
#TEST-VAL-SUB026-3791#REF# FCT 2 MA repetition while end section timer running (timer value decreased)
#TEST-VAL-SUB026-3705#REF# FCT 3 MA repetition while end section timer running (timer value increased)
#TEST-VAL-SUB026-3793#REF# FCT 4 Reception of new MA while end section timer running (new timer start location already passed)

#REQ-UNISIG-SUB026-3719#REF# to.3.8.4.1.4
In case an End Section timer is already running when the Onboard equipment receives a new MA with an End Section timer and the start location of
this new Section Timer is not passed with max safe front end, the Onboard equipment shall stopped the current End Section timer and supervise
the End Section Timer from the new MA.
clarification:
when the new timer start location is not passed, the current timer supervision can stopped.
#TEST-VAL-SUB026-3794#REF# FCT basic function Reception of new MA while end section timer running (new timer start location not yet passed)

#REQ-UNISIG-SUB026-0029#REF# 3.8.4.2.1
The on-board shall start a Section timer for each section:
a)	For Level 2: at the value of the time stamp of the message including the MA.
b)	For Level 1: at the time of passage over the first encountered balise of the balise group giving the MA.
#TEST-VAL-SUB026-3341#REF# EET CFX00034622 Fahrzeugreaktion auf identische Baliseninhalte, Linking available
#TEST-VAL-SUB026-3082#REF# FCT a) Section Time Outs, L2
#TEST-VAL-SUB026-3083#REF# FCT b) Section Time Outs, L1

#REQ-UNISIG-SUB026-3283#REF# to.3.8.4.2.1 #ANA-UNISIG-MAData-0001#REF#
If received a new valid MA with section timer the section timer shall be started only, if the train not passed the timer stop location with min
safe front end.
TEST APPROACH:
The following aspects have been identified:
1) min safe front end < section timer stop location < estimated front end
2) section timer stop location < min safe front end < estimated front end
#TEST-VAL-SUB026-3710#REF# FCT 1 MA - section timer stop location passed with estimated front end
#TEST-VAL-SUB026-3711#REF# FCT 2 MA - section timer stop location passed with min safe front end

#REQ-UNISIG-SUB026-001558#REF# 3.8.4.2.2
When a Section timer value becomes greater than the time-out value given by trackside, the following shall apply:
a)	the EOA/LOA and the SvL shall be withdrawn to the entry point of the revoked section. Refer to appendix A.3.4 for the exhaustive list of
location based information stored on-board, which shall be deleted accordingly;
b)	the National/ Default Value of the Release Speed shall apply ;
c)	if any, a non zero target speed value at the EOA/LOA shall be set to zero.
second part of a is realized with   A3.4.1.2 c
realised by: #REQ-DESIGN-CR-0486:01#REF#
realised by: #REQ-UNISIG-SUB026-2203#REF#

#REQ-DESIGN-CR-0486:01#REF# 3.8.4.2.2 #REQ-UNISIG-SUB026-001558#REF#
When a Section timer value becomes greater than the time-out value given by trackside, the following shall apply:
a) the EOA/LOA and the SvL shall be withdrawn to the entry point of the revoked section.
b) the National/ Default Value of the Release Speed shall apply ;
c) if any, a non zero target speed value at the EOA/LOA shall be set to zero.
Rel. 8.0:
"and SvL" is new
TEST APPROACH:
The following aspects have been identified:
1) MA with EoA and SvL
2) MA with LoA and SvL
#TEST-VAL-SUB026-3997#REF# FCT 1 Section timeout effect on Release/Target speed
#TEST-VAL-SUB026-3927#REF# FCT 2 Handling of V_LOA when MA section time out expires
#TEST-VAL-SUB026-5220#REF# EET error expectation Section timer expiry after MA shortening (two sections, T_SECTIONTIMER_1 < T_SECTIONTIMER_2, train inside first section)
#TEST-VAL-SUB026-5221#REF# EET error expectation Section timer expiry after MA shortening (two sections, T_SECTIONTIMER_1 > T_SECTIONTIMER_2, train inside first section)
#TEST-VAL-SUB026-5222#REF# EET error expectation Section timer expiry after MA shortening (train out inside concerned section)

#REQ-UNISIG-SUB026-0486#REF# 3.8.4.2.3
The Section timer shall be stopped when the min safe front end of the train has passed the associated Section timer stop location.
#TEST-VAL-SUB026-3330#REF# EET CFX00033759 MA in level transition buffer, Section timeout before level transition takes place
#TEST-VAL-SUB026-3331#REF# EET CFX00033759 MA in level transition buffer, pass section timer stop location after level transition (before section timeout)
#TEST-VAL-SUB026-3332#REF# EET CFX00033759 MA in level transition buffer, section timer stop location passed before level transition takes place
#TEST-VAL-SUB026-3084#REF# FCT basic function Section timer stop location

#REQ-UNISIG-SUB026-006962#REF# to.3.8.4.2.3 #ANA-UNISIG-MAData-0010#REF#
Section timer shall be stopped also, when
- a MA is shortened because A3.4
AND
- the begin of the section is behind the new stop location.
#TEST-VAL-SUB026-5285#REF# FCT basic function Begin of the section is behind the new stop location

#REQ-UNISIG-SUB026-0030#REF# 3.8.4.3.1
The on-board shall start a timer for the speed at the EOA/LOA:
a)	For Level 2: at the value of the time stamp of the message including the MA.
b)	For Level 1: at the time of passage over the first encountered balise of the balise group giving the MA.
#TEST-VAL-SUB026-3085#REF# FCT a LOA speed timer
#TEST-VAL-SUB026-3086#REF# FCT b LOA speed timer, L1

#REQ-UNISIG-SUB026-001575#REF# 3.8.4.3.2
When the LOA speed timer value becomes greater than the time-out value given by trackside, the speed  associated with the EOA/LOA shall be set
to zero (i.e. the Limit of Authority becomes an End of Authority and the SvL is defined on-board according to 3.8.4.5). Refer to appendix A.3.4
for the exhaustive list of location based information stored on-board, which shall be deleted accordingly.
the second part is realized with  A.3.4.1.2 n
realised by: #REQ-UNISIG-SUB026-0487:01#REF#
realised by: #REQ-UNISIG-SUB026-010117#REF#

#REQ-UNISIG-SUB026-0487:01#REF# 3.8.4.3.2 #REQ-UNISIG-SUB026-001575#REF#
When the LOA speed timer value becomes greater than the time-out value given by trackside, the speed  associated with the EOA/LOA shall be set
to zero, i.e. the Limit of Authority becomes an End of Authority, and the SvL is defined on-board according to #REQ-UNISIG-SUB026-0032#REF#.

remark: At this time the ma is normally supervised with an EoA and SvL including release speed.
TEST APPROACH:
The following aspects have been identified:
1) MA with LoA and no SvL
2) MA with LoA and SvL
#TEST-VAL-SUB026-3085#REF# FCT 1 LOA speed timer
#TEST-VAL-SUB026-7060#REF# FCT 2 LOA timer expiry, MA includes DP and OL

#REQ-UNISIG-SUB026-0031:01#REF# 3.8.4.4.1
The Overlap timer shall be started on-board when the train passes the Overlap timer start location given by trackside with its max safe front
end. The timer shall be considered as started even if a time-out value “infinite” is given.
Rel. 8.0:
the last sentence is new
#TEST-VAL-SUB026-3088#REF# FCT basic function SvL: Overlap=>DP

#REQ-UNISIG-SUB026-001581#REF# 3.8.4.4.2
When the Overlap timer value becomes greater than the time-out value given by trackside, the following shall apply:
a)	the overlap information shall be deleted, i.e. the Supervised Location shall be withdrawn to the Danger Point if there is any or else to
the EOA. Refer to appendix A.3.4 for the exhaustive list of location based information stored on-board, which shall be deleted accordingly.
b)	the release speed associated with the Overlap shall be deleted
c)	if any, a non zero target speed value at the EOA/LOA shall be set to zero.
the second part of a)  is realized with  A.3.4.1.2 d
realised by: #REQ-UNISIG-SUB026-0488:01#REF#
realised by: #REQ-UNISIG-SUB026-2204#REF#

#REQ-UNISIG-SUB026-0488:01#REF# 3.8.4.4.2 #REQ-UNISIG-SUB026-001581#REF#
When the Overlap timer value becomes greater than the time-out value given by trackside, the following shall apply:
a) the overlap information shall be deleted, i.e. the Supervised Location shall be withdrawn to the Danger Point if there is any or else to the
EOA.
b) the release speed associated with the Overlap shall be deleted
c) if any, a non zero target speed value at the EOA/LOA shall be set to zero.
TEST APPROACH:
The following aspects have been identified:
1) DP becomes the new SvL
2) EoA becomes the new SvL
3) LoA becomes the new EoA and SvL
#TEST-VAL-SUB026-3088#REF# FCT 1 SvL: Overlap=>DP
#TEST-VAL-SUB026-3706#REF# FCT 2 MA repetition while overlap timer running
#TEST-VAL-SUB026-3070#REF# FCT 3 MA-Request triggered by MA shortening

#REQ-UNISIG-SUB026-0489:02#REF# 3.8.4.4.3
If the train comes to a standstill after the Overlap timer has been started, the on-board shall consider that the Overlap timer value became
greater than its time-out value and shall apply 3.8.4.4.2.
#TEST-VAL-SUB026-3089#REF# FCT basic function Overlap wird bei Stillstand freigegeben

#REQ-UNISIG-SUB026-009836#REF# to.3.8.4.4.3
When the train received a movement authority in standstill and the overlap timer start location is passed, the overlap is considered as released
also.
clarification:3.8.4.4.3 is applied also for a received ma in standstill
#TEST-VAL-SUB026-3829#REF# FCT basic function Reception of T_OL =1023 - overlap timer start location is overran already with max safe front end

#REQ-UNISIG-SUB026-3661:02#REF# 3.8.4.4.4
In case no Overlap timer is running when the on-board receives a new MA with an Overlap timer start location in rear of the max safe front end
of the train, the on-board shall consider that the Overlap timer value became greater than its time-out value and shall apply 3.8.4.4.2.
remark:
an infinite timer is also a running timer (see 3.8.4.4.1)
#TEST-VAL-SUB026-3829#REF# FCT basic function Reception of T_OL =1023 - overlap timer start location is overran already with max safe front end

#REQ-UNISIG-SUB026-3657:01#REF# 3.8.4.4.5
In case an Overlap timer is already running when the on-board receives a new MA with an Overlap timer start location in rear of the max safe
front end of the train, the on-board shall keep the Overlap timer running but replace the Overlap time-out value with the value received with
the new MA.
#TEST-VAL-SUB026-3706#REF# FCT basic function MA repetition while overlap timer running

#REQ-UNISIG-SUB026-3720#REF# to.3.8.4.4.5
In case an Overlap timer is already running when the Onboard equipment receives a new MA with an Overlap timer and the start location of this
new Overlap Timer is not passed with max safe front end, the Onboard equipment shall stopped the current Overlap timer and supervise the Overlap
Timer from the new MA.
clarification:
when the new timer start location is not passed, the current timer supervision can stopped.
#TEST-VAL-SUB026-3839#REF# FCT basic function T_OL is already running when the OBU receives a new MA with an T_OL and the start location not passed with max safe front end yet

#REQ-UNISIG-SUB026-0032#REF# 3.8.4.5.1
The Supervised Location (SvL) shall be defined on board as;
a)	the end of overlap (if any and before time-out).
b)	if not, the Danger Point (if any).
c)	if not, the End Of Authority.
#TEST-VAL-SUB026-3737#REF# FCT a, b DP supervision in FS
#TEST-VAL-SUB026-3735#REF# FCT c EoA supervision in FS
#TEST-VAL-SUB026-3271#REF# EET error expectation MA with OL < DP
#TEST-VAL-SUB026-3734#REF# EET error expectation DP supervision in FS
#TEST-VAL-SUB026-3738#REF# EET error expectation End of overlap supervision in FS

#REQ-UNISIG-SUB026-001603#REF# 3.8.4.5.2
As long as a Limit of Authority is supervised, no SvL shall be defined on-board.
#TEST-VAL-SUB026-3927#REF# FCT basic function Handling of V_LOA when MA section time out expires

#REQ-UNISIG-SUB026-010596#REF# to.3.8.4.5.2
exception to #REQ-UNISIG-SUB026-001603#REF#:
If a EoA is temporarily supervised without an SvL (i.e. supervision of the begin of a mode profile) and the regular end of the movement
authority is a LoA, an additional required temporary SvL shall be set to the LoA.

The temporary EoA has to be supervised like an EoA and SvL, if located behind the LoA.
UNISIG clarification: a SvL is necessary, when a EoA has to be supervised.
TEST APPROACH:
The following aspects have been identified:
1) temporary EoA in front of the LoA
2) temporary EoA behind the LoA
#TEST-VAL-SUB026-7671#REF# FCT 1, 2 MP together with MA with LoA

#REQ-UNISIG-SUB026-3338#REF# 3.8.4.6.2
An infill MA shall be evaluated on-board only if the on-board equipment is in FS or LS mode.
realize through 4.8.4.1.1 line infill location reference
realised by: #REQ-UNISIG-SUB026-0755:01#REF#

#REQ-UNISIG-SUB026-0035#REF# 3.8.4.6.4
An infill MA shall be evaluated on-board only if the linking information, regarding the main signal balise group to which it refers, is
available.
UNISIG clarification:
this is not restricted to infill ma. all infill information should be ignored in this case.
realised by: #REQ-UNISIG-SUB026-3124#REF#

#REQ-UNISIG-SUB026-010536#REF# 3.8.4.6.5
The on-board shall start a Section timer for each section beyond the next main signal:
a)	When the infill information is received from a balise group at the time of passing the first encountered balise of the infill balise
group.
b)	When the infill information is received from a loop at the time of receiving the loop message.
c)	When the infill information is received from a radio infill unit at the value of the time stamp of the radio infill message including
the MA.
radio infill is not realized
realised by: #REQ-UNISIG-SUB026-0036:01#REF#

#REQ-UNISIG-SUB026-0036:01#REF# 3.8.4.6.5 #REQ-UNISIG-SUB026-010536#REF#
The on-board shall start a Section timer for each section beyond the next main signal:
a)	When the infill information is received from a balise group at the time of passing the first encountered balise of the infill balise
group.
b)	When the infill information is received from a loop at the time of receiving the loop message.
#TEST-VAL-SUB026-3093#REF# FCT a) Section timer from in-fill BG
#TEST-VAL-SUB026-3094#REF# FCT b) Section timer und loop

#REQ-UNISIG-SUB026-0037#REF# 3.8.5.1 #REQ-UNISIG-SUB026-010151#REF#
A new MA shall replace a previously received MA in the following ways:
a)	When the new MA is given from a balise group at a main signal (i.e. not infill information) or from the RBC all data included in the
previous MA shall be replaced by the new data.
b)	When the new MA is given as infill information all data beyond the announced balise group at the next main signal shall be replaced.
TEST APPROACH:
The following aspects have been identified:
1) a
2) b
3) replacement of MA in transition buffer
3.1) MA revoked by trip order
3.2) trip order revoked by MA
3.3) trip order revoked by infill MA
#TEST-VAL-SUB026-3095#REF# FCT 1 New MA replaces old MA
#TEST-VAL-SUB026-4H36#REF# FCT 2 In-fill MA expanded by new in-fill MA
#TEST-VAL-SUB026-3843#REF# FCT 3.1 Buffered valid MA overwritten by later buffered TRIP command
#TEST-VAL-SUB026-3842#REF# FCT 3.2 Buffered TRIP command overwritten by later buffered valid MA
#TEST-VAL-SUB026-3844#REF# FCT 3.3 Buffered TRIP command overwritten by later buffered infill MA
#TEST-VAL-SUB026-3096#REF# EET CFX00034645 Infill MA replaces old MA beyond reference location
#TEST-VAL-SUB026-5201#REF# EET CFX00035801 Verarbeitung einer Infill-MA nach Transiiton L2/FS nach L1/FS
#TEST-VAL-SUB026-4415#REF# EET CFX00038403 Gap in MA
#TEST-VAL-SUB026-3866#REF# EET error expectation Last MA from level transition buffer valid after level transition
#TEST-VAL-SUB026-4H37#REF# EET error expectation In-fill MA expanded by new in-fill MA before former in-fill location reference passed
#TEST-VAL-SUB026-7105#REF# EET error expectation MA with SvL replaced by MA defining LoA
#TEST-VAL-SUB026-7609#REF# EET error expectation Brake intervention due to passed SBIC/EBIC revoked due to in-fill MA

#REQ-UNISIG-SUB026-001628#REF# 3.8.5.1.2
When an infill MA is received, the on-board shall start a new MA section at the infill location reference, i.e. the balise group at the next
main signal (see 3.6.2.3.1).
TEST APPROACH:
The following aspects have been identified:
1) basic function
2) infill timer expiry after passage of infill location reference
3) infill timer expiry before passage of infill location reference
#TEST-VAL-SUB026-3093#REF# FCT 1 Section timer from in-fill BG
#TEST-VAL-SUB026-4E35#REF# FCT 2 When an infill MA is received, the on-board shall start a new MA section at the infill location reference
#TEST-VAL-SUB026-4E34#REF# FCT 3 When an infill MA is received, the on-board shall start a new MA section at the infill location reference
#TEST-VAL-SUB026-3092#REF# EET error expectation In-fill and repositioning
#TEST-VAL-SUB026-3286#REF# EET error expectation In-fill and repositioning
#TEST-VAL-SUB026-5958#REF# EET error expectation Extention of infill MA by new infill MA

#REQ-UNISIG-SUB026-001630#REF# 3.8.5.1.3
If the SvL defined from the new MA is closer than the one supervised with the former MA, this shall be considered by the on-board equipment as
an MA shortening. Refer to appendix A.3.4 for the exhaustive list of location based information stored on-board, which shall be deleted
accordingly.
the reference to A.3.4 is realized with  A.3.4.1.2 b
realised by: #REQ-UNISIG-SUB026-010120#REF#
realised by: #REQ-UNISIG-SUB026-2202#REF#

#REQ-UNISIG-SUB026-010120#REF# 3.8.5.1.3 #REQ-UNISIG-SUB026-001630#REF#
If the SvL defined from the new MA is closer than the one supervised with the former MA, this shall be considered by the on-board equipment as
an MA shortening.
#TEST-VAL-SUB026-4E31#REF# FCT basic function MA shortened when new MA defined SvL is before current SvL

#REQ-UNISIG-SUB026-001632#REF# 3.8.5.1.4
If a new MA defines an SvL while the on-board was supervising an LOA, this shall always be considered by the on-board equipment as an MA
shortening regardless of the SvL location. Refer to appendix A.3.4 for the exhaustive list of location based information stored on-board, which
shall be deleted accordingly.
the reference to A.3.4 is realized with  A.3.4.1.2 b
realised by: #REQ-UNISIG-SUB026-010121#REF#
realised by: #REQ-UNISIG-SUB026-2202#REF#

#REQ-UNISIG-SUB026-010121#REF# 3.8.5.1.4 #REQ-UNISIG-SUB026-001632#REF#
If a new MA defines an SvL while the on-board was supervising an LOA, this shall always be considered by the on-board equipment as an MA
shortening regardless of the SvL location.

Remark: This means, that the new MA doesn't give a new LoA (see 3.8.4.5.2).
#TEST-VAL-SUB026-4E32#REF# FCT basic function MA shortened when LOA on board and new MA defined an SvL

#REQ-UNISIG-SUB026-010632#REF# 3.8.5.2
It shall be possible to update the length of the current section by means of repositioning information (see section 3.8.5.3).

#REQ-DESIGN-CR-0184:01#REF# to.3.8.5.2
If repositioning information are received and accepted, obu shall re-evaluate the current ma including the length of the current section
according to the repositioning information in reference to the repositioning balise group.

remark:
The not yet reached timer start/stop locations shall be evaluated new too.
UNISIG clarification:
The current ma is evaluated new at the position of the repositioning balise group
TEST APPROACH:
The following aspects were identified:
1) MA update by repositioning information
2) SSP/GP checked for MA expansion
3) combination of repositioning and infill
4) section timer supervision after MA expansion
#TEST-VAL-SUB026-3306#REF# FCT 1 MA update by Repositioning information
#TEST-VAL-SUB026-3305#REF# FCT 2 GP und SSP überdecken die Repositioning Informationen nicht
#TEST-VAL-SUB026-3754#REF# FCT 3 combination of repositioning information and infill MA+MP-LS
#TEST-VAL-SUB026-3097#REF# FCT 4 Aufwertung MA durch angekündigtes Pkt 16 - unangekündigtes Pkt 16 wird verworfen
#TEST-VAL-SUB026-3755#REF# EET error expectation LS combination of repositioning information and infill MA+MP-OS
#TEST-VAL-SUB026-5617#REF# EET error expectation Indication of MRSP start limit (nominal) and SSP indication (save position) does not lead to unreasonable planning area information on DMI
#TEST-VAL-SUB026-7992#REF# EET error expectation Repositioning information received between EoA and SvL

#REQ-DESIGN-CR-0200#REF# 3.8.5.2.2
Repositioning information contained in a balise group message shall only be evaluated if linking information has announced a following balise
group as unknown but containing repositioning information.
#TEST-VAL-SUB026-3097#REF# FCT basic function Aufwertung MA durch angekündigtes Pkt 16 - unangekündigtes Pkt 16 wird verworfen

#REQ-DESIGN-CR-0397#REF# to.3.8.5.2.2
Only packet 16 (repositioning information) shall be ignored in the case the balise group was properly linked. All other information in the same
message shall be used as defined in the SRS.Route unknown is not the only situation in which repositioning can be applied. It can also be used
if the length of a section of the MA is only known at a later location.
UNISIG clarification:
a definition for evaluation P16 is necessary, when repositioning is not announced.
#TEST-VAL-SUB026-3097#REF# FCT basic function Aufwertung MA durch angekündigtes Pkt 16 - unangekündigtes Pkt 16 wird verworfen

#REQ-UNISIG-SUB026-001644#REF# 3.8.5.2.4
The reception of repositioning information or of a new MA with an LOA shall not be considered as an MA shortening by the on-board equipment.
TEST APPROACH:
The following aspects have been identified:
1) new MA with LoA
2) Repositioning information
#TEST-VAL-SUB026-4E31#REF# FCT 1 MA shortened when new MA defined SvL is before current SvL
#TEST-VAL-SUB026-4E33#REF# FCT 2 The reception of repositioning information oshall not be considered as an MA shorten

#REQ-UNISIG-SUB026-0038:01#REF# 3.8.6.1
It shall be possible to shorten a given MA using a special procedure between on-board equipment and RBC. The procedure is as follows:
a)	The RBC proposes a new MA with an EOA closer to the train than the current EOA, optionally with a mode profile.
b)	The ERTMS/ETCS on-board equipment shall check the train front end position versus the Indication supervision limit of the proposed
shortened MA.
  If it is in rear, the on-board equipment shall accept the new MA.
  If it is in advance, the request shall be rejected and the previously received MA remains valid
c)	The RBC shall be informed about the decision.
part a is only trackside
realised by: #REQ-UNISIG-SUB026-8087#REF#

#REQ-UNISIG-SUB026-8087#REF# 3.8.6.1 #REQ-UNISIG-SUB026-0038:01#REF#
#ANA-UNISIG-ShortenMA-0002#REF#
If a request to shorten a ma is received from RBC, the ERTMS/ETCS on-board equipment shall check the train front end position versus the
Indication supervision limit of the proposed shortened MA.
- If it is in rear, the on-board equipment shall accept the new MA
- If it is in advance, the request shall be rejected, and the previously received MA remains valid.

The RBC shall be informed about the decision.
#TEST-VAL-SUB026-5247#REF# EET CFX00040283 M137/M138 and short outage of safe connection
#TEST-VAL-SUB026-3098#REF# FCT basic function Cooperative shortenting of MA
#TEST-VAL-SUB026-4419#REF# EET error expectation Shorten MA on L1 MA

#REQ-UNISIG-SUB026-3128:01#REF# to.3.8.6.1 #ANA-UNISIG-ShortenMA-0001:01#REF#
Ist die neue MA vom Request to Shorten MA länger als die aktuell gültige MA und diese vollständig durch die aktuell an Bord befindlichen
Streckenbeschreibungen abgedeckt, ist die neue MA entsprechend 3.8.6.1 b zu behandeln.

Ist die neue MA dagegen nicht vollständig durch die aktuell an Bord befindlichen Streckenbeschreibungen abgedeckt, ist sie inkl. eines eventuell
vorhandenen Modeprofiles zu ignorieren. Das Ignorieren ist mit einer Diagnosemeldung zu dokumentieren.

Anmerkung: Im Falles des Ignorierens bedeutet dies, dass das Fahrzeug an das RBC keine Antwort auf den Request sendet.
#TEST-VAL-SUB026-3714#REF# FCT basic function acceptance Request To Shorten MA, new MA longer than current MA, train can be stopped without brake intervention at the requested location
#TEST-VAL-SUB026-3715#REF# EET error expectation acceptance Request To Shorten MA, new MA longer than current MA, within brake intervention curve for current SvL
#TEST-VAL-SUB026-3747#REF# EET error expectation SSP/GP/TC shorten by granted Request To Shorten MA which exceeds current MA

Chapter 3.9

#REQ-UNISIG-SUB026-0039#REF# 3.9.1.1
It shall be possible to transmit infill information to the on-board equipment using
a)	Balise groups
b)	Euroloops
c)	Radio infill units.
realised by: #REQ-UNISIG-SUB026-0355:02#REF#
realised by: #REQ-UNISIG-SUB026-0390#REF#

#REQ-UNISIG-SUB026-0493#REF# 3.9.1.3
If the on-board system is not equipped with the infill transmission media as requested by the announcement balise group, the announcement
information shall be ignored by the on-board equipment and the train shall proceed according to the previously received information.
TEST APPROACH:
The requirement aspect radio infill is covered by #REQ-SRS-004408#REF#, #REQ-UNISIG-SUB026-3540:01#REF# and #REQ-UNISIG-SUB026-3636:01#REF#.
#TEST-VAL-SUB026-3102#REF# FCT basic function Loop in-fill not supported in the configuration

#REQ-DESIGN-CR-0752#REF# 3.9.2.2
New EOLM information shall replace previously received EOLM information (for the same direction).

Note: New EOLM information with the same content as previously received EOLM information does not cause any changes in regard to acceptance of
the loop message.
remark: a clarification is necessary, when the obu receives a new EOLM	during an active Loop
#TEST-VAL-SUB026-3886#REF# FCT basic function Effect on receipt of new EoLM data on already existing EoLM data

#REQ-UNISIG-SUB026-0498#REF# 3.9.2.6
The on-board shall only accept information coming from the loop with the announced identity.
#TEST-VAL-SUB026-3886#REF# FCT EOL information available Effect on receipt of new EoLM data on already existing EoLM data
#TEST-VAL-SUB026-3260#REF# FCT no EOL information Loop-Daten ohne EOLM

#REQ-UNISIG-SUB026-0500#REF# 3.9.2.10
The on-board shall be prepared to receive messages from the Euroloop after passing the EOLM.
TEST APPROACH:
The following aspects have been identified:
1) basic software functionality 
2) software hardware integration (including evaluation of Q_SSCODE) 
#TEST-VAL-SUB026-3105#REF# FCT 1 Acceptance of the loop information after passing the EOLM
#TEST-SWHWINT-PERFORMANCE-0011#REF# PER 2 Empfang einer MA über Euroloop (EOLM) -> Update des Vorschaubereichs am DMI

#REQ-UNISIG-SUB026-0501#REF# 3.9.2.11
When the on-board equipment reads the next main signal balise group or when it detects that the next main signal balise group was missed, new
infill information possibly received from the loop shall be ignored.
This is  generally valid for infill information from all allowed media - see 3.8.4.6.4
realised by: #REQ-UNISIG-SUB026-3124#REF#

#REQ-UNISIG-SUB026-0502#REF# 3.9.2.12
The distances given in an EOLM (distance to loop, length of loop) are used for diagnostic purpose only. They shall therefore not be used to
restrict reception of loop telegrams to specific locations.
#TEST-VAL-SUB026-3107#REF# FCT basic function The distances given in an EOLM do not restrict reception of loop telegrams to specific locations

#REQ-UNISIG-SUB026-001766#REF# 3.9.3.3
The order to establish a communication session shall be ignored:
a)	Intentionally deleted.
b)	If the on-board equipment does not include radio.
The order to establish a session to a Radio Infill Unit via packet 133 is meant
realised by: #REQ-UNISIG-SUB026-010481#REF#

#REQ-UNISIG-SUB026-010481#REF# 3.9.3.3 #REQ-UNISIG-SUB026-001766#REF#
If the on-board equipment does not include radio, the order to establish a communication session with a Radio Infill Unit shall be ignored.
radio infill shall not be realized
#TEST-VAL-SUB026-8061#REF# FCT basic function Packet 133 (Radio-infill Area Information) shall be ignored

#REQ-UNISIG-SUB026-001772#REF# 3.9.3.5
If the order to establish a communication session with a radio infill unit sent via balise groups is received by an on-board equipment,
connected with another radio infill unit(s), two cases may arise:
realised by: #REQ-UNISIG-SUB026-010213#REF#
realised by: #REQ-UNISIG-SUB026-010214#REF#

#REQ-UNISIG-SUB026-001774#REF# 3.9.3.5.1
Case 1: the on-board can handle only one communication session at a time. In this case, the onboard shall (unless §3.9.3.5.1.1 applies):
a)	terminate the existing communication session at the location indicated in the order
b)	establish a communication session with the RIU indicated in the order as soon as action a) is completed.
realised by: #REQ-UNISIG-SUB026-010213#REF#

#REQ-UNISIG-SUB026-001778#REF# 3.9.3.5.1.1
The order shall be ignored in case it refers to an RIU with which a session is currently being established or is already established.
radio infill shall not be realized

is the same as 3.5.3.4.1
realised by: #REQ-UNISIG-SUB026-000862#REF#

#REQ-UNISIG-SUB026-010213#REF# 3.9.3.5.1 #REQ-UNISIG-SUB026-001772#REF#
#REQ-UNISIG-SUB026-001774#REF#
If the order to establish a communication session with a radio infill unit sent via balise groups is received by an on-board equipment,
connected with another radio infill unit(s) and the on-board can handle only one communication session at a time.
In this case, the onboard shall:
a) terminate the existing communication session at the location indicated in the order
b) establish a communication session with the RIU indicated in the order as soon as action a) is completed.
radio infill shall not be realized

#REQ-UNISIG-SUB026-001780#REF# 3.9.3.5.2
Case 2: the on-board can handle more than one communication session at a time. In this case, at the location indicated in the order the on-board
shall:
a)	terminate any communication session existing with RIU(s) not indicated in the order
b)	as soon as a new communication session can be handled, establish a communication session with the RIU indicated in the order, unless
currently being established or already established with the said RIU.
realised by: #REQ-UNISIG-SUB026-010214#REF#

#REQ-UNISIG-SUB026-010214#REF# 3.9.3.5.2 #REQ-UNISIG-SUB026-001772#REF#
#REQ-UNISIG-SUB026-001780#REF#
If the order to establish a communication session with a radio infill unit sent via balise groups is received by an on-board equipment,
connected with another radio infill unit(s) and the on-board can handle more than one communication session at a time. In this case, at the
location indicated in the order the on-board shall:
a) terminate any communication session existing with RIU(s) not indicated in the order
b) as soon as a new communication session can be handled, establish a communication session with the RIU indicated in the order, unless
currently being established or already established with the said RIU.
radio infill shall not be realized

#REQ-UNISIG-SUB026-001784#REF# 3.9.3.6
If the order to establish a communication session with a radio infill unit sent via Radio Infill unit is received by an on-board equipment:
a)	If the on-board can handle only one communication session, the order shall be ignored.
b)	If the on-board can handle two communication sessions simultaneously and only one session is ongoing, the existing communication session
shall be maintained and the new one shall be established.
c)	If the on-board can handle two communication sessions simultaneously and two sessions are ongoing, then the communication session
related to the current infill area shall be maintained, the other one shall be terminated and the new one shall be established.
packet 143 is meant

radio infill shall not be realized

#REQ-UNISIG-SUB026-001799#REF# 3.9.3.10
The on-board equipment shall inform the radio infill unit
a)	As soon as the location indicated in the order sent via balise groups is passed (i.e. entry of the train in the infill area)
b)	As soon as the next main signal balise group indicated in the order sent via balise groups is read or the on-board equipment detects
that it was missed.
radio infill shall not be realized

#REQ-UNISIG-SUB026-001803#REF# 3.9.3.11
The information sent to the radio infill unit by the on-board equipment shall include
a)	Train identity (ETCS-ID of the on-board equipment)
b)	Position report
c)	Identifier of the next main signal balise group
d)	Time stamp
radio infill shall not be realized

#REQ-UNISIG-SUB026-001825#REF# 3.9.3.14
The radio infill unit shall evaluate the time stamp according to the principles of section 3.16.3.2.
The on-board equipment shall check the consistency of radio infill data, according to the principles of section 3.16.3.1 and 3.16.3.3.
first part is only trackside
realised by: #REQ-UNISIG-SUB026-010480#REF#

#REQ-UNISIG-SUB026-010480#REF# 3.9.3.14 #REQ-UNISIG-SUB026-001825#REF#
The on-board equipment shall check the consistency of radio infill data according to the same principles as RBC data.
radio infill shall not be realized

#REQ-UNISIG-SUB026-001827#REF# 3.9.3.15
When the on-board equipment reads the next main signal balise group or when it detects that the next main signal balise group was missed, new
infill information related to this balise group possibly received shall be ignored.
radio infill shall not be realized

#REQ-UNISIG-SUB026-001829#REF# 3.9.3.16
The on-board equipment shall terminate the communication session according to the orders received from the trackside (balise group or Radio
Infill units).
is realized through 3.5.5.1 a
realised by: #REQ-UNISIG-SUB026-000952#REF#

Chapter 3.10

#REQ-UNISIG-SUB026-0504:01#REF# 3.10.1.3.1
If the on-board receives a new message with the same identifier it shall replace the previous one.
#TEST-VAL-SUB026-3109#REF# FCT Conditional Emergency Stop New Emergency message with the same identifier replaces the previous one (CES)
#TEST-VAL-SUB026-5882#REF# FCT Unconditional Emergency Stop New message with the same identifier replaces the previous one (UCES)

#REQ-UNISIG-SUB026-3558#REF# to.3.10.1.3.1 #ANA-UNISIG-EmergencyMessage-0002#REF#
If the on-board receives a new emergency message with the same identifier, the new emergency stop shall be evaluated and acknowledged with the
criteria of the new message.
#TEST-VAL-SUB026-3718#REF# FCT Conditional Emergency Stop Reception of several Conditional Emergency Stop with same ID
#TEST-VAL-SUB026-3719#REF# FCT Unconditional Emergency Stop Reception of several Unconditional Emergency Stop with same ID
#TEST-VAL-SUB026-7166#REF# EET error expectation Replacement of CES within transtion buffer

#REQ-UNISIG-SUB026-3559#REF# to.3.10.1.3.1 #ANA-UNISIG-EmergencyMessage-0003#REF#
Exception to 3.10.1.3:
If the on-board receives a new emergency message with the same identifier, but this emergency stop is rejected (for instance the on board has
passed the new stop location with min safe front end), the new message shall not replace the previous one.
Einschränkung ist notwendig, da andernfalls das Warten auf die Revocation mit der Überschreibung gelöscht wird.
#TEST-VAL-SUB026-3718#REF# FCT basic function Reception of several Conditional Emergency Stop with same ID

#REQ-UNISIG-SUB026-0505#REF# 3.10.1.4
Each emergency message to an on-board equipment shall be acknowledged, using the corresponding emergency message identification number.
#TEST-VAL-SUB026-3110#REF# FCT CES Ackknowledgement der Emergency Message
#TEST-VAL-SUB026-4584#REF# FCT UCES mode transition SR-TR[20]
#TEST-VAL-SUB026-3855#REF# EET error expectation Acknowledgment of Emergency Stop messages
#TEST-VAL-SUB026-3992#REF# EET error expectation Ack of Conditional and Unconditional emergency msg sent with lvlTransOrder

#REQ-UNISIG-SUB026-001855#REF# 3.10.2.2
A conditional emergency stop message shall contain the information of a new stop location, referred to the LRBG. In case, when receiving this
message
  the train has already passed with its min safe front end the new stop location, the emergency stop message shall be rejected and the RBC shall
be informed.
  the train has not yet passed with its min safe front end the new stop location, the emergency stop message shall be accepted, however this
location shall be used by the onboard to define the new EOA and SvL only if not beyond the current EOA. Refer to appendix A.3.4 for the
exhaustive list of location based information stored on-board, which shall be deleted accordingly.
The reference to A3.4. is realized through A3.4.1.2 a
realised by: #REQ-DESIGN-CR-0470:01#REF#
realised by: #REQ-UNISIG-SUB026-2201#REF#

#REQ-DESIGN-CR-0470:01#REF# 3.10.2.2 #REQ-UNISIG-SUB026-001855#REF#
A conditional emergency stop message shall contain the information of a new stop location, referred to the LRBG.
In case, when receiving this message
* the train has already passed with its min safe front end the new stop location, the emergency stop message shall be ignored and the RBC shall
be informed.
* the train has not yet passed with its min safe front end the new stop location, the emergency stop message shall be accepted, however this
location shall be used by the onboard to define the new EoA and SvL only if not beyond the current EoA.
the clarification to the second point must be considered
TEST APPROACH:
The following aspects have been identified:
1) min safe front end already passed the new stop location
2) min safe front end has not already passed the new stop location
2.1) EoA shorten
2.2) SvL shorten only
2.3) no shortening
#TEST-VAL-SUB026-3111#REF# FCT 1 Conditional emergency message, min safe front has already passed new stop location
#TEST-VAL-SUB026-3112#REF# FCT 2.1 Conditional emergency message, min safe front hasn't passed new stop location
#TEST-VAL-SUB026-3720#REF# FCT 2.2 Reception of several Conditional Emergency Stop new stop location is beyond the current EoA
#TEST-VAL-SyAnfSpezCR-0060#REF# FCT 2.3 Conditional emergency stop, Stop Location behind EoA

#REQ-UNISIG-SUB026-0507#REF# 3.10.2.3
When receiving an unconditional emergency stop message the train shall be tripped immediately.
see also mode transition [20]
#TEST-VAL-SUB026-3109#REF# FCT basic function New Emergency message with the same identifier replaces the previous one (CES)
#TEST-VAL-SUB026-4818#REF# EET error expectation Outage of safe connection during RBC transition - RBC transition buffer includes unconditional/conditional emergency stop

#REQ-DESIGN-CR-0320#REF# 3.10.2.4
New movement authority received after any accepted emergency stop message and before the emergency message has been revoked, shall be rejected.
realize through exception[5] in table 4.8.3 and figure 3 (filter criteria)
realised by: #REQ-DESIGN-CR-0502#REF#

#REQ-UNISIG-SUB026-001865#REF# 3.10.2.6 #REQ-UNISIG-SUB026-3329#REF#
The driver shall be informed when emergency stop(s) have been accepted and are not yet revoked.
see System status message "Emergency stop" in ERA SRS DMI

UNISIG clarification: the text message should be displayed until the CES is revoked or deleted
#TEST-VAL-SUB026-3720#REF# FCT CES Reception of several Conditional Emergency Stop new stop location is beyond the current EoA
#TEST-VAL-SUB026-4584#REF# FCT UCES mode transition SR-TR[20]

#REQ-UNISIG-SUB026-0043#REF# 3.10.3.1
The revocation message shall refer to the identity of the concerned emergency message.
#TEST-VAL-SUB026-3114#REF# FCT CES Revocation of Conditional Emergency Stop
#TEST-VAL-SUB026-5866#REF# FCT UCES Revocation of unconditional emergency stop

#REQ-UNISIG-SUB026-0510#REF# 3.10.3.3
The revocation of an emergency message shall have no effect on the management of other emergency messages possibly received.
#TEST-VAL-SUB026-3114#REF# FCT CES Revocation of Conditional Emergency Stop
#TEST-VAL-SUB026-5866#REF# FCT UCES Revocation of unconditional emergency stop

Chapter 3.11

#REQ-DESIGN-CR-0612#REF# 3.11.3.1.3
It shall be possible for every element (distance between two discontinuities) of a static speed profile to define, if a transition to a higher
speed limit than the speed limit specified for this element is permitted before the complete train has left the element.
#TEST-VAL-SUB026-3116#REF# FCT basic function Effect of Q_FRONT (P27, P51, P65)

#REQ-UNISIG-SUB026-001936#REF# 3.11.3.2.3
For each part of the Static Speed Profile, the ERTMS/ETCS on-board equipment shall select the SSP best suiting its “Cant Deficiency” train
category, according to the following order of preference:
a)	if available, the “Cant Deficiency” SSP matching its “Cant Deficiency” train category, OR
b)	if available, the “Cant Deficiency” SSP with the highest Cant Deficiency value below the value of its “Cant Deficiency” train category,
OR
c)	the Basic SSP
#TEST-VAL-SUB026-5875#REF# FCT basic function Selection of SSP best suiting the 'Cant Deficiency' train category

#REQ-UNISIG-SUB026-0522:01#REF# 3.11.3.2.5
“Other Specific” SSP categories not relevant to the current train shall be ignored.
UNISIG clarification:
the obu does not have to store the profiles, which are not relevant for the current train category.

If the train categroy is changed, the profiles from the train front end are deleted.
#TEST-VAL-SUB026-5872#REF# FCT basic function Variable test Q_DIFF

#REQ-UNISIG-SUB026-0523:02#REF# 3.11.3.2.6
For each part of the Static Speed Profile, the ERTMS/ETCS on-board equipment in a train belonging to at least one or more “other international”
train categories shall use the most restrictive speed amongst:
a)	the ” Cant Deficiency” SSP as selected in 3.11.3.2.3, only if none of the “other specific” SSP categories matching the train categories
replaces the ” Cant Deficiency” SSP, AND
b)	all the “other specific” SSP categories matching the “other international” train categories.
TEST APPROACH:
NC_DIFF defines three other specific SSP categories 
Freight train braked in ' P' 
Freight train braked in ' G' 
Passenger train 
A given train can only fit to one of these categories.
#TEST-VAL-SUB026-5871#REF# FCT basic function Selection of the most restrictive SSP
#TEST-VAL-SUB026-5872#REF# EET error expectation Variable test Q_DIFF

#REQ-UNISIG-SUB026-001955#REF# 3.11.3.3.2
A train shall always belong to one and only one “Cant Deficiency” train category and may optionally belong to one or more “other international”
train categories.

--- FINALISED ---
Currently is only one “other international” train category possible - see definition of possibility NC_TRAIN values and Driver Selection by
Train Data Input.
#ANALYSE-VALUNISIG-5276#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-0049#REF# 3.11.4.1
It shall be possible to define an Axle load Speed Profile as a non-continuous profile.
#TEST-VAL-SUB026-3118#REF# FCT basic function Axle load SPs

#REQ-UNISIG-SUB026-0527:01#REF# 3.11.4.3
The ERTMS/ETCS on-board equipment shall consider the most restrictive speed restriction that is associated with any axle load category lower
than, or equal to that of the train.
#TEST-VAL-SUB026-3B07#REF# ECT basic function Considering axle load speed restrictions based on train axle load
#TEST-VAL-SUB026-3118#REF# EET error expectation Axle load SPs

#REQ-UNISIG-SUB026-0528#REF# 3.11.4.4
For trains with an axle load category lower than the minimum axle load category given in the profile, the ERTMS/ETCS on-board equipment shall
not consider any speed restriction due to axle load.
#TEST-VAL-SUB026-3B07#REF# ECT basic function Considering axle load speed restrictions based on train axle load
#TEST-VAL-SUB026-3118#REF# EET error expectation Axle load SPs

#REQ-UNISIG-SUB026-0529#REF# 3.11.4.5
The initial state for Axle load Speed Profile shall be “no restriction due to axle load”.
#TEST-VAL-SUB026-3B06#REF# FCT basic function New ASP replaces existing ASP taking D_AXLELOAD/D_TRACKINIT into account

#REQ-DESIGN-CR-0613#REF# 3.11.4.6
Whether a speed increase after the axle load speed restriction shall be delayed with train length, shall be determined by the axle load speed
profile information sent to the on-board equipment.
#TEST-VAL-SUB026-5224#REF# FCT basic function Effect of Q_FRONT (P51)

#REQ-UNISIG-SUB026-0050#REF# 3.11.5.2 #REQ-UNISIG-SUB026-0534#REF#
All Temporary Speed Restrictions shall be independent of each other. This means that an individual Temporary Speed Restriction shall not affect,
nor be affected by, any other individual Temporary Speed Restriction.
#TEST-VAL-SUB026-3119#REF# FCT basic function TSRs

#REQ-UNISIG-SUB026-000796#REF# 3.11.5.3
Whether a speed increase after the temporary speed restriction shall be delayed with train length, shall be determined by the temporary speed
restriction information sent to the on-board equipment.
#TEST-VAL-SUB026-5225#REF# FCT basic function Effect of Q_FRONT (P65)

#REQ-UNISIG-SUB026-0531#REF# 3.11.5.4
When two or more temporary speed restrictions overlap, the most restrictive speed of the overlapping temporary speed restrictions shall be used
in the area of overlap.
#TEST-VAL-SUB026-3119#REF# FCT basic function TSRs

#REQ-UNISIG-SUB026-0532#REF# 3.11.5.5 #REQ-UNISIG-SUB026-0535#REF#
Each Temporary Speed Restriction shall have an identity to make it possible to revoke the Temporary Speed Restriction using its identity. The
speed restriction shall be revoked immediately when revocation is received from trackside, without delay for the train length.
TEST APPROACH:
The following aspects have been identified:
1) handling of several revocable TSRs
2) handling of the train length delay
#TEST-VAL-SUB026-3119#REF# FCT 1 TSRs
#TEST-VAL-SUB026-5867#REF# FCT 2 TSR revocation not delayed by train length

#REQ-UNISIG-SUB026-0533#REF# 3.11.5.6
It shall be possible to identify whether a Temporary Speed Restriction is possible to revoke or not.
NID_TSR=255 means NOT revocable
#TEST-VAL-SUB026-3120#REF# FCT Non-revocable Non-revocable TSR
#TEST-VAL-SUB026-3119#REF# FCT revocable TSRs

#REQ-UNISIG-SUB026-0534#REF# 3.11.5.7
A new Temporary Speed Restriction shall not replace a previously received Temporary Speed Restriction with another identity.
is realized through 3.11.5.2
realised by: #REQ-UNISIG-SUB026-0050#REF#

#REQ-UNISIG-SUB026-0535#REF# 3.11.5.8
Temporary Speed Restrictions shall only be revoked on request from the trackside.
3.11.5.5 is sufficient, because OBU don't get any requirement for revoking a TSR (exception is the mode dependency)
realised by: #REQ-UNISIG-SUB026-0532#REF#

#REQ-UNISIG-SUB026-0536#REF# 3.11.5.9
If the on-board equipment receives a new Temporary Speed Restriction (TSR) with the same identity as an already received TSR, the new Temporary
Speed Restriction shall replace the previous one, except when the Temporary Speed Restriction is identified as non revocable in which case this
shall be considered as an additional TSR.
#TEST-VAL-SUB026-3121#REF# FCT basic function TSRs mit der selben ID
#TEST-VAL-SUB026-3322#REF# EET error expectation TSR ueberschreiben bei Infill
#TEST-VAL-SUB026-3471#REF# EET error expectation RBC sends several non-revocable speed restriction in one message
#TEST-VAL-SUB026-3472#REF# EET error expectation RBC sends several revocable speed restriction with same id in one message

#REQ-UNISIG-SUB026-002001#REF# 3.11.5.13
When ERTMS/ETCS on-board equipment has accepted an order to reject revocable TSRs from balises, this inhibition shall be stored and shall be
effective immediately, but only for revocable TSRs received from balises thereafter.
#TEST-VAL-SUB026-5817#REF# FCT basic function TSR acceptence after receiving Inhibition of revocable TSRs from balises in L2/3

#REQ-UNISIG-SUB026-002002#REF# 3.11.5.14
The inhibition of revocable TSRs from balises shall be deleted if any of the following occurs:
  the communication session established with the RBC that ordered the inhibition is terminated, OR
  in case of RBC/RBC handover, the train front end crosses the RBC/RBC border.
realised by: #REQ-UNISIG-SUB026-002003#REF#

#REQ-UNISIG-SUB026-002003#REF# to.3.11.5.14 #REQ-UNISIG-SUB026-002002#REF#
The inhibition of revocable TSRs from balises shall be deleted if any of the following occurs:
  the communication session established with the RBC that ordered the inhibition is terminated, OR
  in case of RBC/RBC handover, the train front end crosses the RBC/RBC border.

clarification: Second point is valid for TSR inhibitions ordered by the handing over RBC only.
UNISIG clarification: the second point is only relevant for a TSR inhibition from HO RBC
#TEST-VAL-SUB026-5820#REF# FCT RBC/RBC handover Inhibition of revocable TSRs from balises in L2/3 and RBC/RBC handover
#TEST-VAL-SUB026-5818#REF# FCT session state (basic function) Inhibition of revocable TSRs from balises in L2/3 deleted due to session termination
#TEST-VAL-SUB026-5819#REF# FCT session state (special cases) Inhibition of revocable TSRs from balises in L2/3 and outage of safe connection

#REQ-UNISIG-SUB026-0539#REF# 3.11.6.2
This speed value shall be taken into account by the on-board equipment as soon as it is received on-board, with the exception of a signalling
related speed restriction from an infill device. In case of infill information the speed restriction shall be taken into account from the
location reference of the balise group at the next main signal.
#TEST-VAL-SUB026-3124#REF# FCT basic function v_main: nornal and in-fill
#TEST-VAL-SUB026-7043#REF# EET error expectation First Signalling related speed restriction received as infill

#REQ-DESIGN-CR-0531#REF# 3.11.6.3
The speed restriction shall be valid until a new signalling related speed restriction is received.
#TEST-VAL-SUB026-3125#REF# FCT basic function New V_MAIN overrides old one

#REQ-DESIGN-CR-0532#REF# 3.11.6.3.1
If the ERTMS/ETCS on-board equipment switches from level 1 to level 2/3, the signalling related speed restriction shall remain valid until a
L2/3 MA is accepted by the ERTMS/ETCS on-board equipment
#TEST-VAL-SUB026-4079#REF# FCT basic function V_MAIN, position report parameters, movement authority request parameters when entering L2

#REQ-UNISIG-SUB026-002019#REF# 3.11.6.4
In case of a signal at danger the signalling related speed restriction shall have value zero, which shall be evaluated by the ERTMS/ETCS
on-board equipment not as a speed limit but as a train trip order.
TEST APPROACH:
The following aspects have been identified:
1) basic function
2) buffered MA with V_MAIN=0
3) handling of MA with V_MAIN=0 when override is active
3.1) LTO+MA+MP
3.2) MA+MP
3.3) MA only
#TEST-VAL-SUB026-4110#REF# FCT 1 Mode transition from FS to TR due to trip order
#TEST-VAL-SUB026-5956#REF# ECT 2 Buffered MA with V_MAIN=0
#TEST-VAL-SUB026-4E20#REF# FCT 3.1 Override active, pass BG with LTO L1 NOW, MA V_MAIN=0, MP OS D_MAMODE=0 while in UN/L0
#TEST-VAL-SUB026-4E18#REF# FCT 3.2 LS Override active, pass BG with MA with V_MAIN=0 (trip order) plus MP LS with D_MAMODE=0
#TEST-VAL-SUB026-4E17#REF# FCT 3.2 OS Override active, pass BG with MA with V_MAIN=0 (trip order) plus MP OS with D_MAMODE=0
#TEST-VAL-SUB026-4E19#REF# FCT 3.2 SH Override active, pass BG with MA with V_MAIN=0 (trip order) plus MP SH with D_MAMODE=0
#TEST-VAL-SUB026-4E16#REF# FCT 3.3 Override active, pass BG with MA with V_MAIN=0 (trip order)
#TEST-VAL-SUB026-4580#REF# EET error expectation passage of BG with P12 V_MAIN=0 and MP-LS (GP does not covers MA) while override active
#TEST-VAL-SUB026-4581#REF# EET error expectation passage of BG with P12 V_MAIN=0 and MP-OS (SSP does not covers MA) while override active

#REQ-UNISIG-SUB026-0542#REF# 3.11.6.5
In case of infill information the signalling related speed restriction at zero shall be ignored.
#TEST-VAL-SUB026-3126#REF# FCT basic function Infill Trip Order from loop

#REQ-UNISIG-SUB026-0052:01#REF# 3.11.7.1 #REQ-UNISIG-SUB026-1039:01#REF#
The value of the mode related speed restriction shall be determined by the corresponding national value or the corresponding default values if
the national values are not applicable.
#TEST-VAL-SUB026-3466#REF# EET CFX00037712 set/reset of NV (V_NVONSIGHT) D_VALIDNV=0
#TEST-VAL-SUB026-3467#REF# EET CFX00037712 set/reset of NV (V_NVONSIGHT) D_VALIDNV/=0
#TEST-VAL-SUB026-5868#REF# FCT LS Variable test V_NVLIMSUPERV
#TEST-VAL-SUB026-3226#REF# FCT OS Variablentest V_NVONSIGHT
#TEST-VAL-SUB026-3224#REF# FCT SH Variablentest V_NVSHUNT
#TEST-VAL-SUB026-3225#REF# FCT SR Variablentest V_NVSTFF
#TEST-VAL-SUB026-3227#REF# FCT UN Variablentest V_NVUNFIT
#TEST-VAL-SUB026-4A22#REF# EET error expectation Determine Most Restrictive Speed Profile, based on Mode OS

#REQ-UNISIG-SUB026-3105#REF# 3.11.7.1.1 #REQ-UNISIG-SUB026-1039:01#REF#
Exception 1: For the modes On-sight, Limited Supervision and Shunting the speed limit can also be given from the trackside. The speed limit
given from the trackside shall prevail over the National value and the default value.
TEST APPROACH:
The following aspects were identified:
1) V_MAMODE > V_NV
2) V_MAMODE < V_NV
Each aspect is verified for all three modes in question (OS, LS, SH)
#TEST-VAL-SUB026-3750#REF# FCT 1 LS Limited Supervision mode speed limit V_MAMODE< V_NVLIMSUPERV
#TEST-VAL-SUB026-3751#REF# FCT 1 OS OS mode speed limit V_MAMODE< V_NVONSIGHT
#TEST-VAL-SUB026-5869#REF# FCT 1 SH Changing NV does not influence mode related speed restriction given from track side
#TEST-VAL-SUB026-3752#REF# FCT 2 LS, 2 OS V_MAMODE> V_NVONSIGHT/V_NVLIMSUPERV
#TEST-VAL-SUB026-4241#REF# FCT 2 SH transition FS/L2 - SN/STM - SH/L2

#REQ-UNISIG-SUB026-3106#REF# 3.11.7.1.2
Exception 2: For the mode Reversing there is no National/Default value. The speed limit is always given from trackside.
is realized through 4.4.18.1.3 a)
realised by: #REQ-UNISIG-SUB026-3095#REF#

#REQ-UNISIG-SUB026-002033#REF# 3.11.7.1.3
Exception 3: For the mode Staff Responsible the speed limit can also be entered by the driver. The speed limit given by the driver shall prevail
over the National/Default value.
is realized through 4.4.11.1.6.3
realised by: #REQ-DESIGN-CR-0333#REF#

#REQ-UNISIG-SUB026-0053#REF# 3.11.8.1
It shall be possible to define the maximum train speed related to the actual performance and configuration of the train.
realised by: #REQ-UNISIG-SUB026-007294#REF#
realised by: #REQ-UNISIG-SUB026-0122:02#REF#

#REQ-UNISIG-SUB026-007294#REF# to.3.11.8.1 #REQ-UNISIG-SUB026-0053#REF#
For the supervision of the train related speed restriction the train data value "maximum train speed" shall be used.
#TEST-VAL-SUB026-4A24#REF# FCT basic function Determine Most Restrictive Speed Profile, based on Train related SR at Mode FS

#REQ-UNISIG-SUB026-3104#REF# 3.11.10.1 #REQ-UNISIG-SUB026-3103#REF#
While the “override” function is active, the override speed limit (national /default value) shall be taken into account.
TEST APPROACH:
The following aspects have been identified:
1) modes where Override function is active
1.1) SH
1.2) SR
1.3) UN
2) source of Override speed limit 
2.1) national value
2.2) default value
#TEST-VAL-SUB026-5962#REF# FCT 1.1 Speed supervision based on V_NVSHUNT and V_NVSUPOVTRP
#TEST-VAL-SUB026-5961#REF# FCT 1.2 Speed supervision based on V_TSR, V_NVSTFF and V_NVSUPOVTRP
#TEST-VAL-SUB026-5963#REF# FCT 1.3, 2.1, 2.2 Speed supervision based on V_TSR, V_NVUNFIT and V_NVSUPOVTRP

#REQ-UNISIG-SUB026-002051#REF# 3.11.11.2
The order shall be given by means of a non-continuous profile defining:
  The start and end location for the speed restriction
  The permitted braking distance used to calculate the speed restriction value
  Whether the permitted braking distance is to be achieved with the Service Brake or Emergency Brake
  A single gradient value applicable for the calculation
TEST APPROACH:
The verification focuses on the start and end location of the profile. The verification of all P52 parameter takes place via parameter
verification SUBSET026 7.5
#TEST-VAL-SUB026-3A64#REF# FCT basic function Speed and distance monitoring based on PBD Information given as non-continuous profile data

#REQ-UNISIG-SUB026-002057#REF# 3.11.11.3
The speed restriction shall be calculated when ERTMS/ETCS on-board receives the permitted braking distance information from trackside, and shall
be re-calculated only if the brake characteristics of the train taken into account for the calculation of the speed restriction changes.
realised by: #REQ-UNISIG-SUB026-010526#REF#

#REQ-UNISIG-SUB026-010526#REF# 3.11.11.3 #REQ-UNISIG-SUB026-002057#REF#
#ANA-UNISIG-PBD-0001#REF#
The speed restriction shall be calculated when ERTMS/ETCS on-board receives the permitted braking distance information from trackside, and shall
be re-calculated only if any of the following inputs that affects the calculation of the related EBI or FLOI supervision limit changes:
∙	The Train Data referred to in section 3.13.2.2.1
∙	The Status of the special brakes, see 3.13.2.2.6.2
∙	The National Values referred to in 3.13.2.3.7.

clarification:
If also an announced Set of National Values is available or received, the permitted brake distance shall be calculated/ recalculated with both
sets (current/ announced)and the most restricted speed restriction shall be used.
UNISIG clarification: solution UCR 1149 is taken over

The clarification is necessary, when 2 NV-Sets (current, announced or a new announced is received) are available
TEST APPROACH:
Following test aspects have been identified:
1) initial reception of permitted braking distance information from trackside
2) recalculation due to train data change
3) recalculation due to special brake status change - 
4) recalculation due to change of national Values
5) no recalculation due to other change 


The feature special brake dependent braking curve calculation is not part of R8 the verification of the aspect 3) is hence omitted
#TEST-VAL-SUB026-3A64#REF# FCT 1 Speed and distance monitoring based on PBD Information given as non-continuous profile data
#TEST-VAL-SUB026-4B93#REF# FCT 2 dependency of PBDSR on TD change (train length, brake model)
#TEST-VAL-SUB026-4B92#REF# FCT 4 dependency of PBDSR on Q_NVINHSMICPERM
#TEST-VAL-SUB026-4B94#REF# FCT 5 dependency of PBDSR on AP

#REQ-UNISIG-SUB026-002059#REF# 3.11.11.4 #REQ-UNISIG-SUB026-008090#REF#
#REQ-UNISIG-SUB026-010109#REF#
The calculation of the speed restriction by the on-board shall be executed as follows:
  The gradient value received from trackside shall be applied for EBD and/or SBD calculation.
  For the calculation of the EBI limit: the estimated acceleration shall be set to “zero”, the compensation of the speed measurement inaccuracy,
if not inhibited, shall be set to a Fixed Value (see Appendix A.3.1).
  If the permitted braking distance is to be achieved with the emergency brake, the EBI limit shall be calculated like the EBI limit for an SvL
in a target speed supervision towards an EOA.
  If the permitted braking distance is to be achieved with the service brake, the FLOI limit shall be calculated like the FLOI limit of the
target speed supervision for a combined EOA/SvL location.
realised by: #REQ-UNISIG-SUB026-010527#REF#

#REQ-UNISIG-SUB026-010527#REF# 3.11.11.4 #REQ-UNISIG-SUB026-002059#REF#
#ANA-UNISIG-PBD-0001#REF#
The calculation of the speed restriction by the on-board shall be executed as follows:
  The gradient value received from trackside shall be applied for EBD and/or SBD calculation.
  For the calculation of the EBI supervision limit: the estimated acceleration shall be set to “zero”, the compensation of the speed measurement
inaccuracy, if not inhibited, shall be set to a Fixed Value (see Appendix A3.1).
  If the permitted braking distance is to be achieved with the emergency brake, the EBI supervision limit shall be calculated like the EBI
supervision limit for an SvL in a target speed supervision towards an EOA.
  If the permitted braking distance is to be achieved with the service brake, the FLOI supervision limit shall be calculated like the FLOI
supervision limit of the target speed supervision for a combined EOA/SvL location.
The result of the calculation is a speed for which the EBI or FLOI supervision limit is located at the permitted braking distance in rear of the
stop location.
UNISIG clarification: solution UCR 1149 is taken over
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input information for the calculation.
The following aspects have been identified:
1) dependency on D_PBD
2) dependency on G_PBDSR
3) dependency on Q_GDIR
4) dependency on Q_PBDSR
#ANALYSE-VALUNISIG-4784#REF# FCT The calculation of the speed restriction is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4B95#REF# FCT 1 test variable D_PBD
#TEST-VAL-SUB026-4B97#REF# FCT 2 test variable G_PBDSR
#TEST-VAL-SUB026-3A66#REF# FCT 3 Q_GDIR in Packet 52 (PBD Information)
#TEST-VAL-SUB026-4B99#REF# FCT 4 test variable Q_PBDSR
#TEST-VAL-SUB026-7073#REF# EET error expectation Evaluation of high G_PBDSR downhill

#REQ-UNISIG-SUB026-002066#REF# 3.11.11.5
The derived EBI, or FLOI, target speed supervision value shall be used as the SB ceiling speed intervention limit for the speed restriction.
realised by: #REQ-UNISIG-SUB026-010528#REF#

#REQ-UNISIG-SUB026-010528#REF# 3.11.11.5 #REQ-UNISIG-SUB026-002066#REF#
#ANA-UNISIG-PBD-0001#REF#
The speed value derived from the EBI or FLOI supervision limit shall be used as the SB ceiling speed intervention limit for the speed
restriction.
UNISIG clarification: solution UCR 1149 is taken over
#TEST-VAL-SUB026-3A64#REF# FCT basic function Speed and distance monitoring based on PBD Information given as non-continuous profile data

#REQ-UNISIG-SUB026-002068#REF# 3.11.11.6
From the SB ceiling speed intervention limit according to the previous clause, the Permitted Speed limit inside the speed restriction shall be
calculated by:
  Subtracting the applicable speed interval between Permitted Speed limit and SB intervention (see 3.13.9.2.5). The speed interval shall be
approximated by using the SB ceiling speed intervention limit instead of the MRSP speed limit in the formula.
  Rounding the result down to the next lower multiple of 5km/h.
#ANALYSE-VALUNISIG-4783#REF# FCT The calculation of the speed restriction is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-002072#REF# 3.11.11.7
The initial state for Speed Restrictions to Ensure Permitted Braking Distance shall be “no speed restriction”.
#TEST-VAL-SUB026-3A63#REF# FCT basic function initial state for Speed Restrictions to Ensure Permitted Braking Distance

#REQ-UNISIG-SUB026-3645:01#REF# 3.11.12.5
It shall be possible via balise groups to send to the on-board equipment a default gradient for TSR supervision, to be used for the parts of the
track not covered by the gradient profile.
realizes through Packet 141 and 3.13.4.1.3
realised by: #REQ-UNISIG-SUB026-007123#REF#
realised by: #REQ-UNISIG-SUB026-0360#REF#

#REQ-UNISIG-SUB026-3647#REF# 3.11.12.6
The Default Gradient for TSR stored on-board shall be valid until a new Default Gradient for TSR is received.
#TEST-VAL-SUB026-3748#REF# FCT basic function default gradient for TSR handling SR/FS/L2

Chapter 3.12

#REQ-UNISIG-SUB026-3134:02#REF# to.3.12.1.1 #ANA-UNISIG-TrackCondition-0001:02#REF#
A received track condition excluding big metal masses shall be ignored, if the train has passed
- the last indication point of the track condition area (see Subset 026, chapter 5.18), if available
AND
- the end point of train output, if available.

If only one of the two conditions is not yet reached, the track condition shall be evaluated only for this output.

A basic diagnostic event shall be created, if at least one of the conditions is occured.

Exception:
The train output of the track conditions "Change of Traction System" and "Change of Allowed Current Consumption" shall be
executed also, when the train received the track condition beyond the location of change/begin of the track condition.
TEST APPROACH:
The following aspects have been identified:
1) Track conditions with DMI indication, and no TIU output
1.1) TC Tunnel stopping area
1.2) TC Non stopping area
1.3) TC Sound horn
1.4) TC Radio hole
2) Track conditions with both TIU and DMI output
2.1) Last point for DMI indication was passed, end point for TIU output has not been passed
2.1.1) TC Lower pantograph
2.1.2) TC Switch off main power switch
2.1.3) TC Air tightness
2.1.4) TC Regenerative brake off
2.1.5) TC Magnetic shoe brake off
2.1.6) TC Eddy current brake SB off
2.1.7) TC Eddy current brake EB off
2.1.8) TC Change of traction system
2.2) End point for TIU outputs was passed, last point for DMI indication has not been passed
2.2.1) TC Lower pantograph
2.2.2) TC Switch off main power switch
2.2.3) TC Air tightness
2.2.4) TC Regenerative brake off
2.2.5) TC Magnetic shoe brake off
2.2.6) TC Eddy current brake SB off
2.2.7) TC Eddy current brake EB off
Note 1: For TC Change of traction system no end point for TIU output is defined (see exception for this requirement and
#REQ-UNISIG-SUB026-3707:02#, #REQ-UNISIG-SUB026-3742:01# ).So, no aspect for 2.2. is defined
Note 2: TC Station Platforms is omitted, as is not part of R8.0
Note 3: TC Change of allowed power consumption is omitted, as not start or end point is defined for this track condition; the appropriate info
is sent immediately to train interface once is received (#REQ-UNISIG-SUB026-002147#).
#TEST-VAL-SUB026-7745#REF# FCT 1.1 Indication of TC 'Tunnel Stopping Area'
#TEST-VAL-SUB026-7746#REF# FCT 1.2 Indication of TC 'Non Stopping Area'
#TEST-VAL-SUB026-7902#REF# FCT 1.3 evaluation of TC Sound Horn, when end point for DMI output has been passed
#TEST-VAL-SUB026-7903#REF# FCT 1.4 evaluation of TC Radio hole, when end point for DMI output has been passed
#TEST-VAL-SUB026-7781#REF# FCT 2.1.1, 2.1.2 evaluation of TC Lower pantograph, Main power switch, when end point for DMI output has been passed and end point for TIU output has not been passed
#TEST-VAL-SUB026-7782#REF# FCT 2.1.3 evaluation of TC Air tightness, when end point for DMI output has been passed and end point for TIU output has not been passed
#TEST-VAL-SUB026-7783#REF# FCT 2.1.4, 2.1.5, 2.1.6 evaluation of TCs Switch off brakes, when end point for DMI output has been passed and end point for TIU output has not been passed
#TEST-VAL-SUB026-7904#REF# FCT 2.1.7 evaluation of TC Eddy current brake EB, when end point for DMI output has been passed and end point for TIU output has not been passed
#TEST-VAL-SUB026-7905#REF# FCT 2.1.8 evaluation of TC Change of Traction Power, when end point for DMI output has been passed
#TEST-VAL-SUB026-7906#REF# FCT 2.2.1, 2.2.2 evaluation of TC Lower pantograph, Main power switch, when end point for TIU output has been passed and end point for DMI output has not been passed
#TEST-VAL-SUB026-7907#REF# FCT 2.2.3 evaluation of TC Air tightness, when end point for TIU output has been passed and end point for DMI output has not been passed
#TEST-VAL-SUB026-7908#REF# FCT 2.2.4, 2.2.5, 2.2.6 evaluation of TCs Switch off brakes, when end point for TIU output has been passed and end point for DMI output has not been passed
#TEST-VAL-SUB026-7909#REF# FCT 2.2.7 evaluation of TC Eddy current brake EB, when end point for TIU output has been passed and end point for DMI output has not been passed

#REQ-DESIGN-CR-0124#REF# 3.12.1.2.1
The starting point of a profile type track condition shall be evaluated taking into account the max safe front end of the train, the end of the
profile taking into account the min safe rear end of the train. Location type data shall be evaluated taking into account the max safe front of
the train.
the begin and end conditions for the indication on icons is defined in chapter 5.18
--- FINALISED ---
The begin and the end conditions for the indication on icons are defined in chapter 5.18.
realised by: #REQ-UNISIG-SUB026-010308#REF#
realised by: #REQ-UNISIG-SUB026-3708:01#REF#
realised by: #REQ-UNISIG-SUB026-3743:01#REF#
realised by: #REQ-UNISIG-SUB026-007779:01#REF#

#REQ-DESIGN-CR-0505#REF# 3.12.1.2.1.2
Exception 1: The starting point of a Big Metal Mass type track condition shall be evaluated taking into account the max safe antenna position,
the end of the profile taking into account the min safe antenna position.
realised by: #REQ-UNISIG-SUB026-3274#REF#
realised by: #REQ-UNISIG-SUB026-3275#REF#

#REQ-UNISIG-SUB026-002106#REF# 3.12.1.2.1.3
Exception 2: The end of the Powerless section shall be evaluated taking into account the min safe front end of the train.
is realized with chapter 5.18 for the indication and the defined default values (see ANA-UNISIG-TrackCondition-0012) for the TI Output
--- FINALISED ---
The begin and the end conditions for the indication on icons are defined in chapter 5.18.
realised by: #REQ-UNISIG-SUB026-3708:01#REF#
realised by: #REQ-UNISIG-SUB026-007779:01#REF#

#REQ-UNISIG-SUB026-002108#REF# 3.12.1.2.1.4
Exception 3: The start and end of a tunnel stopping area and of a sound horn track condition shall be evaluated taking into account the
estimated front end of the train.
is realized with chapter 5.18 for the indication
--- FINALISED ---
The begin and the end conditions for the indication on icons are defined in chapter 5.18.
#ANALYSE-VALUNISIG-5350#REF# FCT No additional functional requirement refer column FINALISED.
realised by: #REQ-UNISIG-SUB026-007779:01#REF#

#REQ-UNISIG-SUB026-010308#REF# to.3.12.1.2.1 #REQ-DESIGN-CR-0124#REF#
#ANA-UNISIG-TrackCondition-0018:01#REF#
Exception 3.12.1.2.1:
For the supervision of safe radio connection and the session establishment in dependency of a radio hole the start and end of the track
condition radio hole shall be evaluated taking into account the estimated front end of the train.
#TEST-VAL-SUB026-5979#REF# FCT safe radio connection Supervision of safe radio connection depending start and end of the track condition radio hole
#TEST-VAL-SUB026-5980#REF# FCT session establishment , CFX00035657 Session establishment dependending on track condition radio hole

#REQ-DESIGN-CR-0747#REF# to.3.12.1.2.1
In case the trackside commands a track condition with length zero, the onboard shall supervise the shortest length (greater zero) it can
internally handle, instead of zero length.
UNISIG clarification: a TC with length 0 have to be taken into account also
#TEST-VAL-SUB026-3437#REF# ECT basic function Trackcondition with L_TRACKCOND=0 (pkt 67/68)

#REQ-DESIGN-CR-0509:01#REF# 3.12.1.3
The types of track conditions to be covered by this function are:
  Powerless section, lower pantograph (initial state: no powerless section, i.e. pantograph not to be lowered)
  Powerless section, switch off main power switch (initial state: no powerless section, i.e. main power switch not to be switched off)
  Air tightness (initial state: no request for air tightness)
  Sound horn (initial state: no request for sound horn)
  Non stopping area (initial state: stopping permitted)
  Tunnel stopping area (initial state: no tunnel stopping area)
  Change of traction system, switch traction system on-board, used for train capable of handling several traction systems (initial state: no
initial state - keep the current setting)
  Change of allowed current consumption, limit current consumed by the train, used to adapt the maximum current consumption of the train to the
maximum current allowed by the trackside (initial state: no initial state - keep the current setting)
  Big metal masses, ignore onboard integrity check alarms of balise transmission. (initial state: alarms not ignored)
  Radio hole, stop supervision of the loss of safe radio connection (initial state: loss of safe radio connection supervised)
  Switch off regenerative brake (initial state: regenerative brake on)
  Switch off eddy current brake for service brake (initial state: eddy current brake on for service brake)
  Switch off eddy current brake for emergency brake (initial state: eddy current brake on for emergency brake)
  Switch off magnetic shoe brake (initial state: magnetic shoe brake on).
  Station platforms, enable passenger doors with or without steps according to platform location, side and height (initial state: not enabled).
Station Platform isn't realized
#ANALYSE-VALUNISIG-5332#REF# FCT No additional functional requirement. The requirement lists all track condition indicated from the trackside. The information about the initial state of the track condition is used throughout test of track conditions requirements.

#REQ-DESIGN-CR-0510:01#REF# 3.12.1.5 #ANA-UNISIG-TrackCondition-0014:01#REF#
The following actions shall be performed at receiving a track condition:
a)	Indicate on DMI (see chapter 5, procedure “Indication of track conditions”), except “Station platforms”, “Change of allowed current
consumption” and “Big metal masses”.
b)	Send information with the remaining distance to an ERTMS/ETCS external function, with the exception of big metal mass track condition,
sound horn track condition, non stopping area, tunnel stopping area and supervision of radio transmission which are handled inside the
ERTMS/ETCS on-board equipment.
UNISIG clarification:
The output to Train Interface is realized via digital signals (inside the track condition or not) differing to to point b. The remaining
distance is not sended (expected TC "Change of Allowed Current Consumption")
--- FINALISED ---
The part a is realized through the definitions in Chapter 5.18.
realised by: #REQ-UNISIG-SUB026-3707:02#REF#
realised by: #REQ-UNISIG-SUB026-3711:01#REF#
realised by: #REQ-UNISIG-SUB026-3712:02#REF#

#REQ-UNISIG-SUB026-3707:02#REF# 3.12.1.5.b #REQ-DESIGN-CR-0510:01#REF#
#ANA-UNISIG-TrackCondition-0012:01#REF#
Output to Train:
Parameterizable values for evaluation the start- and end conditions shall be provided for the following track conditions:
• Powerless section, lower pantograph
• Powerless section, switch off main power switch
• Air tightness
• Switch off regenerative brake
• Switch off eddy current brake for SB
• Switch off eddy current brake for EB
• Switch off magnetic shoe brake
• Change of traction system

remark: For "Change of traction system" the start conditions are relevant only. Therefore the value of variable train length shall be
never been taken into account.
correspond with  mTCConfigObject in FzgKonfDat
TEST APPROACH:
Following aspects have been identified:
1) TC Lower pantograph
2) TC Switch off main power switch
3) TC Air tightness
4) TC Regenerative brake off
5) TC Magnetic shoe brake off
6) TC Eddy current brake SB off
7) TC Eddy current brake EB off
8) TC Change of traction system
#TEST-VAL-SUB026-7915#REF# FCT 1, 2 evaluation of TC Lower pantograph, Main power switch: changed TIU configuration
#TEST-VAL-SUB026-7916#REF# FCT 3 evaluation of TC Air tightness: changed TIU configuration
#TEST-VAL-SUB026-7917#REF# FCT 4, 5, 6 evaluation of TC Regenerative brake, Magnetic shoe brake, Eddy current brake SB: changed TIU configuration
#TEST-VAL-SUB026-7918#REF# FCT 7 evaluation of TC Eddy current brake EB: changed TIU configuration
#TEST-VAL-SUB026-7901#REF# FCT 8 evaluation of TC Chamge of Traction

#REQ-UNISIG-SUB026-3708:01#REF# to.3.12.1.5 #REQ-DESIGN-CR-0124#REF#
#REQ-UNISIG-SUB026-002106#REF#
#ANA-UNISIG-TrackCondition-0011:01#REF#
#ANA-UNISIG-TrackCondition-0012:01#REF#
Output to Train:
The variables, which are defined in #DSC-TBL-TrackCond-0001:01#REF#, shall be used as parameterizable values for the Track Conditions.
The default values for these variables are defined in #DSC-TBL-TrackCond-0002:01#REF#.
hint to parametrization PositionOffsetOFF:
PositionOffsetON <= PositionOffsetOFF + Train length (if used for supervision the end of the track condition).
This is necessary so that the begin of the track condition + PositionOffsetON is not beyond the end of the track condition.
TEST APPROACH:
The use of the parameterizable values for the different track condition is covered by the verification of #REQ-UNISIG-SUB026-3707:01#REF#.
The min boundary of each configuration item regarding #DSC-TBL-TrackCond-0001#REF# are verified by equivalence test (sample
RegenerativeBrakeInhibit).
The max boundary of each configuration item regarding #DSC-TBL-TrackCond-0001#REF# are verified by equivalence test (sample
RegenerativeBrakeInhibit).
1) IncludeTrainLength (Max)
2) Do not IncludeTrainLength (Min)
3) position offset_on Min
4) position offset_on Max 
5) position offset_off Min
6) position offset_off Max 
7) mDelayTimeON Min
8) mDelayTimeON Max 
9) Default Value values
10) No configuration item modifies the Track Cond from Track Side

#REQ-UNISIG-SUB026-3711:01#REF# to.3.12.1.5.b #REQ-DESIGN-CR-0510:01#REF#
#ANA-UNISIG-TrackCondition-0013#REF#
Output to Train:
If a output signal to the train is parameterized for a track condition, the start and the end of this track condition shall be send to the train
as a change of the state.
TEST APPROACH:
Following aspects have been identified:
1) TC Lower pantograph
2) TC Switch off main power switch
3) TC Air tightness
4) TC Regenerative brake off
5) TC Magnetic shoe brake off
6) TC Eddy current brake SB off
7) TC Eddy current brake EB off
8) TC Change of traction system
#TEST-VAL-SUB026-7915#REF# FCT 1, 2 evaluation of TC Lower pantograph, Main power switch: changed TIU configuration
#TEST-VAL-SUB026-7916#REF# FCT 3 evaluation of TC Air tightness: changed TIU configuration
#TEST-VAL-SUB026-7917#REF# FCT 4, 5, 6 evaluation of TC Regenerative brake, Magnetic shoe brake, Eddy current brake SB: changed TIU configuration
#TEST-VAL-SUB026-7918#REF# FCT 7 evaluation of TC Eddy current brake EB: changed TIU configuration
#TEST-VAL-SUB026-7901#REF# FCT 8 evaluation of TC Chamge of Traction

#REQ-UNISIG-SUB026-3742:01#REF# to.3.12.1.5.b #ANA-UNISIG-TrackCondition-0016:03#REF#
Output to Train:
For evaluation the starting and end point the parameterized values for this track condition shall be considered.

The starting and end point shall be determined as follows:
starting point =  start of track condition + parameterized PositionOffsetON - distance (parameterized DelayTimeON, current train speed)

end point = end of track condition + parameterized PositionOffsetOFF
this evaluation is relevant for all TCs, which are defined in REQ-UNISIG-SUB026-3707, 
exception: for Change of Traction System only the evaluation of starting point
TEST APPROACH:
Following aspects have been identified:
1) TC Lower pantograph
2) TC Switch off main power switch
3) TC Air tightness
4) TC Regenerative brake off
5) TC Magnetic shoe brake off
6) TC Eddy current brake SB off
7) TC Eddy current brake EB off
8) TC Change of traction system
#TEST-VAL-SUB026-7915#REF# FCT 1, 2 evaluation of TC Lower pantograph, Main power switch: changed TIU configuration
#TEST-VAL-SUB026-7916#REF# FCT 3 evaluation of TC Air tightness: changed TIU configuration
#TEST-VAL-SUB026-7917#REF# FCT 4, 5, 6 evaluation of TC Regenerative brake, Magnetic shoe brake, Eddy current brake SB: changed TIU configuration
#TEST-VAL-SUB026-7918#REF# FCT 7 evaluation of TC Eddy current brake EB: changed TIU configuration
#TEST-VAL-SUB026-7901#REF# FCT 8 evaluation of TC Chamge of Traction

#REQ-UNISIG-SUB026-010597#REF# to.3.12.1.5.b #ANA-UNISIG-TrackCondition-0011:01#REF#
Output to Train:
If the starting point (start of track condition + parameterized PositionOffsetON) is beyond the evaluated end point including train length (if
the train length is taken account), the end point shall be shifted by PositionOffsetON and a basic diagnostic event shall be created.
UNISIG clarification: 
the case, that the begin of the track condition + PositionOffsetON can beyond the end of the track condition should be excluded.
#TEST-VAL-SUB026-7926#REF# FCT basic function Evaluated starting point of TIU output is beyond the evaluated end point of TIU output

#REQ-UNISIG-SUB026-3712:02#REF# zu.3.12.1.5.b #REQ-DESIGN-CR-0510:01#REF#
#ANA-UNISIG-TrackCondition-0014:01#REF#
Output to Train:
If the output of the track condition "Change of Traction System" on train interface is set to active, the new values for traction
system (M_VOLTAGE, NID_CTRACTION) shall be send to the train too.
The value for NID_CTRACTION is not relevant, if the variable M_TRACTION is 0.
#TEST-VAL-SUB026-7901#REF# FCT basic function evaluation of TC Chamge of Traction

#REQ-UNISIG-SUB026-3743:01#REF# to.3.12.1.5.b #REQ-DESIGN-CR-0124#REF#
#ANA-UNISIG-TrackCondition-0016:03#REF#
Output to Train:
The on board shall activate the output of a track condition on train interface when the max safe front end of the train reaches the starting
point.
The on board shall deactivate the output of a track condition on train interface when the min safe front or min safe rear end of the train
leaves the end point.

Remark: min safe front or min safe rear end depends on the parameterized value TrainLength.

Exceptions:
For the track condition "Change of Traction System" the deactivation is defined separately. The output of the track conditions
"Change of Allowed Current Consumption" and "Station Platform" are defined separately too.
TEST APPROACH:
Following aspects have been identified:
1) TC Lower pantograph
2) TC Switch off main power switch
3) TC Air tightness
4) TC Regenerative brake off
5) TC Magnetic shoe brake off
6) TC Eddy current brake SB off
7) TC Eddy current brake EB off
8) TC Change of traction system
Note: Verification for 'TC Station Platforms' and 'TC Change of allowed power consumption' is covered by #REQ-UNISIG-SUB026-002147# and
#REQ-UNISIG-SUB026-002149# .
The Verification of the deactivation of 'Change of Traction System' is covered by #REQ-UNISIG-SUB026-002145#REF#.
#TEST-VAL-SUB026-7915#REF# FCT 1, 2 evaluation of TC Lower pantograph, Main power switch: changed TIU configuration
#TEST-VAL-SUB026-7916#REF# FCT 3 evaluation of TC Air tightness: changed TIU configuration
#TEST-VAL-SUB026-7917#REF# FCT 4, 5, 6 evaluation of TC Regenerative brake, Magnetic shoe brake, Eddy current brake SB: changed TIU configuration
#TEST-VAL-SUB026-7918#REF# FCT 7 evaluation of TC Eddy current brake EB: changed TIU configuration
#TEST-VAL-SUB026-7901#REF# FCT 8 evaluation of TC Chamge of Traction

#REQ-UNISIG-SUB026-002145#REF# to.3.12.1.5.b #ANA-UNISIG-TrackCondition-0022#REF#
If an output signal on train interface for a track condition "Change of Traction System" is activated, this information including the
values for traction system shall be taken back after a parametrized time.
#TEST-VAL-SUB026-7901#REF# FCT basic function evaluation of TC Chamge of Traction

#REQ-UNISIG-SUB026-002147#REF# to.3.12.1.5.b #ANA-UNISIG-TrackCondition-0021#REF#
#ANA-UNISIG-TrackCondition-0022#REF#
#ANA-UNISIG-TrackCondition-0023#REF#
When a track condition "Change of Allowed Current Consumption" is received from trackside, the new value of consumption and the
remaining distance shall be sent immediately to the train.
The information shall be taken back after a parametrized time.
#TEST-VAL-SUB026-7731#REF# FCT basic function Acceptance of TC 'Allowed power consumption' - RBC/L2

#REQ-UNISIG-SUB026-002153#REF# to.3.12.1.5.b #ANA-UNISIG-TrackCondition-0023#REF#
The remaining distance for the track condition "Change of Allowed Current Consumption" shall be determined as distance between the
current max safe front end of the train and the location of change of allowed current consumption.
#TEST-VAL-SUB026-7762#REF# FCT basic function Variable test D_CURRENT

#REQ-UNISIG-SUB026-002154#REF# to.3.12.1.5.b
The remaining distance shall be provided in metre scale.
If the current distance greater than the maximum allowed value on the train interface, the maximum possible value
shall be used.
If the current distance negative, value 0 shall be used.
If the internal variable has a lower resolution than metre, it shall be rounded to the nearest representable value.
clarification: This requirement is needed, because the distance from track side can set in 10m or dm resolution (see Q_SCALE)
TEST APPROACH:
The value on the train interface is defined as INT16 I_CurCnsDist which means that the maximum value is 32767 (see #REQ-FFFIS_PN-OUT-1100:01#)
The following aspects have been identified:
1) Distance is greater than the maximum allowed value on the train interface
2) Distance is negative
3) Distance has a lower resolution than metre
#TEST-VAL-SUB026-7762#REF# FCT 1, 3 Variable test D_CURRENT
#TEST-VAL-SUB026-7731#REF# FCT 2 Acceptance of TC 'Allowed power consumption' - RBC/L2

#REQ-UNISIG-SUB026-002149#REF# to.3.12.1.5.b #ANA-UNISIG-TrackCondition-0021#REF#
#ANA-UNISIG-TrackCondition-0022#REF#
When a track condition "Station Platforms" is received from trackside, this information shall be send immediately to train.
The information shall be taken back after a parametrized time.
an output isn't realized

#REQ-UNISIG-SUB026-002152#REF# to.3.12.1.5.b
A time to delay the taken back of track condition information on train interface shall be parameterizable.
range of values : 0...5000 ms
resolution	: 200 ms
default value	: 1000 ms

This time is relevant for output on train interface for following track conditions:
- Change of Traction System
- Change of Allowed Current Consumption
- Station Platforms
current mvb cycle 128/256 ms to trains
TEST APPROACH:
TC 'Station Platforms' is not part of R8.0 (refer #REQ-SRS-004501#REF#), the verification for it is hence omitted.
#TEST-VAL-SUB026-7731#REF# FCT Change of Allowed Current Consumption Acceptance of TC 'Allowed power consumption' - RBC/L2
#TEST-VAL-SUB026-7901#REF# FCT Change of Traction System evaluation of TC Chamge of Traction

#REQ-UNISIG-SUB026-3644#REF# to.3.12.1.5 #ANA-UNISIG-TrackCondition-0002#REF#
Overlapping or adjacent track condition areas of the same type of track condition shall be combined to one track condition area.
#TEST-VAL-SUB026-7914#REF# FCT basic function Overlapping or adjacent TCs are combined into one TC area

#REQ-UNISIG-SUB026-0550#REF# 3.12.1.6
The train is permitted to run without any track condition information given from the trackside. The initial state shall then be used by the
on-board equipment.
TEST APPROACH:
In order to verify the initial states of TCs, the following OBU functionalities are considered: 
Initial states of TCs sound horn, non stopping areas and tunnel stopping areas are: no indication on DMI regarding these TCs
Initial state of TCs lower pantograph, main power switch, air tightness, switch off brakes, change of traction are: no DMI indications regarding
these TCs, and no TIU outputs regarding defined signals for these TCs set.
Initial state of TCs station platforms and allowed power consumption are: no TIU outputs regarding defined signals for these TCs set
Initial state of TC Radio Hole is: no DMI indication regarding Radio Hole, and loss of safe radio connection is supervised. 
Initial state of TC BMM is: integrity check alarms of balise transmission are not ignored.
The following aspects have been identified:
1) Track conditions with DMI indication only
1.1) TC Tunnel stopping area
1.2) TC Non stopping area
1.3) TC Sound horn
2) Track conditions with both TIU and DMI output
2.1) Initial state regarding DMI indication
2.1.1) TC Lower pantograph
2.1.2) TC Switch off main power switch
2.1.3) TC Air tightness
2.1.4) TC Regenerative brake off
2.1.5) TC Magnetic shoe brake off
2.1.6) TC Eddy current brake SB off
2.1.7) TC Eddy current brake EB off
2.1.8) TC Change of traction system
2.2) Initial state regarding TIU output
2.2.1) TC Lower pantograph
2.2.2) TC Switch off main power switch
2.2.3) TC Air tightness
2.2.4) TC Regenerative brake off
2.2.5) TC Magnetic shoe brake off
2.2.6) TC Eddy current brake SB off
2.2.7) TC Eddy current brake EB off
2.2.8) TC Change of traction system
3) Track Conditions with TIU output only
3.1) TC Change of allowed power consumption
4) TC Radio Hole
5) TC BMM
Verification of TC Station platforms is omitted, as this TC is not part of R8.0.
#TEST-VAL-SUB026-7745#REF# FCT 1.1 Indication of TC 'Tunnel Stopping Area'
#TEST-VAL-SUB026-7746#REF# FCT 1.2 Indication of TC 'Non Stopping Area'
#TEST-VAL-SUB026-7724#REF# FCT 1.3 Indication of TC 'Sound horn', default configuration
#TEST-VAL-SUB026-5569#REF# FCT 2.1.1 Indication of TC 'Powerless section, lower pantograph' - default UNISIG values
#TEST-VAL-SUB026-5570#REF# FCT 2.1.2 Indication of TC 'Powerless section, switch off main power switch', default configuration
#TEST-VAL-SUB026-5560#REF# FCT 2.1.3 Indication of TC 'Air tightness', default configuration
#TEST-VAL-SUB026-5563#REF# FCT 2.1.4 Indication of TC inhibition of regenerative brake, default configuration
#TEST-VAL-SUB026-5565#REF# FCT 2.1.5 Indication of TC magnetic shoe brake, default configuration
#TEST-VAL-SUB026-5564#REF# FCT 2.1.6 Indication of TC eddy current brake - SB, default configuration
#TEST-VAL-SUB026-3B89#REF# FCT 2.1.7 Indication of TC eddy current brake - EB, default configuration
#TEST-VAL-SUB026-5566#REF# FCT 2.1.8 Indication of TC change of traction system, default configuration
#TEST-VAL-SUB026-7915#REF# FCT 2.2.1, 2.2.2 evaluation of TC Lower pantograph, Main power switch: changed TIU configuration
#TEST-VAL-SUB026-7916#REF# FCT 2.2.3 evaluation of TC Air tightness: changed TIU configuration
#TEST-VAL-SUB026-7917#REF# FCT 2.2.4, 2.2.5, 2.2.6 evaluation of TC Regenerative brake, Magnetic shoe brake, Eddy current brake SB: changed TIU configuration
#TEST-VAL-SUB026-7918#REF# FCT 2.2.7 evaluation of TC Eddy current brake EB: changed TIU configuration
#TEST-VAL-SUB026-7901#REF# FCT 2.2.8 evaluation of TC Chamge of Traction
#TEST-VAL-SUB026-7731#REF# FCT 3.1 Acceptance of TC 'Allowed power consumption' - RBC/L2
#TEST-VAL-SUB026-7924#REF# FCT 4 Reception of P68 with Q_TRACKINIT=1 within Radio Hole area
#TEST-VAL-SUB026-7925#REF# FCT 5 Initial state related to integrity check alarms of balise transmission: alarms not ignored
#TEST-VAL-SUB026-3130#REF# EET CFX00037396 Initial state of track conditions

#REQ-UNISIG-SUB026-002150#REF# 3.12.2.3
On reception of route suitability data, the ERTMS/ETCS on-board equipment shall compare it with the corresponding Train Data stored on-board.
Unsuitability exists if:
a)	The loading gauge profile of the train is not included in the list of loading gauges accepted by trackside
b)	The list of traction systems accepted by the engine does not include the one received from trackside
c)	The axle load category of the train is higher than the permitted one received from trackside
TEST APPROACH:
The following aspects have been identified:
1) Loading gauge profile
2) List of traction systems
3) Axle load category
#TEST-VAL-SUB026-4H71#REF# FCT 1 Route suitability Loading Gauge information overwrite
#TEST-VAL-SUB026-4H73#REF# FCT 2 Route suitability Traction System information overwrite
#TEST-VAL-SUB026-4H72#REF# FCT 3 Route suitability Axle Load information overwrite
#TEST-VAL-SUB026-8100#REF# EET error expectation train is configured for M_VOLTAGE=0 only, received RUS with M_VOLTAGE > 0 and then with M_VOLTAGE = 0

#REQ-UNISIG-SUB026-002151#REF# to.3.12.2.3
If the train is not fitted with an electrical Traction system (i.e diesel engine), the train shall be suitable for all lines with electrical
traction systems.
UNISIG clarification: this case is not defined in the specification. A clarification is necessary.
#TEST-VAL-SUB026-8100#REF# FCT basic function train is configured for M_VOLTAGE=0 only, received RUS with M_VOLTAGE > 0 and then with M_VOLTAGE = 0

#REQ-UNISIG-SUB026-002155#REF# 3.12.2.4
If at least one unsuitability exists, the closest location corresponding to the unsuitability(ies) shall be considered as both the EOA and SvL
(instead of the EOA and SvL given by the MA), with no Release Speed. The driver shall be informed about all unsuitabilities.
UNISIG clarification:
"shall be considered as both the EOA and SvL" is interpreted as temporarily supervision. The ma is not shortened.

The location of the unsuitability is only used	as EoA, if this location is in front of the EoA given by the ma.
realised by: #REQ-UNISIG-SUB026-0552:03#REF#
realised by: #REQ-UNISIG-SUB026-0553:02#REF#

#REQ-UNISIG-SUB026-0552:03#REF# 3.12.2.4 #REQ-UNISIG-SUB026-002155#REF#
#REQ-UNISIG-SUB026-0557:02#REF#
#ANA-UNISIG-RouteSuitability-0003:01#REF#
If at least one unsuitability exists, the closest location corresponding to the unsuitability(ies) shall be temporarily considered as both the
EOA and SvL (instead of the EOA and SvL given by the MA), with no Release Speed.

clarifications:
The location is supervised like a SvL.
The EoA supervision means, that the Trip supervision of the EoA location is active also.

If EoA < RS location <= SvL, than RS location is only supervised as SvL only.
If RS location > SvL, than the RS location is not relevant for the current ma supervision.
TEST APPROACH:
The following aspects have been identified:
1) EoA and SvL with no Release Speed
2) EoA supervision
3) EoA < RUS location <= SvL
4) RUS location > SvL
#TEST-VAL-SUB026-4H71#REF# FCT 1 Route suitability Loading Gauge information overwrite
#TEST-VAL-SUB026-5241#REF# FCT 2 OS->TR transition due to passing RUS start with min save antenna position
#TEST-VAL-SUB026-5242#REF# FCT 3 EoA and RUS start do not interfere with each other
#TEST-VAL-SUB026-4H75#REF# FCT 4 Route suitability beyond SvL
#TEST-VAL-SUB026-5922#REF# EET error expectation Reception of RUS, train min safe front end has already entered the RUS start

#REQ-UNISIG-SUB026-0553:02#REF# 3.12.2.4 #REQ-UNISIG-SUB026-002155#REF#
#REQ-UNISIG-SUB026-010434#REF#
The driver shall be informed about all unsuitabilities.
TEST APPROACH:
The following aspects have been identified:
1) Loading gauge profile
2) List of traction systems
3) Axle load category
#TEST-VAL-SUB026-3131#REF# FCT 1 Route Suitability: Loading gauge
#TEST-VAL-SUB026-3132#REF# FCT 2 Route Suitability: Traction Power
#TEST-VAL-SUB026-3133#REF# FCT 3 Route Suitability: Axle load
#TEST-VAL-SUB026-4H74#REF# EET error expectation Route suitability Q_TRACKINIT=1
#TEST-VAL-SUB026-4H75#REF# EET error expectation Route suitability beyond SvL

#REQ-UNISIG-SUB026-0557:02#REF# 3.12.2.8
If, for any reasons, the train overpasses the location of the first route suitability where incompatibility occurs, it shall be tripped.
is realized with clarification to 3.12.2.4
realised by: #REQ-UNISIG-SUB026-0552:03#REF#

#REQ-UNISIG-SUB026-0559#REF# 3.12.2.10
The train is permitted to run without any route suitability data given from the track. No default values shall be used or supervised by the
on-board equipment, i.e. the initial state is that no restrictions related to route suitability exists.
#TEST-VAL-SUB026-4F68#REF# FCT basic function Route Suitability: resume initial state

#REQ-UNISIG-SUB026-0058#REF# 3.12.3.1.1
It shall be possible to transmit information to be displayed to the driver from the trackside to the on-board equipment in the form of text
messages.
realised by: #REQ-UNISIG-SUB026-002178#REF#
realised by: #REQ-UNISIG-SUB026-010624#REF#

#REQ-UNISIG-SUB026-002178#REF# to.3.12.3.1.1 #REQ-UNISIG-SUB026-0058#REF#
The trackside information "plain text message" (packet 72) shall be used to generate text messages to be displayed to the driver.
#TEST-VAL-SUB026-4544#REF# FCT basic function Pkt 72 M_MODETEXTDISPLAY = LS, L1 FS->LS[70]->FS[32]

#REQ-UNISIG-SUB026-010624#REF# to.3.12.3.1.1 #REQ-UNISIG-SUB026-0058#REF#
The trackside information "fixed text message" (packet 76) shall be used to generate text messages to be displayed to the driver.
#TEST-VAL-SUB026-4545#REF# FCT basic function P76 M_MODETEXTDISPLAY = LS, L2 FS->LS[70]->FS[31]

#REQ-UNISIG-SUB026-3037#REF# 3.12.3.2.1
Text messages shall be classified according to the following scheme:

is realized with ERA SRS DMI, 8.2.3.4.7
--- FINALISED ---
is realized in ERA SRS DMI, chapter 8.2.3.4.7
The realization is splitted. The requirements for display are realized in DMI (see #REQ-SAS_DMI-003283#REF#). The EVC provides the group
classification for each text message (see #REQ-SAS_DMI-003282:02#REF#).
#ANALYSE-VALUNISIG-5293#REF# FCT The DMI is in charge of the handling of auxiliary/important information. The requirement has to be covered by [ESBO_SyValBer].

#REQ-UNISIG-SUB026-3038:01#REF# 3.12.3.3.1 #ANA-UNISIG-TextMessages-0002:01#REF#
Fixed text messages shall be stored on-board in all languages that can be selected by the driver.

--- FINALISED ---
is realized in DMI (#REQ-FFFIS_MMI-009730:01#REF#)
The EVC transmits the Q_TEXT ID to DMI. There is realized a parameterizable text mapping table.
#ANALYSE-VALUNISIG-5281#REF# FCT The DMI is in charge of language management refer #REQ-SRS_DMI-000565#REF#. The requirement has to be covered by [ESBO_SyValBer].

#REQ-UNISIG-SUB026-3044#REF# 3.12.3.4.2
The following events can be used to define the start condition:
  Location
  Mode (start display as soon as in mode)
  Level (start display as soon as in level)
#TEST-VAL-SUB026-3523#REF# FCT level text end conditions level evaluated once the text message is displayed
#TEST-VAL-SUB026-3475#REF# FCT mode, location start/end condition for location based text messages

#REQ-UNISIG-SUB026-3045:01#REF# 3.12.3.4.3
The following events can be used to define the end condition:
  Location
  Time
  Mode (stop display when leaving mode)
  Level (stop display when leaving level)
UNISIG clarification:
"when leaving mode/level" means, that this event is only triggered by a transition from the given mode/level to another mode/level.
The description in the definition of the variables is not correct.
#TEST-VAL-SUB026-8259#REF# EET error expectation Management of several conditional text messages
#TEST-VAL-SUB026-3523#REF# FCT level text end conditions level evaluated once the text message is displayed
#TEST-VAL-SUB026-3475#REF# FCT location start/end condition for location based text messages
#TEST-VAL-SUB026-3474#REF# FCT mode start/end condition for not location based text messages
#TEST-VAL-SUB026-7712#REF# FCT time Time is used as the end condition for text message

#REQ-UNISIG-SUB026-3050:01#REF# 3.12.3.4.3.1
It shall be possible to define whether one or all of the events used from the list in 3.12.3.4.2/3.12.3.4.3 have to be fulfilled to define the
start/end condition. This definition shall apply to both start and end conditions.
A combined condition specifying "all of the events" will be fulfilled, when the last of the events specified occured while the
condition is evaluated (i.e. it has to be memorized that an event occured).
TEST APPROACH:
The following aspects have been identified:
1) one event has to be fulfilled
2) all events have to be fulfilled
#TEST-VAL-SUB026-8301#REF# FCT 1 Q_TEXTDISPLAY = 0
#TEST-VAL-SUB026-3475#REF# FCT 2 start/end condition for location based text messages
#TEST-VAL-SUB026-7614#REF# EET CFX00041410 Evaluation of stop condition L_TEXTDISPLAY/T_TEXTDISPLAY for text message with Q_TEXTDISPLAY = 1 - spezial scenario
#TEST-VAL-SUB026-7615#REF# EET CFX00041413 Evaluation of stop condition L_TEXTDISPLAY/T_TEXTDISPLAY for text message with Q_TEXTDISPLAY = 1
#TEST-VAL-SUB026-7613#REF# EET error expectation Evaluation of start/stop condition for fixed text message with Q_TEXTDISPLAY = 1

#REQ-UNISIG-SUB026-002240#REF# 3.12.3.4.3.2
In case a confirmation of the text message is requested, it shall be possible to define whether the driver acknowledgement is considered:
a)	As always ending the text display, regardless of the end condition defined in 3.12.3.4.3.1
b)	As a necessary condition to end the text display, in addition to the end condition defined in 3.12.3.4.3.1.
#TEST-VAL-SUB026-7715#REF# FCT a) and b) Driver acknowledgement taken into account for text message display end condition

#REQ-UNISIG-SUB026-3046:01#REF# 3.12.3.4.4
The end condition shall be evaluated as soon as the start condition is fulfilled. No display shall take place if the end condition is
immediately fulfilled.
TEST APPROACH:
The following aspects have been identified:
1) start condition fulfilled before end condition fulfilled
2) end condition fulfilled before start condition fulfilled, end condition not fulfilled when start condition fulfilled
3) end condition already fulfilled when start condition fulfilled (no display)
4) start and end condition fulfilled at same time 
#TEST-VAL-SUB026-3474#REF# FCT 1 start/end condition for not location based text messages
#TEST-VAL-SUB026-3522#REF# FCT 2 text end conditions mode evaluated once the text message is displayed
#TEST-VAL-SUB026-7721#REF# FCT 3 Evaluation of start and end conditions for displaying text messages
#TEST-VAL-SUB026-3523#REF# FCT 4 text end conditions level evaluated once the text message is displayed

#REQ-UNISIG-SUB026-3047#REF# 3.12.3.4.5
Once the text message is displayed and the end condition is fulfilled, the start condition shall not be re-evaluated.
#TEST-VAL-SUB026-3474#REF# FCT basic function start/end condition for not location based text messages

#REQ-UNISIG-SUB026-3048#REF# 3.12.3.4.6
When the end event "location" is used, the length on which the text is displayed shall refer to the location used for the start
condition, independently from other start events.
#TEST-VAL-SUB026-3475#REF# FCT basic function start/end condition for location based text messages

#REQ-UNISIG-SUB026-3662:01#REF# to.3.12.3.4.6 #ANA-UNISIG-CR0397-0001:01#REF#
If no start condition "location" is defined but an end condition "location", the end condition "location" shall be
ignored and a basic diagnostic event shall be triggered.
UNISIG clarification:
Subset 40, 4.2.4.10 defines "The use of the end condition “location” shall be allowed only if the start condition 'location" is
used."
This requirement assesses the non compliance - see analysis
#TEST-VAL-SUB026-3759#REF# FCT basic function text message with end condition 'location' and no start condition 'location'

#REQ-UNISIG-SUB026-3049:01#REF# 3.12.3.4.7
In case a confirmation of the text message is requested, it shall be possible to define whether the service brake or emergency brake application
shall be commanded  if the driver does not acknowledge before the end condition is fulfilled.
#TEST-VAL-SUB026-3761#REF# FCT basic function P72/76 Q_TEXTCONFIRM 3/2

#REQ-UNISIG-SUB026-002252#REF# 3.12.3.4.7.1
If the driver does not acknowledge before the end condition is fulfilled, the text message shall remain displayed until acknowledged by driver.
#TEST-VAL-SUB026-3761#REF# FCT basic function P72/76 Q_TEXTCONFIRM 3/2

#REQ-UNISIG-SUB026-002254#REF# 3.12.3.4.7.2
If the driver acknowledges before the end condition is fulfilled, the on-board equipment shall consider the driver acknowledgement as requested
by trackside (see 3.12.3.4.3.2).
#TEST-VAL-SUB026-7715#REF# FCT basic function Driver acknowledgement taken into account for text message display end condition

#REQ-UNISIG-SUB026-002264#REF# 3.12.3.5.2
When the driver has acknowledged a text message with a request to report driver acknowledgement, the driver acknowledgement report, including
the text message identifier, shall be sent to the RBC referenced in the request.
UNISIG clarification:
the message is considered as sent, if the safe radio connecteion is lost (see 3.5.4.5) or the session is terminated to the announced RBC
#TEST-VAL-SUB026-7719#REF# FCT basic function Driver acknowledgement report together with the text message id is sent to the RBC when requested by trackside
#TEST-VAL-SUB026-7786#REF# FCT error expectation Driver acknowledgemnet report for text message sent to RBC - two communication sessions can be handled simultaneously
#TEST-VAL-SUB026-7787#REF# FCT error expectation Driver acknowledgemnet report for text message sent to RBC - loss of safe radio connection

#REQ-UNISIG-SUB026-002266#REF# 3.12.3.5.3 #REQ-UNISIG-SUB026-010044#REF#
A new text message with request for report of driver acknowledgement shall be rejected by the ERTMS/ETCS on-board equipment if it has the same
text message identifier as a previously received text message, which the driver has not yet acknowledged.
#TEST-VAL-SUB026-7719#REF# FCT basic function Driver acknowledgement report together with the text message id is sent to the RBC when requested by trackside
#TEST-VAL-SUB026-7792#REF# EET error expectation Text msg with same ID is rejected if sent before driver acknowledges

#REQ-DESIGN-CR-0371#REF# 3.12.4.2
For OS and LS mode the mode profile shall define the entry and the length of the On Sight/Limited Supervision area. For SH mode the mode profile
only defines the entry location to SH mode, any length given shall be ignored by the on-board.
#TEST-VAL-SUB026-3789#REF# FCT LS LS mode profile defines the entry and the length of the Limited Supervision area
#TEST-VAL-SUB026-3141#REF# FCT OS; SH Start and end of mode profile
#TEST-VAL-SUB026-5487#REF# EET error expectation Handling of two adjacent OS areas
#TEST-VAL-SUB026-5488#REF# EET error expectation Handling of two adjacent LS areas

#REQ-UNISIG-SUB026-005399#REF# to.3.12.4.2
If more than one EoA or SvL are supervised at the same time (i.e. temporary supervision of the begin of mode profile, route suitability), the
most restrictive EoA and SvL shall be supervised.
a definition is necessary, when more than one mode profile or RS is supervised.
TEST APPROACH:
The following main cases were identified:
1) handling of one temporary EoA/SvL together with the MA EoA/SvL
2) handling of more than one temporary EoA/SvL
For these cases, the following aspects have been identified:
1) EoA1 < EoA2 and SvL1 < SvL2
2) EoA1 < EoA2 and SvL1 > SvL2
3) EoA1 < EoA2 and SvL1 = SvL2
4) EoA1 = EoA2 and SvL1 < SvL2
#TEST-VAL-SUB026-7676#REF# FCT 1.1 - 1.4 Handling of temporay EoA/SvL and MA EoA/SvL
#TEST-VAL-SUB026-7677#REF# FCT 2.1 - 2.4 Handling of more than one temporay EoA/SvL

#REQ-UNISIG-SUB026-0580#REF# 3.12.4.3 #REQ-UNISIG-SUB026-010157#REF#
On reception of a new MA (with or without Mode Profile) the on-board equipment shall delete the currently supervised Mode Profile.
#TEST-VAL-SUB026-3139#REF# FCT basic function Mode Profile deleted due to new MA without MP

#REQ-UNISIG-SUB026-3563#REF# 3.12.4.3.1 #REQ-UNISIG-SUB026-010157#REF#
Exception: When receiving a new MA by infill, any currently supervised Mode Profile shall be deleted only beyond the reference location of the
infill information.
TEST APPROACH:
The following aspects have been identified:
1) MP removal beyond ref. location
2) MP (beyond ref. location) removal of acknowledgment window
3) MP (in front of ref. location) not entered yet
4) MP replaced with new MP at reference location
#TEST-VAL-SUB026-3014#REF# FCT 1 In-fill MA without MP overrides current Mode Profile LS starting with the in-fill reference location
#TEST-VAL-SUB026-4656#REF# FCT 2 Linking information for in-fill location reference in same BG as in-fill MA
#TEST-VAL-SUB026-3655#REF# FCT 3 In-fill MA without Mode Profile deletes current Mode Profile starting with the in-fill reference location
#TEST-VAL-SUB026-3732#REF# FCT 4 In-fill MA with MP-OS overrides current Mode Profile LS starting with the in-fill reference location
#TEST-VAL-SUB026-7133#REF# EET error expectation Infill MA +MP received prior to to start of none infill MP

#REQ-UNISIG-SUB026-010306:01#REF# to.3.12.4.3 #ANA-UNISIG-ModeProfile-0003:01#REF#
The train reaction, which is defined in #DSC-TBL-ModeProfile-0001:01#REF#, shall be executed, when
the train receives a new mode profile and
- the acknowledgement area of this mode profile overlaps the currently supervised mode profile
OR
- the mode profile contains more than one mode profile and the acknowledgement area of the second mode profile is inside the first mode profile
area, including the acknowledgement area.

remark: the desicions for OS shall be valid for LS also.
TEST APPROACH:
Every line of #DSC-TBL-ModeProfile-0001:01#REF# has to be verified.
#TEST-VAL-SUB026-5947#REF# FCT 1, 2, 3, 4, 5, 6 (LS) Evaluation of MP-LS acknowledgment requests
#TEST-VAL-SUB026-5946#REF# FCT 1, 2, 3, 4, 5, 6 (OS) Evaluation of MP-OS acknowledgment requests
#TEST-VAL-SUB026-5948#REF# FCT 7 Evaluation of MP acknowledgment requests for two non overlapping MP areas of same kind
#TEST-VAL-SUB026-5949#REF# FCT 8 Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind
#TEST-VAL-SUB026-5950#REF# FCT 9 Evaluation of MP acknowledgment requests for two non overlapping MP areas with overlapping acknowledgment windows

#REQ-UNISIG-SUB026-010513#REF# 3.12.4.4
In case the mode profile information for shunting is overwritten by a new shunting profile, before the on-board equipment switches to SH mode, a
previous list of balise groups for SH area shall be deleted or replaced by a new list of balise groups for SH area.
realised by: #REQ-UNISIG-SUB026-0581:01#REF#

#REQ-UNISIG-SUB026-0581:01#REF# 3.12.4.4 #REQ-UNISIG-SUB026-005836#REF#
#REQ-UNISIG-SUB026-010513#REF#
The current list of balise groups for SH area shall be deleted, if
- the current mode profile is deleted before the mode is changed to SH (e.g. mode is changed to another mode as SH)
OR
- a new mode profile is received
OR
- a SH authorised is received

Remark: If the new mode profile for shunting or the SH authorised contains a new list of balise groups for SH area, the new list replaces the
current list.
UNISIG clarification:
a current list is always deleted, when a new order to SH is received or the current mode profile is deleted
TEST APPROACH:
Following aspects have been identified:
1) the current mode profile is deleted before the mode is changed to SH
1.1) MP deleted
1.1.1) new MA without MP
1.1.2) mode change
1.2) MP replaced
2) new mode profile is received
2.1) list deleted
2.2) list replaced
3) a SH authorised is received
3.1) list deleted
3.2) list replaced
#TEST-VAL-SUB026-7047#REF# FCT 1.1.1 List of balises for SH Area deleted due to MP deletion
#TEST-VAL-SUB026-4C53#REF# FCT 1.1.2 Stored data: List of balises for SH area when mode changes to SR/L1
#TEST-VAL-SUB026-7046#REF# FCT 1.2 List of balises for SH Area deleted by new MP
#TEST-VAL-SUB026-3030#REF# FCT 2.1 , CFX00039616 List of balises for SH Area deleted when receiving new MP without P49
#TEST-VAL-SUB026-3032#REF# FCT 2.2 List of balises for SH Area replaced by new P49
#TEST-VAL-SUB026-7044#REF# FCT 3.1 List of balises for SH Area deleted by M28
#TEST-VAL-SUB026-7045#REF# FCT 3.2 List of balises for SH Area replaced by new P49 from M28
#TEST-VAL-SUB026-5986#REF# EET error expectation List of balises for SH area when entering UN
#TEST-VAL-SUB026-5987#REF# EET error expectation List of balises for SH area when entering SN
#TEST-VAL-SUB026-7151#REF# EET error expectation P49 buffer processing
#TEST-VAL-SUB026-8163#REF# EET error expectation Level 2, List of balises for SH area onboard, driver selects SH

#REQ-DESIGN-CR-0759#REF# to.3.12.4.4 #ANA-UNISIG-ModeProfile-0003:01#REF#
#ANA-UNISIG-SUB040-0009:01#REF#
Enthält ein mode profile (packet 80) mehr als eine Instanz eines SH-Bereiches, wird nur der erste SH-Bereich, insbesondere dessen
Acknowledgement-Bereich  berücksichtigt.
TEST APPROACH:
The following aspects have been identified:
1) acknowledgment window
2) speed supervision
#TEST-VAL-SUB026-3315#REF# FCT 1 ACK-Bereich des 2. SH-Bereiches beginnt vor dem ACK-Bereich des 1. SH-Bereiches
#TEST-VAL-SUB026-3314#REF# FCT 2 , CFX00039542 Processing of P80 with two MP-SH with same location but different V_MAMODE

#REQ-UNISIG-SUB026-0582#REF# 3.12.4.5
The beginning of the Mode Profile relates to the max safe front end of the train.
realised by: #REQ-UNISIG-SUB026-0790#REF#
realised by: #REQ-UNISIG-SUB026-0805#REF#
realised by: #REQ-UNISIG-SUB026-3525#REF#

#REQ-UNISIG-SUB026-0583#REF# 3.12.4.6
The end of the mode profile relates to the min safe front end of the train.
realised by: #REQ-UNISIG-SUB026-0282#REF#
realised by: #REQ-UNISIG-SUB026-3531#REF#

#REQ-UNISIG-SUB026-010101#REF# to.3.12.4.6
In case the trackside commands a mode profile with length zero, the onboard shall supervise the shortest length it can internally handle.
UNISIG clarification:
Also a mode profile with distance 0 have to be supervised with max and min safe position
#TEST-VAL-SUB026-7447#REF# FCT basic function Variable test L_MAMODE

#REQ-UNISIG-SUB026-002290#REF# 3.12.5.3
If the ERTMS/ETCS on-board equipment receives a new LX information with the same identity as an already received LX information, the new LX
information shall replace the previous one.
#TEST-VAL-SUB026-7644#REF# FCT basic function LX information overwritten by new received LX with same ID
#TEST-VAL-SUB026-7660#REF# EET error expectation LX not protected with no stop required replaced by LX not protected with stop required

#REQ-UNISIG-SUB026-010551#REF# to.3.12.5.3 #ANA-UNISIG-LevelCrossing-0001#REF#
If the ERTMS/ETCS on-board equipment receives a new LX information with the same identity as an already received LX information and the new LX
information is protected, the supervision of the former non protected LX information shall be stopped.

note:
Protected LX information not resetting a stored non protected LX information can be ignored by the ERTMS/ETCS on-board equipment.
UNISIG clarification: see analysis
#TEST-VAL-SUB026-7645#REF# FCT basic function LX supervision is stopped when LX becomes protected

#REQ-UNISIG-SUB026-010500#REF# to.3.12.5.3 #ANA-UNISIG-LevelCrossing-0002#REF#
Stopping in rear of non protected LX shall not be required again if the ERTMS/ETCS on-board equipment receives a new LX information with the
same identity as the currently supervised LX information and the new stopping area start of has been passed already.
UNISIG clarification:
a recurrence of supervision the start location, especailly with EoA/SvL isn't desired.
#TEST-VAL-SUB026-7662#REF# FCT basic function Updated LX information with new stop location already passed

#REQ-UNISIG-SUB026-002292#REF# 3.12.5.4
Level Crossing information shall be given as profile data, corresponding to the LX start location and the length of the LX area.
#TEST-VAL-SUB026-7644#REF# FCT basic function LX information overwritten by new received LX with same ID

#REQ-UNISIG-SUB026-002294#REF# 3.12.5.5
Level Crossing information shall indicate whether the LX is protected or not.
is covered by the definition of variable Q_LXSTATUS
realised by: #REQ-UNISIG-SUB026-008088#REF#

#REQ-UNISIG-SUB026-002296#REF# 3.12.5.6
In case the LX is not protected, ERTMS/ETCS on-board equipment shall be informed:
a)	at which speed the LX is allowed to be passed
b)	whether the stopping of the train in rear of the LX start location is required or not
#TEST-VAL-SUB026-7644#REF# FCT basic function LX information overwritten by new received LX with same ID

Chapter 3.13

TEST APPROACH:
The core requirements of this chapter e.g. braking curve calculation are realized one module of the application software (abbreviation for the
module: BC). All related requirements are assigned to this module.
The appropriated module test cases are not outlined here. Please refer to /ESBO_UUE/ --> reference ID: ESBO_SWModTstSpezBC for detailed
information. 
Also boundary test or test based on equivalence classes and input partition for all used values is implemented in the BC module verification
(see /ESBO_SWValPl/ --> '/EN50128/ --> Table A13').
The quality of the module tests is ensured by review of the module test specification and test implementation as part of the module review. The
result of the review is documented in /ESBO_UUE/ --> reference ID ESBO_VerBer.

The additional VER/VAL test cases focus on the integration of the BC module. 
The BC input parameters have to be tested. 
The consideration of BC output parameter has to be tested.
Function with SW module interaction have to be tested. 

The boundary test (and the provision to BC) of the track side parameter takes place by the test cases for SUBSET-026 chapter 7.
Note: The conversional brake model destinguishes between brake build up time for V_target =0 and V_target>0. The configuration for pre-programed
brake model includes only one value (refer #REQ-UNISIG-SUB026-006967#REF#) which is duplicated for the internal representaion of the brake model
(refer #REQ-DESIGN-012791#REF#).
		
#REQ-UNISIG-SUB026-006929#REF# 3.13.2.2.1.3
The speed and distance monitoring shall use braking models acquired as Train Data, unless the brake percentage is acquired as Train Data and the
conversion model is applicable (see 3.13.3.2 for its validity limits).
realised by: #REQ-UNISIG-SUB026-007088:01#REF#
realised by: #REQ-UNISIG-SUB026-007093#REF#

#REQ-UNISIG-SUB026-006931#REF# 3.13.2.2.2.1
The traction model shall be given as a step function as indicated in Figure 29. It shall describe the time delay T_traction_cut_off from the
traction cut-off command by the on-board (t0) to the moment the acceleration due to traction (A_traction) is guaranteed to be zero (t1). The
estimated acceleration value of the train shall be considered during this time delay.

#DSC-UNISIG-SUB026-002356#REF#

Figure 29: Traction Model
#TEST-VAL-SUB026-4F76#REF# BVA max value (40950ms) Value range for T_tractio_cut_off: max value
#TEST-VAL-SUB026-4F75#REF# BVA min value (0ms) Value range for T_tractio_cut_off: min value

#REQ-UNISIG-SUB026-006937#REF# 3.13.2.2.3.1.2
It shall be possible to define up to seven steps for each speed dependent deceleration model.
#TEST-VAL-SUB026-4F92#REF# ECT EB nominal deceleration, full SB deceleration Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service
#TEST-VAL-SUB026-4F89#REF# FCT normal service brake model Normal Service Brake Model

#REQ-UNISIG-SUB026-006944#REF# 3.13.2.2.3.1.4
The last step of A_brake(V) shall by definition be considered as open ended, i.e. it has no upper speed limit.
#ANALYSE-VALUNISIG-4407#REF# FCT The interpretation of the last step is ensured by the implementation of the appropriated BAS class. Verification takes place via BAS module test.

#REQ-UNISIG-SUB026-006946#REF# 3.13.2.2.3.1.6
The model shall be used for the emergency brake nominal deceleration (A_brake_emergency(V)), for the full service brake deceleration
(A_brake_service(V)) and for the normal service brake deceleration (A_brake_normal_service(V)).
#TEST-VAL-SUB026-4F92#REF# FCT EB nominal deceleration, full SB deceleration Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service
#TEST-VAL-SUB026-4F89#REF# FCT normal service brake model Normal Service Brake Model

#REQ-UNISIG-SUB026-006947#REF# 3.13.2.2.3.1.7
It shall be possible to define individual speed dependent deceleration models of A_brake_emergency(V) and A_brake_service(V) for each
combination of use of regenerative brake, eddy current brake and magnetic shoe brake.
"special brakes" should not be realized 
=> the parametrization is to be restricted.
TEST APPROACH:
Dependency on special brakes not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF# hence only one set of SB/EB
model taken into account.
#TEST-VAL-SUB026-4F92#REF# FCT EB nominal deceleration, full SB deceleration Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service
#TEST-VAL-SUB026-4F89#REF# FCT normal service brake model Normal Service Brake Model

#REQ-UNISIG-SUB026-006949#REF# 3.13.2.2.3.1.9
It shall be possible to define up to two sets of three models of A_brake_normal_service(V):
a)	one set applicable when the brake position is in “Freight train in G”
b)	one set applicable when the brake position is in “Passenger train in P” or “Freight train in P”
#TEST-VAL-SUB026-4F89#REF# ECT basic function Normal Service Brake Model

#REQ-UNISIG-SUB026-006952#REF# 3.13.2.2.3.1.10
A set of A_brake_normal_service(V) shall be defined as a function of the full service brake deceleration at zero speed, A_brake_service(V=0):
If A_brake_service(V = 0) ≤ A_SB01
A_brake_normal_service(V) = A_brake_normal_service_0(V)
if A_SB01 < A_brake_service(V = 0) ≤ A_SB12
A_brake_normal_service(V) = A_brake_normal_service_1(V)
if A_SB12 < A_brake_service (V = 0)
A_brake_normal_service(V) = A_brake_normal_service_2(V)
#ANALYSE-VALUNISIG-4408#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-006964#REF# 3.13.2.2.3.2.5
This model for T_brake_build_up shall be used for the emergency brake (T_brake_emergency) and for the full service brake (T_brake_service).
realised by: #REQ-UNISIG-SUB026-006967#REF#

#REQ-UNISIG-SUB026-006967#REF# 3.13.2.2.3.2.8 #REQ-UNISIG-SUB026-006964#REF#
It shall be possible to define individual values of T_brake_emergency and T_brake_service for each combination of use of regenerative brake,
eddy current brake, magnetic shoe brake and Ep brake.
"special brakes" should not be realized 
=> the parametrization is to be restricted.
TEST APPROACH:
Dependency on special brakes not part of R8.0 (refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#) hence only one set of
T_brake_emergency and T_brake_service taken into account
#TEST-VAL-SUB026-4F92#REF# ECT EB/SB min=0s, max=40.75s, no special brakes Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service

#REQ-UNISIG-SUB026-006972#REF# 3.13.2.2.4.1
The brake position shall be set to one of the following three values:
a)	Passenger train in P
b)	Freight train in P
c)	Freight train in G

--- FINALISED ---
The brake position is determined from the train data.
#TEST-VAL-SUB026-4F81#REF# BVA basic function Parameter brake position

#REQ-UNISIG-SUB026-006983#REF# 3.13.2.2.6.1
For each special brake (regenerative brake, eddy current brake, magnetic shoe brake and electro-pneumatic brake), it shall be possible to
configure the on-board to one of the following possibilities marked with an “X” in Table 3

#DSC-UNISIG-SUB026-002446#REF#

Table 3: On-board Configuration in relation to special brakes
realised by: #REQ-UNISIG-SUB026-006982#REF#

#REQ-UNISIG-SUB026-006982#REF# 3.13.2.2.6.1 #REQ-UNISIG-SUB026-006983#REF#
For each special brake (regenerative brake, eddy current brake, magnetic shoe brake and electro-pneumatic brake), it shall be possible to
configure the on-board to one of the following possibilities marked with an “X” in Table 3


Table 3: On-board Configuration in relation to special brakes
"special brakes" should not be realized 
=> the parametrization is to be restricted.
TEST APPROACH:
Dependency on special brakes not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#. 
#ANALYSE-VALUNISIG-7663#REF# FCT The feature special brakes is not part of R8.0 hence only no interface exists relevant. The use of the configuration for the brake curve calculation is verified by BC module test.

#REQ-UNISIG-SUB026-002448#REF# 3.13.2.2.6.2
When an interface exists with the regenerative brake, eddy current brake, magnetic shoe brake system and/or the Ep brake on-board system and
depending whether their status affects the concerned brake parameter(s), the speed and distance monitoring shall take into account their status
“active” or “not active” to select the appropriate brake parameter(s) captured as Train Data, according to Table 4:

#DSC-UNISIG-SUB026-002450#REF#

Table 4: Selection of brake parameters according to status of special brakes
realised by: #REQ-UNISIG-SUB026-006984#REF#

#REQ-UNISIG-SUB026-006984#REF# 3.13.2.2.6.2 #REQ-UNISIG-SUB026-002448#REF#
When an interface exists with the regenerative brake, eddy current brake, magnetic shoe brake system and/or the Ep brake on-board system and
depending whether their status affects the concerned brake parameter(s), the speed and distance monitoring shall take into account their status
“active” or “not active” to select the appropriate brake parameter(s) captured as Train Data, according to Table 4:



Table 4: Selection of brake parameters according to status of special brakes
TEST APPROACH:
Dependency on special brakes not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#. 
#ANALYSE-VALUNISIG-7647#REF# FCT The feature Special Brakes is not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#

#REQ-UNISIG-SUB026-006991#REF# 3.13.2.2.7.1
The on-board shall be configured to define whether the service brake command is implemented or not, i.e. whether a service brake interface is
implemented to command a full service brake effort.
#TEST-VAL-SUB026-5644#REF# FCT Interface to SB available Interface to SB available, T_bs1/T_bs2 (d_SBI) dependency on train length change
#TEST-VAL-SUB026-5645#REF# FCT Interface to SB not available Interface to SB not available, T_bs1/T_bs2 (d_SBI) have no dependency on train length change

#REQ-UNISIG-SUB026-006992#REF# 3.13.2.2.7.2
The on-board shall be configured to define whether the service brake feedback is implemented or not, i.e. whether it is able to acquire from the
service brake interface the information that the service brake is currently applied (e.g. from the main brake pipe pressure or brake cylinder
pressure).
TEST APPROACH:
The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#. 
#TEST-VAL-SUB026-4B76#REF# FCT SB feedback enabled T_indication is 5s if SB feedback available for use

#REQ-UNISIG-SUB026-006994#REF# 3.13.2.2.8.1
The on-board shall be configured to define whether the traction cut-off command is implemented, i.e. whether the interface to the traction
system is implemented or not.
#TEST-VAL-SUB026-5646#REF# FCT traction cut-off command is implemented Traction cut-off is implemented, dependency on T_traction
#TEST-VAL-SUB026-5647#REF# FCT traction cut-off command is not implemented Traction cut-off is not implemented, dependency on T_traction

#REQ-UNISIG-SUB026-006997#REF# 3.13.2.2.9.1.1
If the braking models are captured as Train Data, rolling stock correction factors shall be defined in the ETCS on-board equipment. If the brake
percentage is captured as Train Data and the conversion model is used (see 3.13.3.2 for its validity limits), no rolling stock correction factor
shall apply.
realised by: #REQ-UNISIG-SUB026-006998#REF#
realised by: #REQ-UNISIG-SUB026-007162#REF#

#REQ-UNISIG-SUB026-006998#REF# 3.13.2.2.9.1.2 #REQ-UNISIG-SUB026-006997#REF#
For each defined individual speed dependent deceleration model of A_brake_emergency(V) (i.e. corresponding to each combination of use of
regenerative brake, eddy current brake and magnetic shoe brake), one set of rolling stock correction factors Kdry_rst(V, EBCL) and Kwet_rst(V)
shall be defined in the on-board equipment.
TEST APPROACH:
Dependency on special brakes not part of R8.0 (refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#) hence only one set of
T_brake_emergency and T_brake_service taken into account
#TEST-VAL-SUB026-4F92#REF# ECT basic function Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service

#REQ-UNISIG-SUB026-006999#REF# 3.13.2.2.9.1.3 #REQ-UNISIG-SUB026-007051:01#REF#
For a given confidence level on emergency brake safe deceleration (EBCL), the rolling stock correction factor Kdry_rst(V) shall be given as a
step function of speed, with the same steps as the ones of A_brake_emergency(V).
#TEST-VAL-SUB026-4F92#REF# ECT basic function Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service

#REQ-UNISIG-SUB026-007001#REF# 3.13.2.2.9.1.5
The rolling stock correction factor Kwet_rst(V) shall be given as a step function of speed, with the same steps as the ones of
A_brake_emergency(V). It represents the loss of deceleration with regards to emergency braking on dry rails, when the emergency brake is
commanded on wet rails, according to wheel/rail adhesion reference conditions.
The correction factor Kwet_rst is limited to 1
#TEST-VAL-SUB026-4F92#REF# ECT basic function Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service

#REQ-UNISIG-SUB026-007004#REF# 3.13.2.2.9.2.1
The speed dependent correction factors for gradient on the normal service brake, Kn+(V) and Kn-(V), shall be given as step functions in the
range from 0 to 10 m/s2.
#TEST-VAL-SUB026-4F83#REF# ECT in range values Normal SB brake model correction factors for gradient Kn+/-
#TEST-VAL-SUB026-4F85#REF# ECT min/max values Normal SB brake model correction factors for gradient Kn+/-: min/max values

#REQ-UNISIG-SUB026-007005#REF# 3.13.2.2.9.2.2
It shall be possible to define up to five steps for Kn+(V) and for Kn-(V), respectively.
#TEST-VAL-SUB026-4F83#REF# ECT 1 step Normal SB brake model correction factors for gradient Kn+/-
#TEST-VAL-SUB026-4F85#REF# ECT 5 steps Normal SB brake model correction factors for gradient Kn+/-: min/max values

#REQ-UNISIG-SUB026-007012#REF# 3.13.2.2.9.2.4
Kn+(V) shall be applicable for positive gradients.
realised by: #REQ-UNISIG-SUB026-007219#REF#

#REQ-UNISIG-SUB026-007013#REF# 3.13.2.2.9.2.5
Kn-(V) shall be applicable for negative gradients.
realised by: #REQ-UNISIG-SUB026-007219#REF#

#REQ-UNISIG-SUB026-007014#REF# 3.13.2.2.9.2.6
The last step of the Kn+(V) or Kn-(V) shall by definition be considered as open ended, i.e. it has no upper speed limit.
#ANALYSE-VALUNISIG-4409#REF# FCT The interpretation of the last step is ensured by the implementation of the appropriated BAS class. Verification takes place via BAS module test.

#REQ-UNISIG-SUB026-002507#REF# 3.13.2.2.10.1
It shall be possible to define the nominal rotating mass to be used for compensating the gradient, instead of the two related fixed values
defined in A.3.1.
realised by: #REQ-UNISIG-SUB026-007016:01#REF#

#REQ-UNISIG-SUB026-007016:01#REF# to.3.13.2.2.10.1 #REQ-UNISIG-SUB026-002507#REF#
The nominal rotating mass to be used for compensating the gradient shall be parameterizable for each pre-programmed brake model.
min: 2%
max:15%
special value: 0 - undefined
default: undefined
UNISIG clarification:
a parameterized value for the nominal rotating mass can given
only for the pre-programmed models (see definition of conversion model in 3.13.3.1.1).
for a conversion model is this value undefined

the range is given from the fixed limits in A3.1
#TEST-VAL-SUB026-4F77#REF# BVA basic function Value range for nominal rotating mass: min, max, unknown

#REQ-UNISIG-SUB026-007037#REF# 3.13.2.3.4.1
The speed and distance monitoring shall take into account the following types of track condition received from trackside (see section 3.12.1):
powerless section, inhibition of regenerative brake, eddy current brake and magnetic shoe brake.
TEST APPROACH:
Dependency on special brakes not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#. 
#ANALYSE-VALUNISIG-7646#REF# FCT The feature Special Brakes is not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#

#REQ-UNISIG-SUB026-007045#REF# 3.13.2.3.7.1
It shall be possible by means of a National Value to inhibit the use of the service brake command in target speed monitoring.
realised by: #REQ-UNISIG-SUB026-007484#REF#
realised by: #REQ-UNISIG-SUB026-007593#REF#

#REQ-UNISIG-SUB026-007046#REF# 3.13.2.3.7.2
It shall be possible to state by means of a National Value whether an emergency brake command has to be revoked, both in ceiling speed and
target speed monitoring, when:
a)	the Permitted Speed supervision limit is no longer exceeded, or
b)	the train is at standstill.
realised by: #REQ-UNISIG-SUB026-007458#REF#
realised by: #REQ-UNISIG-SUB026-007493#REF#
realised by: #REQ-UNISIG-SUB026-007494:01#REF#
realised by: #REQ-UNISIG-SUB026-007986#REF#

#REQ-UNISIG-SUB026-007049#REF# 3.13.2.3.7.3
It shall be possible by means of a National Value to inhibit the guidance curve (GUI).
realised by: #REQ-UNISIG-SUB026-007254#REF#
realised by: #REQ-UNISIG-SUB026-007345#REF#
realised by: #REQ-UNISIG-SUB026-007589#REF#

#REQ-UNISIG-SUB026-007050#REF# 3.13.2.3.7.4
It shall be possible by means of a National Value to inhibit the service brake feedback function.
realised by: #REQ-UNISIG-SUB026-007560#REF#
realised by: #REQ-UNISIG-SUB026-007590#REF#

#REQ-UNISIG-SUB026-007051:01#REF# 3.13.2.3.7.5
It shall be possible by means of National Values to indicate to the on-board equipment the required confidence level on the emergency brake safe
deceleration, when the emergency brake is commanded on dry rails (see 3.13.2.2.9.1.4).
realised by: #REQ-UNISIG-SUB026-006999#REF#
realised by: #REQ-UNISIG-SUB026-007579:01#REF#

#REQ-UNISIG-SUB026-007052#REF# 3.13.2.3.7.6
It shall be possible by means of a National Value to indicate to the on-board equipment the available wheel/rail adhesion, weighted between the
wheel/rail adhesion for dry rails and the wheel/rail adhesion for wet rails according to reference conditions.
realised by: #REQ-UNISIG-SUB026-007162#REF#
realised by: #REQ-UNISIG-SUB026-007578#REF#

#REQ-UNISIG-SUB026-002571#REF# 3.13.2.3.7.7
In order to adapt the train behaviour under reduced adhesion conditions, it shall be possible by means of National Values to limit to a maximum
value the speed dependent deceleration for the emergency brake. Three values shall be applicable for a given combination of the brake position
and of the type of brakes:
a)	the first value shall be used for “Passenger train in P” with special/additional brakes independent from wheel/rail adhesion;
b)	the second value shall be used for “Passenger train in P” without special/additional brakes independent from wheel/rail adhesion;
c)	the third value shall be used for “Freight train in P” or “Freight train in G”.
realised by: #REQ-UNISIG-SUB026-007054#REF#
realised by: #REQ-UNISIG-SUB026-007055#REF#
realised by: #REQ-UNISIG-SUB026-007056#REF#

#REQ-UNISIG-SUB026-007054#REF# 3.13.2.3.7.7 #REQ-UNISIG-SUB026-002571#REF#
In order to adapt the train behaviour under reduced adhesion conditions, it shall be possible by means of National Values to limit to a maximum
value the speed dependent deceleration for the emergency brake. Three values shall be applicable for a given combination of the brake position
and of the type of brakes:
a) the first value shall be used for “Passenger train in P” with special/additional brakes independent from wheel/rail adhesion;
realised by: #REQ-UNISIG-SUB026-007167#REF#
realised by: #REQ-UNISIG-SUB026-007575#REF#

#REQ-UNISIG-SUB026-007055#REF# 3.13.2.3.7.7 #REQ-UNISIG-SUB026-002571#REF#
In order to adapt the train behaviour under reduced adhesion conditions, it shall be possible by means of National Values to limit to a maximum
value the speed dependent deceleration for the emergency brake. Three values shall be applicable for a given combination of the brake position
and of the type of brakes:
b) the second value shall be used for “Passenger train in P” without special/additional brakes independent from wheel/rail adhesion;
realised by: #REQ-UNISIG-SUB026-007167#REF#
realised by: #REQ-UNISIG-SUB026-007576#REF#

#REQ-UNISIG-SUB026-007056#REF# 3.13.2.3.7.7 #REQ-UNISIG-SUB026-002571#REF#
In order to adapt the train behaviour under reduced adhesion conditions, it shall be possible by means of National Values to limit to a maximum
value the speed dependent deceleration for the emergency brake. Three values shall be applicable for a given combination of the brake position
and of the type of brakes:
c) the third value shall be used for “Freight train in P” or “Freight train in G”.
realised by: #REQ-UNISIG-SUB026-007167#REF#
realised by: #REQ-UNISIG-SUB026-007577#REF#

#REQ-UNISIG-SUB026-007057#REF# 3.13.2.3.7.8
It shall be possible by means of a National Value to specify a release speed.
realised by: #REQ-DESIGN-CR-0576#REF#
realised by: #REQ-UNISIG-SUB026-3234#REF#

#REQ-UNISIG-SUB026-008090#REF# 3.13.2.3.7.9
It shall be possible by means of a National Value to inhibit the compensation of the speed measurement inaccuracy.
realised by: #REQ-UNISIG-SUB026-002059#REF#
realised by: #REQ-UNISIG-SUB026-007305#REF#
realised by: #REQ-UNISIG-SUB026-007364:01#REF#
realised by: #REQ-UNISIG-SUB026-007370#REF#
realised by: #REQ-UNISIG-SUB026-007387:01#REF#
realised by: #REQ-UNISIG-SUB026-007399:02#REF#
realised by: #REQ-UNISIG-SUB026-007413:01#REF#
realised by: #REQ-UNISIG-SUB026-008093#REF#

#REQ-UNISIG-SUB026-007058#REF# 3.13.2.3.7.10
It shall be possible by means of National Values to define integrated correction factors, namely Kv_int(V), Kr_int(l) and Kt_int. The integrated
correction factors only apply to the on-board equipment when the conversion model is used.
realised by: #REQ-UNISIG-SUB026-007162#REF#
realised by: #REQ-UNISIG-SUB026-002809#REF#
realised by: #REQ-UNISIG-SUB026-007587#REF#
realised by: #REQ-UNISIG-SUB026-007586#REF#
realised by: #REQ-UNISIG-SUB026-007588#REF#
realised by: #REQ-UNISIG-SUB026-007582#REF#
realised by: #REQ-UNISIG-SUB026-007580#REF#
realised by: #REQ-UNISIG-SUB026-007583#REF#

#REQ-UNISIG-SUB026-007060#REF# 3.13.2.3.7.11.1
It shall be possible to define up to five steps for Kv_int(V).
#TEST-VAL-SUB026-5619#REF# FCT Kv_int with 1/5 steps P203 - valid packet structure
#TEST-VAL-SUB026-5621#REF# FCT Kv_int with 6 steps P203 - invalid packet structure

#REQ-UNISIG-SUB026-007067#REF# 3.13.2.3.7.11.3
It shall be possible to define up to 2 sets of Kv_int with separate speed limits V1, V2, .. for each set. The sets of Kv_int relate to the
following train types:
1)  Freight trains
2)  Conventional passenger trains
#TEST-VAL-SUB026-5621#REF# FCT 3 Kv_int sets P203 - invalid packet structure
#TEST-VAL-SUB026-5619#REF# FCT 0, 1, 2 Kv_int sets P203 - valid packet structure

#REQ-UNISIG-SUB026-007070#REF# 3.13.2.3.7.11.4
The set of Kv_int for conventional passenger trains shall be divided into two sub sets Kv_int_x_a and Kv_int_x_b, with identical speed limits
V1, V2, ....
realised by: #REQ-UNISIG-SUB026-007572:03#REF#
realised by: #REQ-UNISIG-SUB026-3347:01#REF#
realised by: #REQ-UNISIG-SUB026-007582#REF#

#REQ-UNISIG-SUB026-007071#REF# 3.13.2.3.7.11.5
Subset Kv_int_x_a shall be applicable for maximum emergency brake deceleration lower or equal to a deceleration limit, defined as a National
Value.
realised by: #REQ-UNISIG-SUB026-002787#REF#

#REQ-UNISIG-SUB026-007072#REF# 3.13.2.3.7.11.6
Subset Kv_int_x_b shall be applicable for maximum emergency brake deceleration greater or equal to a deceleration limit, defined as a National
Value.
realised by: #REQ-UNISIG-SUB026-002787#REF#

#REQ-UNISIG-SUB026-007074#REF# 3.13.2.3.7.12.1
It shall be possible to define up to five steps for Kr_int(l).
#TEST-VAL-SUB026-5619#REF# FCT Kr_int with 1/5 steps P203 - valid packet structure
#TEST-VAL-SUB026-5621#REF# FCT Kr_int with 6 steps P203 - invalid packet structure

#REQ-UNISIG-SUB026-007081#REF# 3.13.2.3.7.13
The last step of the Kv_int(V) and Kr_int(l) shall by definition be considered as open ended, i.e. it has no upper speed and train length limit,
respectively.
#ANALYSE-VALUNISIG-4410#REF# FCT The interpretation of the last step is ensured by the implementation of the appropriated BAS class. Verification takes place via BAS module test.

#REQ-UNISIG-SUB026-007082#REF# 3.13.2.3.7.14
The correction factor for brake build up time (Kt_int) shall be a single parameter.
realised by: #REQ-UNISIG-SUB026-002809#REF#
realised by: #REQ-UNISIG-SUB026-007572:03#REF#
realised by: #REQ-UNISIG-SUB026-3347:01#REF#
realised by: #REQ-UNISIG-SUB026-007588#REF#

#REQ-UNISIG-SUB026-007088:01#REF# 3.13.3.2.1 #REQ-UNISIG-SUB026-006929#REF#
The conversion models shall be used by the on-board equipment if the brake percentage is acquired as part of Train Data, and if the maximum
train speed, the brake percentage and the train length are all within the following validity limits of the conversion models:
a)	0 ≤ V ≤ 200, where V is the maximum train speed in km/h
b)	30 ≤ λ ≤ 250, where λ is the brake percentage in %
c)	0 ≤ L ≤ Lmax, where L is the train length in m and where Lmax = 900 m if the brake position is “Passenger train in P” or Lmax = 1500 m
if the brake position is “Freight train in P” or “Freight train in G”
TEST APPROACH:
The following aspects have been identified:
1) dependency on brake position
1.1) Passenger train in P
1.2) Freight train in G
1.3) Freight train in P
2) dependency on brake percentage
3) dependency on train length
4) dependency on max train speed
#TEST-VAL-SUB026-4F62#REF# BVA 1.1 Selection of conversion brake model based on train data: L_TRAIN; Brake position Passenger train in P
#TEST-VAL-SUB026-3B66#REF# BVA 1.2 Selection of conversion brake model based on train data: L_TRAIN; Brake position Freight train in G
#TEST-VAL-SUB026-3B65#REF# BVA 1.3 Selection of conversion brake model based on train data: L_TRAIN; Brake position Freight train in P
#TEST-VAL-SUB026-4F61#REF# BVA 2 Selection of conversion brake model based on train data: M_BRAKECAPACITY
#TEST-VAL-SUB026-4F60#REF# BVA 3 Selection of conversion brake model based on train data: V_MAX_TRAIN

#REQ-UNISIG-SUB026-007093#REF# 3.13.3.2.2 #REQ-UNISIG-SUB026-006929#REF#
For trains not fitting into at least one of those validity limits, it is still possible to acquire the brake percentage as Train Data, but the
conversion models are not applicable, which means that braking models (i.e. pre-programmed deceleration profiles and brake build up times) shall
be used by the speed and distance monitoring function.
realised by: #REQ-UNISIG-SUB026-008062:01#REF#

#REQ-UNISIG-SUB026-008062:01#REF# 3.13.3.2.2 #REQ-SRS-004372#REF#
#REQ-UNISIG-SUB026-007093#REF#
The entered values for	"operational train category (includes cant deficiency and train category)", "brake capacity",
"train length", and "max train speed" shall be compared with the parameterized brake models.
∙	For the selection of a brake model the entered value shall be greater or equal to the lower limit and less or equal to the upper limit
(l <= x <= h).
∙	If a parameterized brake model is available for these values, it shall be used as preprogrammed brake model.
∙	If more than one brake model is available the first preprogrammed model found shall be used.
∙	If no parameterized brake model is available for these values, they shall be compared against the parameterized limits for the validity
of the conversion model. If they are inside the limits, the conversion model shall be used.
∙	If neither a preprogrammed brake model nor the conversion model is available for the entered values, they shall be rejected.
TEST APPROACH:
Following aspects have been identified:
1) train data input which agrees with parameterized brake model leads to the use of the pre-programmed brake model (bullet 1 and 2)
2) train data input which agrees with more than one parameterized brake model leads to the use of one of the fitting pre-programmed brake models
(bullet 3)
3) train data input which does not agree with any parameterized brake model but with the limits for the conversional brake model leads to the
use of the conversion model (bullet 4)
4) train data input which neither agrees with any parameterized brake model nor the conversional brake model limits must be rejected (bullet 5) 
#TEST-VAL-SUB026-4F96#REF# FCT 1, 3 Parametrized brake model limits
#TEST-VAL-SUB026-4F93#REF# FCT 2, 4 Brake model selection

#REQ-UNISIG-SUB026-007122#REF# 3.13.4.1.2
The default gradient for TSR shall be compensated in value according to the rotating mass as defined in 3.13.4.3.
realised by: #REQ-UNISIG-SUB026-007123#REF#
realised by: #REQ-UNISIG-SUB026-002706#REF#

#REQ-UNISIG-SUB026-007123#REF# 3.13.4.1.3 #REQ-UNISIG-SUB026-3645:01#REF#
#REQ-UNISIG-SUB026-007122#REF#
For all locations not covered by the gradient profile, the on-board shall consider the gradient value as:
a)	the default gradient for TSR, if available and if the concerned target is due to a TSR
b)	zero, for other cases.
#ANALYSE-VALUNISIG-4411#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3748#REF# FCT a) default gradient for TSR handling SR/FS/L2
#TEST-VAL-SUB026-3768#REF# FCT b) gradient value zero used if no gradient information is available SR
#TEST-VAL-SUB026-3769#REF# EET error expectation gradient value zero used if no gradient information is available UN

#REQ-UNISIG-SUB026-002696#REF# 3.13.4.2.1
Assuming that a fictive train front end would be at any location between the current (actual) train front end location and the SvL, the
acceleration due to the gradient shall be determined using the lowest (taking the sign into account) gradient value given by the gradient
profile between the location of the fictive train front end and the location of the fictive train rear end (see Figure 35).
realised by: #REQ-UNISIG-SUB026-007127#REF#

#REQ-UNISIG-SUB026-007127#REF# 3.13.4.2.1 #REQ-UNISIG-SUB026-002696#REF#
Assuming that a fictive train front end would be at any location between the current (actual) train front end location and the SvL, the
acceleration due to the gradient shall be determined using the lowest (taking the sign into account) gradient value given by the gradient
profile between the location of the fictive train front end and the location of the fictive train rear end (see Figure 35).

Clarification:
The profile used for supervision shall be computed by using the safe coordinate value of the start location and the maximum of the safe length
and the nominal length of each element.
#ANALYSE-VALUNISIG-4412#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-002700#REF# 3.13.4.3.1
The influence of gradients shall be compensated for the rotating mass of the train (see Figure 35).
realised by: #REQ-UNISIG-SUB026-007133#REF#

#REQ-UNISIG-SUB026-002706#REF# 3.13.4.3.2 #REQ-UNISIG-SUB026-007122#REF#
#REQ-UNISIG-SUB026-007974#REF#
#REQ-UNISIG-SUB026-007975#REF#
The following formulas shall be used:
a)	If M_rotating_nom is unknown:
  Uphill: A_gradient = g * grad / (1000+10*M_rotating_max)
  Downhill: A_gradient = g * grad / (1000+10*M_rotating_min)
  Uphill: A_gradient = g * grad / (1000+10*M_rotating_nom)
  Downhill: A_gradient = g * grad / (1000+10*M_rotating_nom)
realised by: #REQ-UNISIG-SUB026-007133#REF#

#REQ-UNISIG-SUB026-007133#REF# to.3.13.4.3.2 #REQ-UNISIG-SUB026-002700#REF#
#REQ-UNISIG-SUB026-002706#REF#
The influence of gradients shall be compensated for the rotating mass of the train (see Figure 35).
The following formulas shall be used:
a)	If M_rotating_nom is unknown:
-	Uphill: A_gradient = g * grad / (1000+10*M_rotating_max)
-	Downhill: A_gradient = g * grad / (1000+10*M_rotating_min)
b)	If M_rotating_nom is known:
-	Uphill: A_gradient = g * grad / (1000+10*M_rotating_nom)
-	Downhill: A_gradient = g * grad / (1000+10*M_rotating_nom)

Legend:
A_gradient = acceleration/deceleration due to gradient
g = 9.81 m/s2 - acceleration of gravity in m/s2
grad = gradient values in ‰ (positive = uphill)
M_rotating_nom = nominal rotating mass (part of train data) as a percentage of the total train weight
M_rotating_max = maximum possible rotating mass (see A.3.1) as a percentage of the total train weight
M_rotating_min = minimum possible rotating mass (see A.3.1) as a percentage of the total train weight

Clarification:
The formulas are given for the case, that a gradient of 1‰ is coded as integer 1,
M_rotating_max of 15 % is coded as integer 15 and A_gradient gives a deceleration (with positive values specifying a deceleration).
In the case that a gradient of 1 ‰ is coded as 0.001, M_rotating_max of 15 % is coded as 0.15 and A_gradient gives an acceleration (with
positive values specifying an acceleration), the formulas have to be modified as follows:
  A_gradient = -g * grad / (1+M_rotating_max)	for Uphill with unknown M_rotating_nom
  A_gradient = -g * grad / (1+M_rotating_min)	for Downhill with unknown M_rotating_nom
  A_gradient = -g * grad / (1+M_rotating_nom)  for known M_rotating_nom
TEST APPROACH:
The following aspects have been identified:
1) Dependency on M_rotating_nom
1.1) M_rotating_nom known
1.2) M_rotating_nom unknown
2) Dependency on gradient
#ANALYSE-VALUNISIG-4413#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F77#REF# FCT 1.1, 1.2 Value range for nominal rotating mass: min, max, unknown
#TEST-VAL-SUB026-5650#REF# FCT 2 Dependency of A_safe, A_expected and A_normal_service on gradient

#REQ-UNISIG-SUB026-002723:01#REF# 3.13.5.1
As long as it uses a track condition profile given by trackside, the on-board shall consider locations without special brake contribution over a
distance going from the start location of the profile to the foot of the deceleration curve (EBD, SBD or GUI, see sections ‎3.13.8.3, ‎3.13.8.4
and ‎3.13.8.5).
realised by: #REQ-UNISIG-SUB026-007138:01#REF#

#REQ-UNISIG-SUB026-007138:01#REF# 3.13.5.1 #REQ-UNISIG-SUB026-002723:01#REF#
As long as it uses a track condition profile given by trackside, the on-board shall consider locations without special brake contribution over a
distance going from the start location of the profile to the foot of the deceleration curve (EBD, SBD or GUI, see sections ‎3.13.8.3, ‎3.13.8.4
and ‎3.13.8.5).

Clarification:
The profile used for supervision shall be computed by using the safe coordinate value of the start location and the maximum of the safe length
and the nominal length of each element.
TEST APPROACH:
Dependency on special brakes not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#. 
#ANALYSE-VALUNISIG-7644#REF# FCT The feature Special Brakes is not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#

#REQ-UNISIG-SUB026-010331#REF# 3.13.5.2
If the status of a special brake is “not active”, all locations shall be considered without the contribution of this special brake.
#ANALYSE-VALUNISIG-7645#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-002725#REF# 3.13.5.3
From the adhesion profile given by trackside, the on-board shall consider locations with reduced adhesion conditions over a distance going from
the start location of the profile to the location derived by adding the train length to the end location of the profile.
realised by: #REQ-UNISIG-SUB026-007139#REF#

#REQ-UNISIG-SUB026-007139#REF# 3.13.5.3 #REQ-UNISIG-SUB026-002725#REF#
From the adhesion profile given by trackside, the on-board shall consider locations with reduced adhesion conditions over a distance going from
the start location of the profile to the location derived by adding the train length to the end location of the profile.

Clarification:
The profile used for supervision shall be computed by using the safe coordinate value of the start location and the maximum of the safe length
and the nominal length of each element.
TEST APPROACH:
The following aspects have been identified:
1) Evaluation of slippery area from track side and slippery input from driver 
2) Evaluation of slippery area from track side based on safe coordinate value 
#ANALYSE-VALUNISIG-4414#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5648#REF# FCT 1 Evaluation of slippery area from track side and slippery input from driver
#TEST-VAL-SUB026-5649#REF# FCT 2 Evaluation of slippery area from track side based on safe coordinate value

#REQ-UNISIG-SUB026-007140#REF# 3.13.5.4
When slippery rail is selected by the driver, all locations shall be considered with reduced adhesion conditions.
#ANALYSE-VALUNISIG-4415#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5648#REF# FCT basic function Evaluation of slippery area from track side and slippery input from driver

#REQ-UNISIG-SUB026-2024#REF# 3.13.5.5
The speed and distance monitoring shall use, as resulting reduced adhesion conditions, the most restrictive value of the adhesion conditions
selected by the driver and the adhesion conditions calculated from the trackside profile.
TEST APPROACH:
The following aspects have been identified:
1) adhesion factor changed by driver and track 
2) adhesion factor changed by track and driver 
#TEST-VAL-SUB026-4671#REF# FCT 1 adhesion factor changed by driver and track
#TEST-VAL-SUB026-4672#REF# FCT 2 adhesion factor changed by track and driver

#REQ-UNISIG-SUB026-007160#REF# 3.13.6.2.1.3
A_safe(V,d) shall be equal to:
For locations with normal adhesion conditions:
A_safe(V,d) = A_brake_safe(V,d) + A_gradient(d)
For locations with reduced adhesion conditions:
A_safe(V,d) = MIN(A_brake_safe(V,d) , A_MAXREDADH) + A_gradient(d)
TEST APPROACH:
The following aspects have been identified:
1) dependency on A_NVMAXREDADH1
2) dependency on A_NVMAXREDADH2
3) dependency on A_NVMAXREDADH3
4) dependency on A_gradient
5) dependency on M_ADHESION
#ANALYSE-VALUNISIG-4416#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5631#REF# FCT 1 Variable test A_NVMAXREDADH1
#TEST-VAL-SUB026-5632#REF# FCT 2 Variable test A_NVMAXREDADH2
#TEST-VAL-SUB026-5633#REF# FCT 3 Variable test A_NVMAXREDADH3
#TEST-VAL-SUB026-5650#REF# FCT 4 Dependency of A_safe, A_expected and A_normal_service on gradient
#TEST-VAL-SUB026-5464#REF# FCT 5 SB/EB dependency on adhesion factor

#REQ-UNISIG-SUB026-007162#REF# 3.13.6.2.1.4 #REQ-UNISIG-SUB026-006997#REF#
#REQ-UNISIG-SUB026-007052#REF#
#REQ-UNISIG-SUB026-007058#REF#
A_brake_safe(V,d) shall be the safe emergency brake deceleration. A_brake_safe(V,d) shall be equal to:
If the speed dependent deceleration model(s) for the emergency brake are acquired as part of Train Data:
A_brake_safe(V,d) = Kdry_rst(V, M_NVEBCL) * (Kwet_rst(V) + M_NVAVADH *(1- Kwet_rst(V))) * A_brake_emergency(V,d)
If the conversion model is used:
A_brake_safe(V) = Kv_int(V) * Kr_int(L_TRAIN) * A_brake_emergency(V)
TEST APPROACH:
The following aspects have been identified:
1) conversion model:
1.1) dependency on A_NVP12, A_NVP23/Kv_int
1.2) dependency on L_NVKRINT/Kr_int
1.3) dependency on M_NVKRINT/Kr_int
1.4) dependency on M_NVKVINT/Kv_int
1.5) dependency on V_NVKVINT/Kv_int
1.6) dependency on Q_NVKVINTSET/Kv_int
2) preprogrammed brake model:
2.1)  dependency on M_NVAVADH
2.2) dependency on M_NVEBCL/Kdry_rst
#ANALYSE-VALUNISIG-4417#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5637#REF# FCT 1.1 Variable test A_NVP12, A_NVP23
#TEST-VAL-SUB026-5640#REF# FCT 1.2 Variable test L_NVKRINT
#TEST-VAL-SUB026-5641#REF# FCT 1.3 Variable test M_NVKRINT
#TEST-VAL-SUB026-5639#REF# FCT 1.4 Variable test M_NVKVINT
#TEST-VAL-SUB026-5638#REF# FCT 1.5 Variable test V_NVKVINT
#TEST-VAL-SUB026-5636#REF# FCT 1.6 Variable test Q_NVKVINTSET
#TEST-VAL-SUB026-5634#REF# FCT 2.1 Variable test M_NVAVADH
#TEST-VAL-SUB026-5635#REF# FCT 2.2 Variable test M_NVEBCL

#REQ-UNISIG-SUB026-002768:01#REF# 3.13.6.2.1.5
A_brake_emergency(V,d) shall be the emergency brake deceleration as a function of the speed, of the locations with change of special brake(s)
contribution encountered between the train front and the foot of the EBD curve.  A_brake_emergency(V,d) shall be equal to:
A_brake_emergency1(V) when destfront ≤ d ≤ d1
A_brake_emergency2(V) when d1 < d ≤ d2
A_brake_emergency3(V) when d2 < d ≤ d3
....
Where
d1, d2, d3,... are the locations with change of special brake(s) contribution
A_brake_emergencyx(V) is equal to the emergency brake model, A_brake_emergency, applicable for the concerned combination of brake.

#DSC-UNISIG-SUB026-002777#REF#

Figure 36: Influence of track conditions on A_brake_emergency(V,d)
realised by: #REQ-UNISIG-SUB026-007164:01#REF#

#REQ-UNISIG-SUB026-007164:01#REF# 3.13.6.2.1.5 #REQ-UNISIG-SUB026-002768:01#REF#
A_brake_emergency(V,d) shall be the emergency brake deceleration as a function of the speed, of the locations with change of special brake(s)
contribution encountered between the train front and the foot of the EBD curve.  A_brake_emergency(V,d) shall be equal to:
A_brake_emergency1(V) when destfront ≤ d ≤ d1
A_brake_emergency2(V) when d1 < d ≤ d2
A_brake_emergency3(V) when d2 < d ≤ d3
....
Where
d1, d2, d3,... are the locations with change of special brake(s) contribution
A_brake_emergencyx(V) is equal to the emergency brake model, A_brake_emergency, applicable for the concerned combination of brake.


Figure 36: Influence of track conditions on A_brake_emergency(V,d)
TEST APPROACH:
The feature Special Brakes is not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#
#ANALYSE-VALUNISIG-5351#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007167#REF# 3.13.6.2.1.6 #REQ-UNISIG-SUB026-007054#REF#
#REQ-UNISIG-SUB026-007055#REF#
#REQ-UNISIG-SUB026-007056#REF#
A_MAXREDADH shall be the deceleration value, out of the three related National Values, applicable for this train according to:
a)	its brake position
b)	whether special/additional brakes independent from wheel/rail adhesion are active and it is allowed to take into account their
contribution to the emergency braking effort.
TEST APPROACH:
The feature Special Brakes is not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#
#ANALYSE-VALUNISIG-4419#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5632#REF# FCT Passenger train in P (no special brakes) Variable test A_NVMAXREDADH2
#TEST-VAL-SUB026-5631#REF# FCT Passenger train in P (with special brakes) Variable test A_NVMAXREDADH1
#TEST-VAL-SUB026-5633#REF# FCT freight train in G Variable test A_NVMAXREDADH3
#TEST-VAL-SUB026-5662#REF# FCT freight train in P Selection of NV A_MAXREDADH for Freight train in P

#REQ-UNISIG-SUB026-007171#REF# 3.13.6.2.1.8
Kv_int(V) shall be the integrated correction factor applicable for the train, selected according to the brake position.
#ANALYSE-VALUNISIG-4420#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5636#REF# FCT basic function Variable test Q_NVKVINTSET

#REQ-UNISIG-SUB026-002787#REF# 3.13.6.2.1.8.1 #REQ-UNISIG-SUB026-007071#REF#
#REQ-UNISIG-SUB026-007072#REF#
If the brake position is “Passenger train in P”, the set of Kv_int shall be calculated as a function of the maximum emergency brake deceleration
(A_ebmax) in the following way (see also figure 10):
Kv_int_x = Kv_int_x_a		when		A_ebmax ≤ A_P12.
Kv_int_x = Kv_int_x_b		when		A_ebmax ≥ A_P23.
Kv_int_x = Kv_int_x_a + (A_ebmax - A_P12)/(A_P23 - A_P12) * (Kv_int_x_b - Kv_int_x_a)	when		A_P12 < A_ebmax < A_P23.”

#DSC-UNISIG-SUB026-002792#REF#

Figure 37: Kv_int structure for conventional passenger trains
realised by: #REQ-UNISIG-SUB026-007172#REF#

#REQ-UNISIG-SUB026-007172#REF# 3.13.6.2.1.8.1 #REQ-UNISIG-SUB026-002787#REF#
If the brake position is “Passenger train in P”, the set of Kv_int shall be calculated as a function of the maximum emergency brake deceleration
(A_ebmax) in the following way (see also figure 10):
Kv_int_x = Kv_int_x_a	when	A_ebmax ≤ A_P12
Kv_int_x = Kv_int_x_b	when	A_ebmax ≥ A_P23
Kv_int_x = Kv_int_x_a + (A_ebmax - A_P12)/(A_P23 - A_P12) * (Kv_int_x_b - Kv_int_x_a)
when A_P12 < A_ebmax < A_P23.

Figure 37: Kv_int structure for conventional passenger trains
#ANALYSE-VALUNISIG-4421#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007177#REF# 3.13.6.2.1.8.2
The maximum EB deceleration A_ebmax shall be the maximum of A_brake_emergency between 0 km/h and the maximum speed of the train.
#ANALYSE-VALUNISIG-4422#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-002809#REF# 3.13.6.2.2.3 #REQ-UNISIG-SUB026-007058#REF#
#REQ-UNISIG-SUB026-007082#REF#
The safe brake build up time T_be shall be equal to:
If values of T_brake_emergency are acquired as part of Train Data:
T_be = T_brake_emergency, with T_brake_emergency corresponding to the combination of special brakes currently in use
If the conversion model is used:
T_be = Kt_int * T_brake_emergency
realised by: #REQ-UNISIG-SUB026-007186#REF#

#REQ-UNISIG-SUB026-007186#REF# 3.13.6.2.2.3 #REQ-UNISIG-SUB026-002809#REF#
The safe brake build up time T_be shall be equal to:
-	If values of T_brake_emergency are acquired as part of Train Data:
T_be = T_brake_emergency, with T_brake_emergency corresponding to the combination of special brakes currently in use
-	If the conversion model is used:
T_be = Kt_int * T_brake_emergency

Clarification:
Because there are two values for T_brake_emergency (T_brake_emergency_cm0 and T_brake_emergency_cmt, see 3.13.3.4.4.1), two values for T_be are
calculated (T_be_cm0 and T_be_cmt).
TEST APPROACH:
The following aspects have been identified:
1) conversion model dependency on M_NVKTINT
2) pre-programmed model no dependency on M_NVKTINT
#ANALYSE-VALUNISIG-4423#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5643#REF# FCT 1 Variable test M_NVKTINT
#TEST-VAL-SUB026-5685#REF# FCT 2 Pre-programmed brake model and M_NVKTINT

#REQ-UNISIG-SUB026-007197#REF# 3.13.6.3.1.3
A_expected(V,d) shall be equal to:
A_expected(V,d) = A_brake_service(V,d) +A_gradient(d)
TEST APPROACH:
The following aspects have been identified:
1) dependency on A_gradient
#ANALYSE-VALUNISIG-4424#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5650#REF# FCT 1 Dependency of A_safe, A_expected and A_normal_service on gradient

#REQ-UNISIG-SUB026-007199:01#REF# 3.13.6.3.1.4
A_brake_service(V,d) shall be the full deceleration of the service brake as a function of the speed, of the locations with change of special
brake(s) contribution encountered between the train front and the foot of the SBD curve. A_brake_service(V,d) shall be equal to:
A_brake_service1(V) when destfront ≤ d ≤ d1
A_brake_service2(V) when d1 < d ≤ d2
A_brake_service3(V) when d2 < d ≤ d3
....
Where
d1, d2, d3,... are the locations with change of special brake(s) contribution
A_brake_servicex(V) is equal to the full service brake model, A_brake_service, applicable for the concerned combination of brake.
TEST APPROACH:
The feature Special Brakes is not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#
#ANALYSE-VALUNISIG-4425#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-002849#REF# 3.13.6.3.2.4
The expected brake build up time T_bs shall be equal to the brake build up time of the full service brake:
T_bs = T_brake_service, with T_brake_service corresponding to the combination of special brakes currently in use
realised by: #REQ-UNISIG-SUB026-007207#REF#

#REQ-UNISIG-SUB026-007207#REF# to.3.13.6.3.2.4 #REQ-UNISIG-SUB026-002849#REF#
The expected brake build up time T_bs shall be equal to the brake build up time of the full service brake:
T_bs = T_brake_service, with T_brake_service corresponding to the combination of special brakes currently in use

Clarification:
Because there are two values for T_brake_service (T_brake_service_cm0 and T_brake_service_cmt, see 3.13.3.4.4.1), two values for T_bs are
calculated (T_bs_cm0 and T_bs_cmt).
TEST APPROACH:
The following aspects have been identified:
1) Pre-programmed brake model 
2) Conversion model
#ANALYSE-VALUNISIG-4426#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F87#REF# FCT 1 Dependency T_brake_service ->T_bs ->T_indication : 0.8*T_bs > 5s
#TEST-VAL-SUB026-8136#REF# FCT 2 Dependency T_brake_service ->T_bs ->T_indication : 0.8*T_bs > 5s (Conversion model)

#REQ-UNISIG-SUB026-007219#REF# 3.13.6.4.3 #REQ-UNISIG-SUB026-007012#REF#
#REQ-UNISIG-SUB026-007013#REF#
The normal service brake deceleration shall be equal to:
For positive gradient values (uphill):
A_normal_service(V,d) = A_brake_normal_service(V,d) + A_gradient(d) - Kn+(V)*grad
For negative gradient values (downhill):
A_normal_service(V,d) = A_brake_normal_service(V,d) + A_gradient(d) - Kn-(V)*grad
Where
grad = gradient values in ‰ (positive = uphill)
grad = gradient values in ‰ means the absolut value
for instance:
G_A=7‰ => grad=0,007
TEST APPROACH:
The following aspects have been identified:
1) dependency on A_gradient
2) dependency on Kn
#ANALYSE-VALUNISIG-4427#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5650#REF# FCT 1 Dependency of A_safe, A_expected and A_normal_service on gradient
#TEST-VAL-SUB026-4F86#REF# FCT 2 Dependency of GUI on Kn+/-

#REQ-UNISIG-SUB026-007221:01#REF# 3.13.6.4.4
A_brake_normal_service(V,d) shall be the normal deceleration of the service brake as a function of the speed, of the locations with change of
special brake(s) contribution encountered between the train front and the foot of the GUI curve.
A_brake_normal_service(V,d) shall be equal to:
A_brake_normal_service1(V) when destfront ≤ d ≤ d1
A_brake_normal_service2(V) when d1 < d ≤ d2
A_brake_normal_service3(V) when d2 < d ≤ d3
....
Where
d1, d2, d3,... are the locations with change of special brake(s) contribution
A_brake_normal_servicex(V) is equal to the normal service brake model applicable for the concerned combination of brake position and of the
value of A_brake_service(V=0) between dx-1 and dx (see 3.13.2.2.3.1.9 and 3.13.2.2.3.1.10).
TEST APPROACH:
The feature Special Brakes is not part of R8.0 refer #REQ-SRS-004416#REF#/#REQ-SWAnf-NotRealizedFeatures-008113#REF#
#ANALYSE-VALUNISIG-4428#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-002886#REF# 3.13.7.2
The Most Restrictive Speed Profile shall be computed from all speed restrictions (see 3.13.2.2.13 & 3.13.2.3.2) by selecting the most
restrictive parts of each element, some elements being compensated by the train length if requested by trackside (see 3.11.3.1.3 for SSP,
3.11.4.6 for ASP and 3.11.5.3 for TSR).

#DSC-UNISIG-SUB026-002888#REF#

Figure 39: Most Restrictive Speed Profile selection
realised by: #REQ-UNISIG-SUB026-007225#REF#

#REQ-UNISIG-SUB026-007225#REF# 3.13.7.2 #REQ-UNISIG-SUB026-002886#REF#
#REQ-UNISIG-SUB026-007280#REF#
The Most Restrictive Speed Profile shall be computed from all speed restrictions (see 3.13.2.2.13 & 3.13.2.3.2) by selecting the most
restrictive parts of each element, some elements being compensated by the train length if requested by trackside (see 3.11.3.1.3 for SSP,
3.11.4.6 for ASP and 3.11.5.3 for TSR).

Clarification:
This includes the speed restriction due to an LOA.


Figure 39: Most Restrictive Speed Profile selection
this clarification realize REQ-UNISIG-SUB026-007280 (3.13.9.3.7)
TEST APPROACH:
The following aspects have been identified:
The computation of the MRSP based on:
1) ISSP
2) ASP
3) TSR
4) Max train speed
5) Signalling related speed restriction
6) Mode related speed restriction
7) STM max speed
8) STM system speed
9) LX speed
10) Override speed
11) PBD speed
12) LOA speed
#ANALYSE-VALUNISIG-4429#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3115#REF# FCT 1, 2, 3, 6 MRSP calculation
#TEST-VAL-SUB026-5868#REF# FCT 4 Variable test V_NVLIMSUPERV
#TEST-VAL-SUB026-3125#REF# FCT 5 New V_MAIN overrides old one
#TEST-VAL-SUB026-4474#REF# FCT 7, 8 FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-7644#REF# FCT 9 LX information overwritten by new received LX with same ID
#TEST-VAL-SUB026-5961#REF# FCT 10 Speed supervision based on V_TSR, V_NVSTFF and V_NVSUPOVTRP
#TEST-VAL-SUB026-3A65#REF# FCT 11 PBD Information accepted in mode UN via RBC/L0[2] and supervised in mode FS
#TEST-VAL-SUB026-5231#REF# FCT 12 Ceiling supervision limits based on V_LoA

#REQ-UNISIG-SUB026-007846#REF# to.3.13.7.2
The MRSP used to supervise the locations corresponding to a speed increase of the MRSP shall be computed by using the safe coordinate values of
the start and end locations of each element.
#ANALYSE-VALUNISIG-4430#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5663#REF# FCT basic function Save supervision of MRSP
#TEST-VAL-SUB026-3639#REF# EET error expectation TSR in L1(Balise)/train orientation A, reset of confidence interval

#REQ-UNISIG-SUB026-007847#REF# to.3.13.7.2
The MRSP used to determine the supervised targets, the indication location and the preindication location and to be transmitted to the DMI shall
be computed by using the safe coordinate value of the start location and the maximum of the safe length and the nominal length of each element.
#ANALYSE-VALUNISIG-4431#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007227#REF# 3.13.7.3
The Most Restrictive Speed Profile shall be recalculated when any of the elements it is built of is changed.
#ANALYSE-VALUNISIG-4432#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3115#REF# FCT basic function MRSP calculation
#TEST-VAL-SUB026-7603#REF# EET error expectation New STM system speed and distance and STM max speed replace any previously received value

#REQ-UNISIG-SUB026-008019#REF# to.3.13.8.1.3 #ANA-UNISIG-BrakingCurves-0001#REF#
If the deceleration value for a speed and distance indicates an acceleration instead of a deceleration, the value 0 shall be used instead.
Note: This is done to ensure that the speed of a deceleration curve never increases with increasing distance. To assure safe deceleration
curves, the locations with these deceleration values are protected through additional speed restrictions (see #REQ-UNISIG-SUB026-008018:01#REF#
added to 3.13.8.3).
#ANALYSE-VALUNISIG-4433#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5651#REF# FCT basic function Additional speed restriction OBU defined speed restriction due to GP, AP, NV which reduce the A_safe

#REQ-UNISIG-SUB026-007234#REF# 3.13.8.2.1
The on-board shall continuously supervise a list of targets, which may include the following types of target:
a)	the locations corresponding to a speed decrease of the MRSP (if any), which are in advance of the max safe front end of the train
b)	the Limit of Authority (LOA), if the target speed at the EOA/LOA is not equal to zero
c)	the End of Authority (EOA) and the Supervised Location (SvL), if the target speed at the EOA is equal to zero
d)	the location deduced from the maximum permitted distance to run in Staff Responsible, with a target speed zero
TEST APPROACH:
The following aspects have been identified:
The verification of the track input for BC module:
1) Speed decrease in the MRSP
1.1) ISSP
1.2) ASP
1.3) TSR
1.4) STM system speed and distance
1.5) STM max speed
1.6) PBD speed
1.7) LX 
2) End of MA
2.1) LoA
2.2) EoA
2.3) SvL
3) D_SR
#ANALYSE-VALUNISIG-4434#REF# FCT BC supervises the list of targets identified by other modules. Verification of this aspect takes place via BC module test.
#TEST-VAL-SUB026-5229#REF# FCT 1.1, 1.2, 1.3, 2.2, 2.3, 3 target supervision
#TEST-VAL-SUB026-4474#REF# FCT 1.4, 1.5 FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-7168#REF# FCT 1.6, 1.7 Supervision of PBD/LX target
#TEST-VAL-SUB026-7557#REF# FCT 2.1 Variable test V_LOA

#REQ-UNISIG-SUB026-007241#REF# 3.13.8.2.2
The list of supervised targets shall be re-evaluated when any of the elements it is built of is changed (e.g. new MA and/or track description
accepted on-board, EOA and/or SvL temporarily supervised at the start location of a mode profile, update of stored information in specific
situations (see sections A.3.4 and 4.10)).
TEST APPROACH:
The following aspects have been identified:
1) change of input information leads to changed output MRDT
#ANALYSE-VALUNISIG-4435#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5670#REF# FCT 1 MRDT change due to changed list of supervised targets

#REQ-UNISIG-SUB026-002914#REF# 3.13.8.2.3
A target corresponding to a speed decrease of the MRSP shall be removed from the list of supervised targets when the max safe front end of the
train has passed the target location.
realised by: #REQ-UNISIG-SUB026-007242#REF#

#REQ-UNISIG-SUB026-007242#REF# 3.13.8.2.3 #REQ-UNISIG-SUB026-002914#REF#
A target corresponding to a speed decrease of the MRSP shall be removed from the list of supervised targets when the max safe front end of the
train has passed the target location.

Clarification:
A target corresponding to a speed decrease of the MRSP shall be added to the list of supervised targets again when the max safe front end of the
train has not passed the target location any more (this conforms to A3.6.2.1).
TEST APPROACH:
The following aspects have been identified:
The verification of the track input for BC module:
1) handling of the target list
2) indication of the MRDT
3) A3.6.2.1
#ANALYSE-VALUNISIG-4436#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5229#REF# FCT 1 target supervision
#TEST-VAL-SUB026-3363#REF# FCT 2 Supervision with regards to the target location refers to max safe front end
#TEST-VAL-SUB026-3786#REF# FCT 3 Storage of TSR for backward movement Q_FRONT=0

#REQ-UNISIG-SUB026-007244:01#REF# 3.13.8.3.1
If a target belongs to the MRSP or is an LOA, the on-board shall calculate an EBD curve based on the safe deceleration A_safe(V,d), that crosses
the ceiling speed EBI supervision limit (see ‎3.13.9.2) at the target location, and that extends up to the location where the target speed is
reached (EBD foot).

#DSC-UNISIG-SUB026-002920#REF#

Figure 40: Calculation of the EBD curve with regards to MRSP or LOA target
#ANALYSE-VALUNISIG-4438#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007246#REF# 3.13.8.3.2
If a target is an SvL, the on-board shall calculate an Emergency Brake Deceleration (EBD) curve based on the safe deceleration A_safe(V,d) and
that reaches zero speed at the SvL.
#ANALYSE-VALUNISIG-4439#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007247#REF# 3.13.8.3.3
If a target is the location at the end of the maximum permitted distance to run in Staff Responsible, the on-board shall calculate an Emergency
Brake Deceleration (EBD) curve based on the safe deceleration A_safe(V,d) and that reaches zero speed at this staff responsible end location.

#DSC-UNISIG-SUB026-002926#REF#

Figure 41: Calculation of the EBD curve with regards to SvL or SR distance
#ANALYSE-VALUNISIG-4440#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5664#REF# FCT basic function Supervision of D_SR and V_NVSTFF

#REQ-UNISIG-SUB026-008018:01#REF# to.3.13.8.3 #ANA-UNISIG-BrakingCurves-0001#REF#
If the value for A_safe(V,d) for a part of an Emergency Brake Deceleration (EBD) curve indicates that braking is not possible, an additional
speed restriction shall be inserted from d_begin to d_end with the value v_low - dv_ebi where:
  d_begin is the beginning location of the area where braking is not possible,
  d_end is the end location of the area where braking is not possible,
  v_low is the lowest speed in this area where braking is not possible,
  dv_ebi is the difference between the permitted speed and the emergency brake intervention speed calculated using the inverse of the formula
from 3.13.9.2.3.
#ANALYSE-VALUNISIG-4437#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5658#REF# FCT basic function Section based evaluation (if brakeing is possible) of Emergency Brake Deceleration curve

#REQ-UNISIG-SUB026-007250#REF# 3.13.8.4.1
If a target is an EOA, the on-board shall calculate an Service Brake Deceleration (SBD) curve based on the expected deceleration A_expected(V,d)
and that reaches zero speed at this EOA location.

#DSC-UNISIG-SUB026-002932#REF#

Figure 42: Calculation of the SBD curve with regards to EOA
#ANALYSE-VALUNISIG-4441#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007254#REF# 3.13.8.5.2 #REQ-UNISIG-SUB026-007049#REF#
If the National Value does not inhibit them, the on-board shall calculate a guidance curve (GUI) for each supervised target, based on the normal
service brake deceleration A_normal_service(V,d). The foot of a GUI curve (i.e. the location where the GUI speed is equal to the target speed)
shall be:
a)	the target location, in case of EOA/SvL
b)	the location defined in 3.13.9.3.5.9, for others targets
#ANALYSE-VALUNISIG-4442#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5628#REF# FCT basic function Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007275#REF# 3.13.9.2.3
For dv_ebi, the following formula shall be applied:
when:



with

when:
see figure 44
#DSC-UNISIG-SUB026-002973#REF#

Figure 44: Definition of dV_ebi
realised by: #REQ-UNISIG-SUB026-007273#REF#

#REQ-UNISIG-SUB026-007273#REF# 3.13.9.2.3-1 #REQ-UNISIG-SUB026-007275#REF#
#REQ-UNISIG-SUB026-007274#REF#
#REQ-UNISIG-SUB026-007959#REF#
#REQ-UNISIG-SUB026-007960#REF#
#REQ-UNISIG-SUB026-007961#REF#
#REQ-UNISIG-SUB026-007962#REF#
For dv_ebi, the following formula shall be applied:
when:



with


when:




Figure 44: Definition of dV_ebi

dV_ebi_min, dV_ebi_max, V_ebi_min and V_ebi_max are defined as fixed values (See Appendix A.3.1)
TEST APPROACH:
The following aspects have been identified:
1) non-UNISIG values defined for dV_ebi_min, dV_ebi_max, V_ebi_min and V_ebi_max 
2) default UNISIG values defined for dV_ebi_min, dV_ebi_max, V_ebi_min and V_ebi_max 
#ANALYSE-VALUNISIG-4443#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F79#REF# FCT 1 Fixed values for CSM
#TEST-VAL-SUB026-5230#REF# FCT 2 Ceiling supervision limits based on MRSP

#REQ-UNISIG-SUB026-007274#REF# 3.13.9.2.4
dV_ebi_min, dV_ebi_max, V_ebi_min and V_ebi_max are defined as fixed values (See Appendix A.3.1)
realised by: #REQ-UNISIG-SUB026-007273#REF#

#REQ-UNISIG-SUB026-007278#REF# 3.13.9.2.5 #REQ-UNISIG-SUB026-007963#REF#
#REQ-UNISIG-SUB026-007964#REF#
#REQ-UNISIG-SUB026-007965#REF#
#REQ-UNISIG-SUB026-007966#REF#
For dV_sbi, the same formula as for dV_ebi shall apply, dV_sbi_min, dV_sbi_max, V_sbi_min and V_sbi_max being also defined as fixed values (See
Appendix A.3.1)
TEST APPROACH:
The following aspects have been identified:
1) non-UNISIG values defined for dV_sbi_min, dV_sbi_max, V_sbi_min and V_sbi_max 
2) default UNISIG values defined for dV_sbi_min, dV_sbi_max, V_sbi_min and V_sbi_max 
#ANALYSE-VALUNISIG-4444#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F79#REF# FCT 1 Fixed values for CSM
#TEST-VAL-SUB026-5230#REF# FCT 2 Ceiling supervision limits based on MRSP

#REQ-UNISIG-SUB026-007279#REF# 3.13.9.2.6 #REQ-UNISIG-SUB026-007967#REF#
#REQ-UNISIG-SUB026-007968#REF#
#REQ-UNISIG-SUB026-007969#REF#
#REQ-UNISIG-SUB026-007970#REF#
For dV_warning, the same formula as for dV_ebi shall apply, dV_warning_min, dV_warning_max, V_warning_min and V_warning_max being also defined
as fixed values (See Appendix A.3.1)
TEST APPROACH:
The following aspects have been identified:
1) non-UNISIG values defined for dV_warning_min, dV_warning_max, V_warning_min and V_warning_max 
2) default UNISIG values defined for dV_warning_min, dV_warning_max, V_warning_min and V_warning_max 
#ANALYSE-VALUNISIG-4445#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F79#REF# FCT 1 Fixed values for CSM
#TEST-VAL-SUB026-5231#REF# FCT 2 Ceiling supervision limits based on V_LoA

#REQ-UNISIG-SUB026-007280#REF# 3.13.9.2.7
For LOA, the same formulas shall apply, by substituting V_MRSP with V_LOA.
realised by: #REQ-UNISIG-SUB026-007225#REF#

#REQ-UNISIG-SUB026-007292#REF# 3.13.9.3.2.3
The traction time (T_Traction) shall be defined as follows:
a)	when the traction cut-off is implemented:
T_traction = MAX((T_traction_cut_off - (T_warning + T_bs2)) ; 0).
b)	when the traction cut-off is not implemented: T_traction = T_traction_cut_off
realised by: #REQ-UNISIG-SUB026-007295#REF#

#REQ-UNISIG-SUB026-007295#REF# 3.13.9.3.2.3 #REQ-UNISIG-SUB026-007292#REF#
The traction time (T_Traction) shall be defined as follows:
a)	when the traction cut-off is implemented:
T_traction = MAX((T_traction_cut_off - (T_warning + T_bs2)) ; 0).
b)	when the traction cut-off is not implemented:
T_traction = T_traction_cut_off
Clarification:
Because there are two values for T_bs2 (T_bs2_cm0 and T_bs2_cmt), two values for T_traction are calculated (T_traction_cm0 and T_traction_cmt).
#ANALYSE-VALUNISIG-4446#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5646#REF# FCT a Traction cut-off is implemented, dependency on T_traction
#TEST-VAL-SUB026-5647#REF# FCT b Traction cut-off is not implemented, dependency on T_traction

#REQ-UNISIG-SUB026-007299#REF# 3.13.9.3.2.6
The remaining time with no traction (T_berem) shall be equal to MAX(T_be - T_traction ; 0).
realised by: #REQ-UNISIG-SUB026-007300#REF#

#REQ-UNISIG-SUB026-007300#REF# 3.13.9.3.2.6 #REQ-UNISIG-SUB026-007299#REF#
The remaining time with no traction (T_berem) shall be equal to MAX(T_be - T_traction ; 0).

Clarification:
Because there are two values each for T_be and T_traction (T_be_cm0 and T_be_cmt, T_traction_cm0 and T_traction_cmt), two values for T_berem are
calculated (T_berem_cm0 and T_berem_cmt).
#ANALYSE-VALUNISIG-4447#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007302#REF# 3.13.9.3.2.8 #ANA-UNISIG-CR1124-0001#REF#
During T_traction, the estimated acceleration/deceleration (A_est1), which is measured at the moment when the calculation is made, shall be
taken into account.
UNISIG clarification: solution of UCR 1124, part 4 is to be taken over
realised by: #REQ-UNISIG-SUB026-007306#REF#

#REQ-UNISIG-SUB026-007306#REF# to.3.13.9.3.2.8 #REQ-UNISIG-SUB026-007302#REF#
#ANA-UNISIG-CR1124-0001#REF#
During T_traction, the estimated acceleration (A_est1)shall be the one measured at the moment when the calculation is made, but limited to
positive or null values.
UNISIG clarification: solution of UCR 1124, part 4 is to be taken over
=> new requirementreplaces the old origin
#ANALYSE-VALUNISIG-7665#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-8258#REF# FCT basic function Dependency of perminted speed on A_est1

#REQ-UNISIG-SUB026-007303#REF# 3.13.9.3.2.9
If T_be > T_traction, the estimated acceleration during T_berem (A_est2) shall be the one measured at the moment when the calculation is
made, but limited to values between 0 and +0.4m/s2.
#ANALYSE-VALUNISIG-4448#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-8256#REF# FCT basic function Dependency of perminted speed on A_est2

#REQ-UNISIG-SUB026-007305#REF# 3.13.9.3.2.10 #REQ-UNISIG-SUB026-008090#REF#
The compensated speed and the distance travelled during the time elapsed between the Emergency brake intervention and the full application of
the braking effort is reached shall be derived as follows (see Figure 45):




with  or  (if compensation of speed inaccuracy is inhibited by National Value)

with  and
realised by: #REQ-UNISIG-SUB026-007304:01#REF#

#REQ-UNISIG-SUB026-007304:01#REF# to.3.13.9.3.2.10 #REQ-UNISIG-SUB026-007305#REF#
The compensated speed and the distance travelled during the time elapsed between the Emergency brake intervention and the full application of
the braking effort is reached shall be derived as follows (see Figure 45):




with  or  (if compensation of speed inaccuracy is inhibited by National Value)

with  and


Clarification:
Depending on the target speed the correct value for T_berem (T_berem_cm0 or T_berem_cmt) shall be used in the calculation.
TEST APPROACH:
The following aspects have been identified:
1) dependency on Q_NVINHSMICPERM/V_ura
2) dependency on T_traction
#ANALYSE-VALUNISIG-4449#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5630#REF# FCT 1 Variable test Q_NVINHSMICPERM
#TEST-VAL-SUB026-5647#REF# FCT 2 Traction cut-off is not implemented, dependency on T_traction

#REQ-UNISIG-SUB026-007309#REF# 3.13.9.3.2.12
For the estimated speed V_est, the location of the EBI supervision limit shall be:

TEST APPROACH:
The following aspect has been identified:
1) dependency on T_traction/D_bec
#ANALYSE-VALUNISIG-4450#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5647#REF# FCT 1 Traction cut-off is not implemented, dependency on T_traction

#REQ-UNISIG-SUB026-007311#REF# 3.13.9.3.3.1
For the EOA, the on-board shall calculate the location of the SBI supervision limit (SBI1) valid for the estimated speed, assuming that this
latter remains constant during the interval T_bs1, until the SBD curve is reached.

realised by: #REQ-UNISIG-SUB026-007312#REF#

#REQ-UNISIG-SUB026-007312#REF# 3.13.9.3.3.1 #REQ-UNISIG-SUB026-007311#REF#
For the EOA, the on-board shall calculate the location of the SBI supervision limit (SBI1) valid for the estimated speed, assuming that this
latter remains constant during the interval T_bs1, until the SBD curve is reached.



Clarification:
Depending on the target speed the correct value for T_bs1 (T_bs1_cm0 or T_bs1_cmt) shall be used in the calculation.
TEST APPROACH:
The following aspects have been identified:
1) Pre-programmed brake model 
2) Conversion model
#ANALYSE-VALUNISIG-4451#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F90#REF# FCT 1 Dependecy SBI on T_bs/T_brake_service (Pre-programmed brake model)
#TEST-VAL-SUB026-5644#REF# FCT 2 Interface to SB available, T_bs1/T_bs2 (d_SBI) dependency on train length change

#REQ-UNISIG-SUB026-007313#REF# 3.13.9.3.3.2
For an EBD based target, the on-board shall calculate the location of the SBI supervision limit (SBI2) valid for the estimated speed, assuming
that this latter remains constant during the interval T_bs2, until the location of the EBI supervision limit is reached.

realised by: #REQ-UNISIG-SUB026-007314#REF#

#REQ-UNISIG-SUB026-007314#REF# 3.13.9.3.3.2 #REQ-UNISIG-SUB026-007313#REF#
For an EBD based target, the on-board shall calculate the location of the SBI supervision limit (SBI2) valid for the estimated speed, assuming
that this latter remains constant during the interval T_bs2, until the location of the EBI supervision limit is reached.



Clarification:
Depending on the target speed the correct value for T_bs2 (T_bs2_cm0 or T_bs2_cmt) shall be used in the calculation.
TEST APPROACH:
The following aspects have been identified:
1) Pre-programmed brake model 
2) Conversion model
#ANALYSE-VALUNISIG-4452#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F90#REF# FCT 1 Dependecy SBI on T_bs/T_brake_service (Pre-programmed brake model)
#TEST-VAL-SUB026-5644#REF# FCT 2 Interface to SB available, T_bs1/T_bs2 (d_SBI) dependency on train length change

#REQ-UNISIG-SUB026-007315#REF# 3.13.9.3.3.3
If the service brake command is available for use and the service brake feedback is not available for use, T_bs1 and T_bs2 shall be equal to
T_bs.
realised by: #REQ-UNISIG-SUB026-007316#REF#

#REQ-UNISIG-SUB026-007316#REF# 3.13.9.3.3.3 #REQ-UNISIG-SUB026-007315#REF#
If the service brake command is available for use and the service brake feedback is not available for use, T_bs1 and T_bs2 shall be equal to
T_bs.

Clarification:
This applies to T_bs1_cm0, T_bs1_cmt, T_bs2_cm0 and T_bs2_cmt.
#ANALYSE-VALUNISIG-4453#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-010177#REF# 3.13.9.3.3.4
Service brake feedback shall be used for driver initiated service brake only.
UNISIG clarification: SB feedback shall not be used if the SB was applied by OBU supervision function.
TEST APPROACH:
The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#. 
#ANALYSE-VALUNISIG-4771#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4B87#REF# FCT basic function SB feedback is used only if SB is command is initiated by driver

#REQ-UNISIG-SUB026-007317#REF# 3.13.9.3.3.4.1
In case T_bs < T_bs2_locked then T_bs2 shall be equal to T_bs2_locked.
realised by: #REQ-UNISIG-SUB026-007318#REF#

#REQ-UNISIG-SUB026-007318#REF# 3.13.9.3.3.4.1 #REQ-UNISIG-SUB026-007317#REF#
In case T_bs < T_bs2_locked then T_bs2 shall be equal to T_bs2_locked.

Clarification:
This applies to T_bs2_cm0 and T_bs2_cmt.
#ANALYSE-VALUNISIG-4774#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4B81#REF# FCT T_bs2_cm0 SB feedback available, t_bs smaller than t_bs2_locked
#TEST-VAL-SUB026-4B80#REF# FCT T_bs2_cmt SB feedback available, t_bs smaller than t_bs2_locked

#REQ-UNISIG-SUB026-007320#REF# 3.13.9.3.3.5
If the service brake command is not available for use, T_bs1 and T_bs2 shall be set to zero.
realised by: #REQ-UNISIG-SUB026-007319#REF#

#REQ-UNISIG-SUB026-007319#REF# 3.13.9.3.3.5 #REQ-UNISIG-SUB026-007320#REF#
If the service brake command is not available for use, T_bs1 and T_bs2 shall be set to zero.

Clarification:
This applies to T_bs1_cm0, T_bs1_cmt, T_bs2_cm0 and T_bs2_cmt.
TEST APPROACH:
The following aspects have been identified:
1) service brake command is not available for use
2) service brake command is available for use
#ANALYSE-VALUNISIG-4454#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5645#REF# FCT 1 Interface to SB not available, T_bs1/T_bs2 (d_SBI) have no dependency on train length change
#TEST-VAL-SUB026-5644#REF# FCT 2 Interface to SB available, T_bs1/T_bs2 (d_SBI) dependency on train length change

#REQ-UNISIG-SUB026-003055#REF# 3.13.9.3.3.7
For display purpose only, the SBI1 speed for the estimated train front end, shall be calculated as follows (see Figure 47):


if

#DSC-UNISIG-SUB026-003059#REF#

Figure 47: Calculation of SBI1 speed displayed to the driver
realised by: #REQ-UNISIG-SUB026-007321#REF#

#REQ-UNISIG-SUB026-007321#REF# 3.13.9.3.3.7 #REQ-UNISIG-SUB026-003055#REF#
For display purpose only, the SBI1 speed for the estimated train front end, shall be calculated as follows (see Figure 47):


if



Figure 47: Calculation of SBI1 speed displayed to the driver

Clarification:
Depending on the target speed the correct value for T_bs1 (T_bs1_cm0 or T_bs1_cmt) shall be used in the calculation.
Note:
In the currrent context, the target speed will always be 0.
TEST APPROACH:
The following aspects have been identified:
1) dependency on T_bs1
2) dependency on V_est
3) dependency on d_estfront
#ANALYSE-VALUNISIG-4455#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-8150#REF# FCT 1 Dependency of perminted speed and FLOI speed on T_bs1
#TEST-VAL-SUB026-8151#REF# FCT 2 Dependency of P speed related to SBD on V_est
#TEST-VAL-SUB026-5628#REF# FCT 3 Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007324#REF# 3.13.9.3.3.8 #ANA-UNISIG-CR1124-0001#REF#
For display purpose only, the SBI2 speed for the max safe front end of the train shall be calculated as follows (see Figure 48):


if

With D_bec and V_bec calculated according to 3.13.9.3.2.10
UNISIG clarification: solution of UCR 1124, part 1 is to be taken over
#DSC-UNISIG-SUB026-003066:01#REF#

Figure 48: Calculation of SBI2 speed displayed to the driver
realised by: #REQ-UNISIG-SUB026-007325:01#REF#

#REQ-UNISIG-SUB026-007325:01#REF# 3.13.9.3.3.8 #REQ-UNISIG-SUB026-007324#REF#
#ANA-UNISIG-CR1124-0001#REF#
For display purpose only, the SBI2 speed for the max safe front end of the train shall be calculated as follows (see Figure 48):


if




With V_delta0, V_delta1 and V_delta2 calculated according to 3.13.9.3.2.10

With




Figure 48: Calculation of SBI2 speed displayed to the driver

Clarification:
Depending on the target speed the correct value for T_bs2 (T_bs2_cm0 or T_bs2_cmt) shall be used in the calculation.
UNISIG clarification: solution of UCR 1124, part 1 is to be taken over
TEST APPROACH:
The following aspects have been identified:
1) dependency on V_delta0
2) dependency on V_delta1
3) dependency on V_delta2
4) dependency on T_bs2
5) dependency on V_est
6) dependency on d_maxsafefrontend
7) dependency on T_traction

Note: the influence of T_traction on the EBD supervision limits is covered via #REQ-UNISIG-SUB026-007295#, so aspect 7) is ommited here.
#ANALYSE-VALUNISIG-4456#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5630#REF# FCT 1, 6 Variable test Q_NVINHSMICPERM
#TEST-VAL-SUB026-8258#REF# FCT 2 Dependency of perminted speed on A_est1
#TEST-VAL-SUB026-8256#REF# FCT 3 Dependency of perminted speed on A_est2
#TEST-VAL-SUB026-8142#REF# FCT 4 Dependency of perminted speed and FLOI speed on T_bs2
#TEST-VAL-SUB026-8143#REF# FCT 5 Dependency of perminted speed on V_est

#REQ-UNISIG-SUB026-007331#REF# 3.13.9.3.3.9
The FLOI (First Line Of Intervention) supervision limit, valid for estimated speed, shall be defined as the SBI supervision limit, of which the
location is the closest to the train front, taking into account the max safe train front end for the SBI2 supervision limit(s) and the estimated
train front end for the SBI1.
if

if

With

MREBDT = Most Restrictive Target amongst the EBD based targets
#ANALYSE-VALUNISIG-4457#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007336#REF# 3.13.9.3.4.1
The on-board shall calculate the location of the Warning supervision limit valid for the estimated speed, assuming that this latter remains
constant during the interval T_warning until the location of the FLOI supervision limit is reached.

realised by: #REQ-UNISIG-SUB026-007337#REF#

#REQ-UNISIG-SUB026-007337#REF# 3.13.9.3.4.1 #REQ-UNISIG-SUB026-007336#REF#
#REQ-UNISIG-SUB026-007338#REF#
#REQ-UNISIG-SUB026-007971#REF#
The on-board shall calculate the location of the Warning supervision limit valid for the estimated speed, assuming that this latter remains
constant during the interval T_warning until the location of the FLOI supervision limit is reached.



T_warning is defined as a fixed value (refer to A.3.1).
TEST APPROACH:
The following aspect has been identified:
1) dependency on parameterized T_warning
#ANALYSE-VALUNISIG-4458#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F69#REF# FCT 1 Dependecy on T_warning

#REQ-UNISIG-SUB026-007338#REF# 3.13.9.3.4.2
T_warning is defined as a fixed value (refer to A.3.1).
realised by: #REQ-UNISIG-SUB026-007337#REF#

#REQ-UNISIG-SUB026-007342#REF# 3.13.9.3.5.1
In case the calculation of the GUI curve is inhibited, the on-board shall calculate the location of the Permitted speed supervision limit valid
for the estimated speed, assuming that this latter remains constant during the interval T_driver until the location of the FLOI supervision
limit is reached.

realised by: #REQ-UNISIG-SUB026-007341#REF#

#REQ-UNISIG-SUB026-007341#REF# 3.13.9.3.5.1 #REQ-UNISIG-SUB026-007342#REF#
#REQ-UNISIG-SUB026-007343#REF#
#REQ-UNISIG-SUB026-007972#REF#
In case the calculation of the GUI curve is inhibited, the on-board shall calculate the location of the Permitted speed supervision limit valid
for the estimated speed, assuming that this latter remains constant during the interval T_driver until the location of the FLOI supervision
limit is reached.



T_driver is defined as a fixed value (refer to A.3.1).
TEST APPROACH:
The following aspect has been identified:
1) dependency on parameterized T_driver
#ANALYSE-VALUNISIG-4459#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F70#REF# FCT 1 Dependecy on T_driver

#REQ-UNISIG-SUB026-007343#REF# 3.13.9.3.5.2
T_driver is defined as a fixed value (refer to A.3.1).
realised by: #REQ-UNISIG-SUB026-007341#REF#

#REQ-UNISIG-SUB026-007345#REF# 3.13.9.3.5.4 #REQ-UNISIG-SUB026-007049#REF#
In case the calculation of the Guidance curve is enabled, the on-board shall calculate the location of the Permitted speed supervision limit
valid for the estimated speed, as follows:

TEST APPROACH:
The following aspect has been identified:
1) dependency on d_GUI
#ANALYSE-VALUNISIG-4460#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5628#REF# FCT 1 Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007346#REF# 3.13.9.3.5.5
In case the calculation of the GUI curve is inhibited, for display purpose only, the P speed related to SBD shall be calculated for the
estimated train front end as follows:


if
realised by: #REQ-UNISIG-SUB026-007347#REF#

#REQ-UNISIG-SUB026-007347#REF# 3.13.9.3.5.5 #REQ-UNISIG-SUB026-007346#REF#
In case the calculation of the GUI curve is inhibited, for display purpose only, the P speed related to SBD shall be calculated for the
estimated train front end as follows:


if


Clarification:
Depending on the target speed the correct value for T_bs1 (T_bs1_cm0 or T_bs1_cmt) shall be used in the calculation.
TEST APPROACH:
The following aspects have been identified:
1) dependency on T_bs1
2) dependency on V_est
3) dependency on d_estfront
4) dependency on GUI curve calculation
5) dependency on T_driver

Note: the influence of T_driver on the supervision limits is covered via #REQ-UNISIG-SUB026-007341#, so
aspect 5) is ommited here.
#ANALYSE-VALUNISIG-4461#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-8150#REF# FCT 1 Dependency of perminted speed and FLOI speed on T_bs1
#TEST-VAL-SUB026-8151#REF# FCT 2 Dependency of P speed related to SBD on V_est
#TEST-VAL-SUB026-5628#REF# FCT 3, 4 Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007349#REF# 3.13.9.3.5.6
In case the calculation of the GUI curve is enabled, for display purpose only, the P speed related to SBD shall be calculated for the estimated
train front end as follows:


if
realised by: #REQ-UNISIG-SUB026-007350#REF#

#REQ-UNISIG-SUB026-007350#REF# 3.13.9.3.5.6 #REQ-UNISIG-SUB026-007349#REF#
In case the calculation of the GUI curve is enabled, for display purpose only, the P speed related to SBD shall be calculated for the estimated
train front end as follows:


if


Clarification:
Depending on the target speed the correct value for T_bs1 (T_bs1_cm0 or T_bs1_cmt) shall be used in the calculation.
TEST APPROACH:
Only dependency on GUI is verified here; the other dependencies are verified in the tests for
#REQ-UNISIG-SUB026-007347#
#ANALYSE-VALUNISIG-4462#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5628#REF# FCT basic function Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007352#REF# 3.13.9.3.5.7 #ANA-UNISIG-CR1124-0001#REF#
In case the calculation of the GUI curve is inhibited, for display purpose only, the P speed related to EBD, shall be calculated for the max
safe front end of the train as follows (see Figure 49):


if

With D_bec and V_bec calculated according to 3.13.9.3.2.10
UNISIG clarification: solution of UCR 1124, part 1 is to be taken over
#DSC-UNISIG-SUB026-003108#REF#

Figure 49: Calculation of Permitted speed displayed to the driver
realised by: #REQ-UNISIG-SUB026-007353:01#REF#

#REQ-UNISIG-SUB026-007353:01#REF# 3.13.9.3.5.7 #REQ-UNISIG-SUB026-007352#REF#
#ANA-UNISIG-CR1124-0001#REF#
In case the calculation of the GUI curve is inhibited, for display purpose only, the P speed related to EBD, shall be calculated for the max
safe front end of the train as follows (see Figure 49):


if


With V_delta0, V_delta1 and V_delta2 calculated according to 3.13.9.3.2.10
With




Figure 49: Calculation of Permitted speed displayed to the driver

Clarification:
Depending on the target speed the correct value for T_bs2 (T_bs2_cm0 or T_bs2_cmt) shall be used in the calculation.
UNISIG clarification: solution of UCR 1124, part 1 is to be taken over

a additional clarification for T_bs2 is nnecessary
TEST APPROACH:
The following aspects have been identified:
1) dependency on V_delta0
2) dependency on V_delta1
3) dependency on V_delta2
4) dependency on T_bs2
5) dependency on V_est
6) dependency on d_maxsafefrontend
7) dependency on T_traction
8) dependency on T_driver
9) dependency on GUI curve calculation

Note1: the influence of T_traction on the EBD supervision limits is covered via #REQ-UNISIG-SUB026-007295#, so aspect 7) is ommited here.
Note2: the influence of T_driver on the supervision limits is covered via #REQ-UNISIG-SUB026-007341#, so aspect 8) is ommited here.
#ANALYSE-VALUNISIG-4463#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5630#REF# FCT 1, 6 Variable test Q_NVINHSMICPERM
#TEST-VAL-SUB026-8258#REF# FCT 2 Dependency of perminted speed on A_est1
#TEST-VAL-SUB026-8256#REF# FCT 3 Dependency of perminted speed on A_est2
#TEST-VAL-SUB026-8142#REF# FCT 4 Dependency of perminted speed and FLOI speed on T_bs2
#TEST-VAL-SUB026-8143#REF# FCT 5 Dependency of perminted speed on V_est
#TEST-VAL-SUB026-5628#REF# FCT 9 Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007358#REF# 3.13.9.3.5.8 #ANA-UNISIG-CR1124-0001#REF#
In case the calculation of the GUI curve is enabled, for display purpose only, the P speed related to EBD, shall be calculated for the max safe
front end of the train as follows:


if

or if

With D_bec and V_bec calculated according to 3.13.9.3.2.10
UNISIG clarification: solution of UCR 1124, part 1 is to be taken over
realised by: #REQ-UNISIG-SUB026-007359:01#REF#

#REQ-UNISIG-SUB026-007359:01#REF# 3.13.9.3.5.8 #REQ-UNISIG-SUB026-007358#REF#
#ANA-UNISIG-CR1124-0001#REF#
In case the calculation of the GUI curve is enabled, for display purpose only, the P speed related to EBD, shall be calculated for the max safe
front end of the train as follows:




if

or if



With V_delta0, V_delta1 and V_delta2 calculated according to 3.13.9.3.2.10
With


Clarification:
Depending on the target speed the correct value for T_bs2 (T_bs2_cm0 or T_bs2_cmt) shall be used in the calculation.
UNISIG clarification: solution of UCR 1124, part 1 is to be taken over

an additional clarification for T_bs2 is nnecessary
TEST APPROACH:
Only dependency on GUI is verified here; the other dependencies are verified in the tests for #REQ-UNISIG-SUB026-007353:01#
#ANALYSE-VALUNISIG-4464#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5628#REF# FCT basic function Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007364:01#REF# 3.13.9.3.5.9 #REQ-UNISIG-SUB026-008090#REF#
In order to determine the reference location of the target distance displayed to the driver and in order to determine the foot of the GUI curve
(only if it is enabled) in case of target different from EOA/SvL, the location of the Permitted speed supervision limit, valid for the target
speed, shall be calculated from the EBD, taking into account the following assumptions:
a)	the estimated acceleration shall be set to “zero”
b)	if not inhibited by National Value, the compensation of the inaccuracy of the speed measurement shall be set to a value calculated from
the target speed, as defined in SUBSET-041 § 5.3.1.2: V_delta0t = f41(V_target)
the correspond requirement for SUBSET-041 § 5.3.1.2
is #REQ-SRS_041-000135#REF#
#ANALYSE-VALUNISIG-4465#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007366#REF# 3.13.9.3.5.10
To do so, the same formulas defined above with V_est and V_delta0 shall be applied, by substituting V_est with V_target and V_delta0 with
V_delta0t.



realised by: #REQ-UNISIG-SUB026-007367:01#REF#

#REQ-UNISIG-SUB026-007367:01#REF# 3.13.9.3.5.10 #REQ-UNISIG-SUB026-007366#REF#
To do so, the same formulas defined above with V_est and V_delta0 shall be applied, by substituting V_est with V_target and V_delta0 with
V_delta0t.





Clarification:
Depending on the target speed the correct value for T_bs2 (T_bs2_cm0 or T_bs2_cmt) and T_berem (T_berem_cm0 or T_berem_cmt) shall be used in the
calculation.
#ANALYSE-VALUNISIG-4466#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007370#REF# 3.13.9.3.5.11 #REQ-UNISIG-SUB026-008090#REF#
In case a non protected LX start location is supervised as both the EOA and SvL and the stopping in rear of LX is not required, the location of
the Permitted speed supervision limit, valid for the LX speed shall be used in order to determine the location where the supervision of the LX
start location is substituted by the supervision of the LX speed (see section 5.16.3). This location shall be calculated taking into account the
following assumptions:
a)	the estimated acceleration shall be set to “zero”
b)	if not inhibited by National Value, the compensation of the inaccuracy of the speed measurement shall be set to a value calculated from
the LX speed, as defined in SUBSET-041 § 5.3.1.2: V_delta0lx = f41(V_LX)
NV Q_NVINHSMICPERM is meant.

The correspond requirement for SUBSET-041 § 5.3.1.2
is #REQ-SRS_041-000135#REF#:
± 2 km/h for speed lower than 30 km/h, then increasing linearly up to ± 12 km/h at 500 km/h.
#ANALYSE-VALUNISIG-5333#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007371#REF# 3.13.9.3.5.12
To do so, the same formulas defined above with V_est and V_delta0 shall be applied, by substituting V_est with V_LX and V_delta0 with
V_delta0lx.




with

if

Or  if

In case the GUI curve is inhibited:

In case the GUI curve is enabled:
#ANALYSE-VALUNISIG-5334#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007372#REF# 3.13.9.3.6.1
The on-board shall calculate the location of the Indication supervision limit valid for the estimated speed, assuming that this latter remains
constant during the interval T_indication until the location of the Permitted speed supervision limit is reached.

TEST APPROACH:
The following aspect has been identified:
1) dependency on T_indication
#ANALYSE-VALUNISIG-4467#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F87#REF# FCT basic function Dependency T_brake_service ->T_bs ->T_indication : 0.8*T_bs > 5s

#REQ-UNISIG-SUB026-007375#REF# 3.13.9.3.6.2
If the service brake feedback interface is not available for use, then

realised by: #REQ-UNISIG-SUB026-007374#REF#

#REQ-UNISIG-SUB026-007374#REF# 3.13.9.3.6.2 #REQ-UNISIG-SUB026-007375#REF#
If the service brake feedback interface is not available for use, then



Clarification:
Depending on the target speed the correct value for T_bs (T_bs_cm0 or T_bs_cmt) shall be used in the calculation.
TEST APPROACH:
The following aspects have been identified:
1) Pre-programmed brake model 
1.1) 0.8*T_bs<5s
1.2) 0.8*T_bs>5s
2) Conversion model
2.1) T_bs is based on T_bs_cm0
2.1.1) 0.8*T_bs<5s
2.1.2) 0.8*T_bs>5s
2.2) T_bs is based on T_bs_cmt
2.2.1) 0.8*T_bs<5s
2.2.2) 0.8*T_bs>5s
#ANALYSE-VALUNISIG-4468#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F88#REF# FCT 1.1 Dependency T_brake_service ->T_bs ->T_indication : 0.8*T_bs < 5s
#TEST-VAL-SUB026-4F87#REF# FCT 1.2 Dependency T_brake_service ->T_bs ->T_indication : 0.8*T_bs > 5s
#TEST-VAL-SUB026-8137#REF# FCT 2.1.1, 2.2.1 Dependency T_brake_service ->T_bs ->T_indication : 0.8*T_bs < 5s (Conversion model)
#TEST-VAL-SUB026-8136#REF# FCT 2.1.2, 2.2.2 Dependency T_brake_service ->T_bs ->T_indication : 0.8*T_bs > 5s (Conversion model)

#REQ-UNISIG-SUB026-007377#REF# 3.13.9.3.6.4
If the service brake feedback interface is available for use then T_indication = 5s.
TEST APPROACH:
The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#. 
#ANALYSE-VALUNISIG-7648#REF# FCT The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#.
#TEST-VAL-SUB026-4B76#REF# FCT basic function T_indication is 5s if SB feedback available for use

#REQ-UNISIG-SUB026-007379#REF# 3.13.9.4.1
The release speed is a special ceiling speed limit, applicable in the vicinity of the EOA. The EBI supervision limit shall be equal to the
release speed. There is no SBI, W, P, I supervision limit associated to the release speed.
realised by: #REQ-UNISIG-SUB026-007505#REF#

#REQ-DESIGN-CR-0576#REF# 3.13.9.4.3 #REQ-UNISIG-SUB026-007057#REF#
With each MA, it shall be possible for the trackside to:
a)	Give the value of the release speed directly to the on-board, OR
b)	Instruct the on-board to calculate the release speed, OR
c)	Instruct the on-board to use the national value.
UNISIG clarification:
a release speed = 0 from trackside is interpreted as no release speed
#TEST-VAL-SUB026-7568#REF# FCT DP release speed Variable test V_RELEASEDP
#TEST-VAL-SUB026-7569#REF# FCT OL release speed Variable test V_RELEASEOL

#REQ-UNISIG-SUB026-3746#REF# to.3.13.9.4.3 #ANA-UNISIG-ReleaseSpeed-0003#REF#
If a release speed both for overlap and for danger point is defined, the release speed for overlap shall be used until the overlap is released
(see #REQ-UNISIG-SUB026-0489:02#REF#)
#TEST-VAL-SUB026-3820#REF# FCT basic function Release speed calculation depending on V_RELEASEOL and V_RELEASEDP

#REQ-DESIGN-CR-0577#REF# 3.13.9.4.4
In case the MA does not identify the variant to be used or in case of LOA, no release speed shall be supervised.
TEST APPROACH:
The following aspects have been identified:
1) LoA
2) MA without DP/OL
3) release speed = 0
#TEST-VAL-SUB026-5610#REF# FCT 1 Processing of MA with LoA and DP/OL
#TEST-VAL-SUB026-5611#REF# FCT 2 MA does not identify the RS variant to be used (no OL/DP given)
#TEST-VAL-SUB026-3A07#REF# FCT 3 Processing of track side defined release speed 0

#REQ-UNISIG-SUB026-007387:01#REF# 3.13.9.4.6 #REQ-UNISIG-SUB026-008090#REF#
The start location of the release speed monitoring (i.e. where the EBI supervision limit related to EBD is replaced with an EBI supervision
limit equal to the release speed value) shall be the location of the FLOI supervision limit, calculated for the Release Speed value, taking into
account the following assumptions:
a)	the estimated acceleration shall be set to “zero”
b)	if not inhibited by National Value, the compensation of the inaccuracy of the speed measurement shall be set to a value calculated from
the release speed, as defined in SUBSET-041 § 5.3.1.2: V_delta0rs = f41(V_release)
the correspond requirement for SUBSET-041 § 5.3.1.2
is ##REQ-SRS_041-000135#REF#
#ANALYSE-VALUNISIG-4469#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007389#REF# 3.13.9.4.7
To do so, the same formulas defined above with V_est and V_delta0 shall be applied, by substituting V_est with V_release and V_delta0 with
V_delta0rs.




with

if

Or  if

#DSC-UNISIG-SUB026-003179#REF#

Figure 50: Start location of Release Speed Monitoring
realised by: #REQ-UNISIG-SUB026-007390:01#REF#

#REQ-UNISIG-SUB026-007390:01#REF# 3.13.9.4.7 #REQ-UNISIG-SUB026-007389#REF#
To do so, the same formulas defined above with V_est and V_delta0 shall be applied, by substituting V_est with V_release and V_delta0 with
V_delta0rs.




with



if


Or


if




Figure 50: Start location of Release Speed Monitoring
Clarification:
Depending on the target speed the correct values for T_bs1, T_bs2, T_berem (T_bs1_cm0, T_bs1_cmt, T_bs2_cm0, T_bs2_cmt, T_berem_cm0 or
T_berem_cmt) shall be used in the calculation.
#ANALYSE-VALUNISIG-4470#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007396#REF# 3.13.9.4.8
When the Release Speed is calculated on-board (Figure 51 box 3), its value shall be equal to the most restrictive value, at the Trip location
related to the EOA, amongst the EBI supervision limit related to the SvL (Figure 51 box 1) and, if any, the EBI supervision limits(s) related to
other target(s) between the Trip location related to the EOA and the SvL (Figure 51 box 2).

#DSC-UNISIG-SUB026-003183#REF#

Figure 51: Calculated Release Speed based on speed restriction between EOA and SvL
realised by: #REQ-UNISIG-SUB026-007397#REF#

#REQ-UNISIG-SUB026-007397#REF# 3.13.9.4.8 #REQ-UNISIG-SUB026-007396#REF#
When the Release Speed is calculated on-board (Figure 51 box 3), its value shall be equal to the most restrictive value, at the Trip location
related to the EOA, amongst the EBI supervision limit related to the SvL (Figure 51 box 1) and, if any, the EBI supervision limits(s) related to
other target(s) between the Trip location related to the EOA and the SvL (Figure 51 box 2).



Figure 51: Calculated Release Speed based on speed restriction between EOA and SvL

Clarification:
Additionally, the calculated Release Speed shall be limited to the most restrictive value of the MRSP between the EOA and the Trip location
related to the EOA.
#ANALYSE-VALUNISIG-4471#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5234#REF# FCT basic function On-board calculated release speed

#REQ-UNISIG-SUB026-007399:02#REF# 3.13.9.4.8.1 #REQ-UNISIG-SUB026-008090#REF#
In order to calculate in advance the EBI supervision limit at the Trip location related to the EOA, the on-board equipment shall take into
account an estimated acceleration set to “zero”.
is considered in the formula in 3.13.9.4.8.2
realised by: #REQ-UNISIG-SUB026-007402:02#REF#

#REQ-UNISIG-SUB026-007402:02#REF# 3.13.9.4.8.2 #REQ-UNISIG-SUB026-007399:02#REF#
#ANA-UNISIG-CR1127-0001#REF#
The release speed shall be iteratively calculated as follows:


With  or  (if compensation of speed inaccuracy is inhibited by National Value)

With

With


And with if level = 1

if level = 2 or 3


if

or if



as soon as

with
UNISIG clarification:
UCR 1127 - this requirement is replaced by a newer
realised by: #REQ-UNISIG-SUB026-007829#REF#

#REQ-UNISIG-SUB026-007829#REF# to.3.13.9.4.8.2 #REQ-UNISIG-SUB026-007402:02#REF#
#ANA-UNISIG-CR1127-0001#REF#
The on-board equipment shall seek for each target referred to in clause 3.13.9.4.8 a release speed value which satisfies the two following
inequalities:





With  or  (if compensation of speed inaccuracy is inhibited by National Value)

With

With


And with if level = 1

if level = 2 or 3


If no speed value higher than V_target fulfils the above inequalities, then:

UNISIG clarifications:
UCR 1127 - new requirement 3.13.9.4.8.2

Q_LOCACC of the current LRBG is used for Qlocacc_refBG

=> this requirement replaces the older clarification REQ-UNISIG-SUB026-007827:02
TEST APPROACH:
The correct implementation of the requirement is verified via module test.
Following aspects have been identified for integration test:
1) dependency on Q_NVINHSMICPERM 
2) dependency on level
3) dependency on antenna offset
4) dependency on Q_LocAcc
5) dependency on (d_maxsafefront - d_minsafefront)
6) dependency on antenna distance
7) switch between estimated and measured inaccuracy 
#TEST-VAL-SUB026-3B94#REF# FCT 1 On-Board calculated release speed: dependency on Q_NVINHSMICPERM
#TEST-VAL-SUB026-3B96#REF# FCT 2, 3 (antenna offset!=0) On-Board calculated release speed: dependency on level and antenna offset(!=0)
#TEST-VAL-SUB026-3B97#REF# FCT 4 On-board calculated release speed - dependency on Q_LocAcc
#TEST-VAL-SUB026-7052#REF# FCT 5 Release speed calculation depending on MA reference location
#TEST-VAL-SUB026-7703#REF# FCT 6 Onboard calculated release speed: dependency on antenna distance (cab change)
#TEST-VAL-SUB026-5234#REF# FCT 7 On-board calculated release speed
#TEST-VAL-SUB026-3B95#REF# FCT 3 (antenna offset=0) On-Board calculated release speed: dependency on level and antenna offset(=0)

#REQ-UNISIG-SUB026-007409#REF# 3.13.9.4.9
If the release speed (Figure 52 box 1 gives an example when it is calculated on-board) exceeds the MRSP anywhere in the area (Figure 52 box 2)
delimited on one side by the presumed start location of the Release speed monitoring and on the other side by the trip location related to the
EOA, the on-board shall use as a fixed release speed (Figure 52 box 4) the most restrictive value of the MRSP (Figure 52 box 3) within this
area, and shall re-evaluate the start location of the Release speed monitoring accordingly.

#DSC-UNISIG-SUB026-003203#REF#

Figure 52: Release Speed limited by MRSP
realised by: #REQ-UNISIG-SUB026-007408#REF#

#REQ-UNISIG-SUB026-007408#REF# 3.13.9.4.9 #REQ-UNISIG-SUB026-007409#REF#
If the release speed (Figure 52 box 1 gives an example when it is calculated on-board) exceeds the MRSP anywhere in the area (Figure 52 box 2)
delimited on one side by the presumed start location of the Release speed monitoring and on the other side by the trip location related to the
EOA, the on-board shall use as a fixed release speed (Figure 52 box 4) the most restrictive value of the MRSP (Figure 52 box 3) within this
area, and shall re-evaluate the start location of the Release speed monitoring accordingly.



Figure 52: Release Speed limited by MRSP
#ANALYSE-VALUNISIG-4474#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5234#REF# FCT basic function On-board calculated release speed

#REQ-UNISIG-SUB026-007412#REF# 3.13.9.5.3
Starting from the first element of the MRSP (i.e. from the start location of the on-board stored track description), the on-board shall
calculate the location of the Indication supervision limit, valid for the speed of the MRSP element, taking into account the following
assumptions:
a)	the estimated acceleration shall be set to “zero”
b)	if not inhibited by National Value, the compensation of the inaccuracy of the speed measurement shall be set to a value, calculated from
the speed of the MRSP element, as defined in SUBSET-041 § 5.3.1.2: V_delta0ind = f41(V_MRSP-n)
the correspond requirement for SUBSET-041 § 5.3.1.2
is #REQ-SRS_041-000135#REF#
realised by: #REQ-UNISIG-SUB026-007413:01#REF#

#REQ-UNISIG-SUB026-007413:01#REF# 3.13.9.5.3 #REQ-UNISIG-SUB026-008090#REF#
#REQ-UNISIG-SUB026-007412#REF#
Starting from the first element of the MRSP (i.e. from the start location of the on-board stored track description), the on-board shall
calculate the location of the Indication supervision limit, valid for the speed of the MRSP element, taking into account the following
assumptions:
a)	the estimated acceleration shall be set to “zero”
b)	if not inhibited by National Value, the compensation of the inaccuracy of the speed
measurement shall be set to a value, calculated from the speed of the MRSP element, as defined in SUBSET-041 § 5.3.1.2: V_delta0ind =
f41(V_MRSP-n)
Clarification:
Only MRSP-elements that are (at least in part) in front of the max safe front end shall be taken into account.
the correspond requirement for SUBSET-041 § 5.3.1.2
is #REQ-SRS_041-000135#REF#
#ANALYSE-VALUNISIG-4475#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007415#REF# 3.13.9.5.4
To calculate the EBI supervision limit, the same formulas defined above with V_est and V_delta0 shall be applied, by substituting V_est with
V_MRSP-n and V_delta0 with V_delta0ind.






With  if the GUI curve is inhibited

Or  if the GUI curve is enabled
realised by: #REQ-UNISIG-SUB026-007416:01#REF#

#REQ-UNISIG-SUB026-007416:01#REF# 3.13.9.5.4 #REQ-UNISIG-SUB026-007415#REF#
To calculate the EBI supervision limit, the same formulas defined above with V_est and V_delta0 shall be applied, by substituting V_est with
V_MRSP-n and V_delta0 with V_delta0ind.






With  if the GUI curve is inhibited

Or  if the GUI curve is enabled


Clarification:
Depending on the target speed the correct values for T_bs2 and T_berem (T_bs2_cm0, T_bs2_cmt, T_berem_cm0 or T_berem_cmt) shall be used in the
calculation.
#ANALYSE-VALUNISIG-4476#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007421#REF# 3.13.9.5.5
If the Indication supervision limit, obtained from the speed of the nth element, is located between the start and end locations of this nth
element, the pre-indication location shall be calculated as follows:
If

Then
TEST APPROACH:
The following aspect has been identified:
1) dependency on parameterized T_preindication
#ANALYSE-VALUNISIG-4477#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F71#REF# FCT 1 Dependecy on T_preindication

#REQ-UNISIG-SUB026-007422#REF# 3.13.9.5.6
If the Indication supervision limit, obtained from the speed of the nth element, is located in advance of the end location of this nth element,
and if the Indication supervision limit, obtained from the speed of the n+1th element is located in rear of the end location of this nth element
(see Figure 53), the pre-indication location shall be calculated as follows:
If  and

Then

#DSC-UNISIG-SUB026-003230#REF#

Figure 53: Pre-indication location derived from MRSP speed increase
realised by: #REQ-UNISIG-SUB026-007423#REF#

#REQ-UNISIG-SUB026-007423#REF# 3.13.9.5.6 #REQ-UNISIG-SUB026-007422#REF#
#REQ-UNISIG-SUB026-007426#REF#
#REQ-UNISIG-SUB026-007973#REF#
If the Indication supervision limit, obtained from the speed of the nth element, is located in advance of the end location of this nth element,
and if the Indication supervision limit, obtained from the speed of the n+1th element is located in rear of the end location of this nth element
(see Figure 53), the pre-indication location shall be calculated as follows:
If  and

Then



Figure 53: Pre-indication location derived from MRSP speed increase

T_preindication is defined as a fixed value (refer to A.3.1).
#ANALYSE-VALUNISIG-4478#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007426#REF# 3.13.9.5.7
T_preindication is defined as a fixed value (refer to A.3.1).
realised by: #REQ-UNISIG-SUB026-007423#REF#

#REQ-UNISIG-SUB026-007428#REF# 3.13.9.5.8
For the EOA, the on-board shall calculate its pre-indication location in the same way as for an EBD based target, except that the formulas to
calculate the distance between the location of the Indication supervision limit and the SBD shall be:




With  if the GUI curve is inhibited

Or if the GUI curve is enabled
realised by: #REQ-UNISIG-SUB026-007427#REF#

#REQ-UNISIG-SUB026-007427#REF# 3.13.9.5.8 #REQ-UNISIG-SUB026-007428#REF#
For the EOA, the on-board shall calculate its pre-indication location in the same way as for an EBD based target, except that the formulas to
calculate the distance between the location of the Indication supervision limit and the SBD shall be:




With  if the GUI curve is inhibited

Or if the GUI curve is enabled


Clarification:
Depending on the target speed the correct value for T_bs1 (T_bs1_cm0 or T_bs1_cmt) shall be used in the calculation.
Note:
In the currrent context, the target speed will always be 0.
#ANALYSE-VALUNISIG-4479#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F71#REF# FCT basic function Dependecy on T_preindication

#REQ-UNISIG-SUB026-007431#REF# 3.13.9.5.9
If, in exceptional situation (e.g. after a shortening of MA), the calculation described above leads to a pre-indication location in rear of the
start location of the MRSP, the condition [1] for executing speed monitoring transition (see Table 16) shall be considered as immediately
fulfilled.
#ANALYSE-VALUNISIG-4480#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007432#REF# 3.13.9.5.10
If, in exceptional situation (e.g. after a shortening of MA), the EBD, SBD or GUI speed at the start location of the MRSP is lower than the
speed of the first element of the MRSP, the condition [1] for executing speed monitoring transition (see Table 16) shall be considered as
immediately fulfilled.
#ANALYSE-VALUNISIG-4481#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007776#REF# to.3.13.9.5.13
The preindication location used for the transitions between types of speed and distance monitoring (see 3.13.10.6) shall be defined as the
preindication location, of which the location is the closest to the train front, taking into account the max safe train front end for the
preindication location calculated for an EBD based target and the estimated train front end for the preindication location calculated for the
EOA.
Note: The calculation is similar to the calculation for the FLOI defined in chapter 3.13.9.3.3.9.
#ANALYSE-VALUNISIG-4482#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-0061#REF# 3.13.10.2.1
The train speed indicated to the driver shall be identical to the speed used for the speed monitoring (i.e. the estimated speed).
#TEST-VAL-SUB026-4F59#REF# FCT basic function Train state and standstill input to BC, speed output to DMI

#REQ-UNISIG-SUB026-003272#REF# to.3.13.10.2.1 #ANA-UNISIG-BrakingCurves-0002#REF#
To provide an acceptable speed display at the dmi the value of the current train speed shall be smoothed. The smoothed value shall be based on
the speed values received over a maximum of one second.
UNISIG clarification: see analysis
#TEST-VAL-SUB026-7147#REF# FCT basic function Indicated current train speed smoothed

#REQ-UNISIG-SUB026-007449#REF# 3.13.10.2.3
If there is no on-board interface with the service brake or if the use of the service brake command is not allowed by a National Value (only in
Target speed monitoring), whenever a service brake command is specified, the emergency brake command shall be triggered instead.
realised by: #REQ-UNISIG-SUB026-007450:01#REF#

#REQ-UNISIG-SUB026-007450:01#REF# 3.13.10.2.3 #REQ-UNISIG-SUB026-007449#REF#
If there is no on-board interface with the service brake or if the use of the service brake command is not allowed by a National Value (only in
Target speed monitoring), whenever a service brake command is specified, the emergency brake command shall be triggered instead.

Clarification:
If the National Value changes from allowed to not allowed while the service brake command is already active in Target speed monitoring, the
emergency brake command shall be triggered and the service brake command shall remain active until the revocation condition for the srevice
brake command is met.

If the service brake command is already active when entering Target speed monitoring (and the National Value disallows the use of the service
brake in Target speed monitoring), the service brake command shall remain active until the revocation condition for the service brake command is
met (see 3.13.10.6.2.1).
UNISIG clarification:
A change of  
Q_NVSBTSMPERM from true to false during an active SB in TSM doesn't lead to a revocation of this SB.
TEST APPROACH:
The following aspects regarding correct provisioning of input information (NV, configuration) to BC module have been identified:
1) Q_NVSRBKTRG=0
1.1) Q_NVEMRRLS=0
1.2) Q_NVEMRRLS=1
2) no SB interface
2.1) Q_NVEMRRLS=0
2.2) Q_NVEMRRLS=1
The following additional aspects regarding integration to other modules are identified:
3) DMI
4) JRU
#TEST-VAL-SUB026-5232#REF# FCT 1.1 Speed supervision Q_NVSRBKTRG=0 Q_NVEMRRLS=0
#TEST-VAL-SUB026-5240#REF# FCT 1.2 Speed supervision Q_NVSRBKTRG=0 Q_NVEMRRLS=1
#TEST-VAL-SUB026-5233#REF# FCT 2.1 Speed supervision no on-board interface with the service brake Q_NVEMRRLS=0
#TEST-VAL-SUB026-3148#REF# FCT 2.2 Speed supervision no on-board interface with the service brake Q_NVEMRRLS=1
#TEST-VAL-SUB026-2070#REF# FCT 3, 4 , CFX00041799 EB indication to MMI/JRU if EB applied due to missing interface to SB

#REQ-UNISIG-SUB026-007452#REF# 3.13.10.2.4
The emergency brake command, which is triggered instead of the service brake command when an SBI supervision limit is exceeded, shall be revoked
according to the requirements specified for the revocation of service brake command, unless the emergency brake command has been also triggered
due to an EBI supervision limit. In such case, the condition for revoking the emergency brake command due to EBI supervision limit shall
prevail.
realised by: #REQ-UNISIG-SUB026-007451#REF#

#REQ-UNISIG-SUB026-007451#REF# 3.13.10.2.4 #REQ-UNISIG-SUB026-007452#REF#
The emergency brake command, which is triggered instead of the service brake command when an SBI supervision limit is exceeded, shall be revoked
according to the requirements specified for the revocation of service brake command, unless the emergency brake command has been also triggered
due to an EBI supervision limit. In such case, the condition for revoking the emergency brake command due to EBI supervision limit shall
prevail.
Clarification:
If the National Value changes from not allowed to allowed while the emergency brake command, which is triggered instead of the service brake
command, is active, the service brake command shall be triggered and the emergency brake command shall remain active until the revocation
condition for the service brake command is met.
TEST APPROACH:
The following aspects have been identified:
1) Q_NVSRBKTRG=0
1.1) Q_NVEMRRLS=0
1.2) Q_NVEMRRLS=1
2) no SB interface
2.1) Q_NVEMRRLS=0
2.2) Q_NVEMRRLS=1
#ANALYSE-VALUNISIG-4483#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5232#REF# FCT 1.1 Speed supervision Q_NVSRBKTRG=0 Q_NVEMRRLS=0
#TEST-VAL-SUB026-5240#REF# FCT 1.2 Speed supervision Q_NVSRBKTRG=0 Q_NVEMRRLS=1
#TEST-VAL-SUB026-5233#REF# FCT 2.1 Speed supervision no on-board interface with the service brake Q_NVEMRRLS=0
#TEST-VAL-SUB026-3148#REF# FCT 2.2 Speed supervision no on-board interface with the service brake Q_NVEMRRLS=1

#REQ-DESIGN-CR-0118#REF# 3.13.10.2.6
In level 2/3: Train trip shall be initiated if the on-board equipment detects that the minimum safe front end has passed the EOA/LOA location.
#TEST-VAL-SUB026-3600#REF# EET CFX00035058 Trip Auslösung bei erreichen minimum safe front end LOA
#TEST-VAL-SUB026-3159#REF# FCT basic function Transition to TR at EOA/LOA

#REQ-DESIGN-CR-0119#REF# 3.13.10.2.7
In Level 1: Train Trip shall be initiated if the on-board equipment detects that the minimum safe antenna position (calculated by subtracting
distance between active Eurobalise antenna and the front end of the train from the min safe front end position) has passed the EOA/LOA location.
#TEST-VAL-SUB026-4588#REF# FCT EoA!=SvL EoA supervision - MA with OL on board FS/L1
#TEST-VAL-SUB026-4977#REF# FCT EoA=SvL Check table 4.6.2 - OS->TR - TransitionId[12]
#TEST-VAL-SUB026-4H16#REF# FCT LoA LoA supervision - OS/L1

#REQ-UNISIG-SUB026-007456#REF# 3.13.10.3.1
The on-board equipment shall display the Permitted speed.
#ANALYSE-VALUNISIG-4484#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5230#REF# FCT basic function Ceiling supervision limits based on MRSP

#REQ-UNISIG-SUB026-007457#REF# 3.13.10.3.2
When the supervision status is Overspeed, Warning or Intervention, the on-board equipment shall display the SBI speed (i.e. the FLOI speed).
Requirements for Ceiling speed monitoring
#ANALYSE-VALUNISIG-4485#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5230#REF# FCT basic function Ceiling supervision limits based on MRSP

#REQ-UNISIG-SUB026-007459#REF# 3.13.10.3.3
The on-board shall compare the estimated speed with the ceiling supervision limits defined in section 3.13.9.2 and shall trigger/revoke commands
to the train interface (service brake if implemented or emergency brake) and supervision statuses as described in Table 5 and Table 6.
Requirements for Ceiling speed monitoring
#DSC-UNISIG-SUB026-003293#REF#

Table 5: triggering of Train Interface commands and supervision statuses in ceiling speed monitoring #DSC-UNISIG-SUB026-003295#REF#
Table 6: Revocation of Train Interface commands and supervision statuses in ceiling speed monitoring
realised by: #REQ-UNISIG-SUB026-007458#REF#

#REQ-UNISIG-SUB026-007458#REF# 3.13.10.3.3 #REQ-UNISIG-SUB026-007046#REF#
#REQ-UNISIG-SUB026-007459#REF#
The on-board shall compare the estimated speed with the ceiling supervision limits defined in section 3.13.9.2 and shall trigger/revoke commands
to the train interface (service brake if implemented or emergency brake) and supervision statuses as described in Table 5 and Table 6.

Table 5: triggering of Train Interface commands and supervision statuses in ceiling speed monitoring


Table 6: Revocation of Train Interface commands and supervision statuses in ceiling speed monitoring
Requirements for Ceiling speed monitoring
#ANALYSE-VALUNISIG-4486#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5214#REF# EET CFX00041535 Evaluation of Q_NVEMRRLS=0 - train data not available (SR->SH)
#TEST-VAL-SUB026-5215#REF# EET CFX00041535 Evaluation of Q_NVEMRRLS=0 - train data not available (SB->SH)
#TEST-VAL-SUB026-5216#REF# EET CFX00041535 Evaluation of Q_NVEMRRLS=0 - train data not available (FS->SH)
#TEST-VAL-SUB026-5217#REF# EET CFX00041535 Evaluation of Q_NVEMRRLS=0 - train data not available (UN->SH)
#TEST-VAL-SUB026-5218#REF# EET CFX00041535 Evaluation of Q_NVEMRRLS=0 - train data not available (OS->SH)
#TEST-VAL-SUB026-5230#REF# FCT basic function Ceiling supervision limits based on MRSP

#REQ-UNISIG-SUB026-007460#REF# 3.13.10.3.4
The on-board equipment shall execute the transitions between the different supervision statuses as described in Table 7 (see section 4.6.1 for
details about the symbols). This table takes into account the order of precedence between the supervision statuses and the possible updates of
the MRSP while in ceiling speed monitoring (e.g. when a TSR is revoked).
Requirements for Ceiling speed monitoring
#DSC-UNISIG-SUB026-003299#REF#

Table 7: Transitions between supervision statuses in ceiling speed monitoring
realised by: #REQ-UNISIG-SUB026-007461#REF#

#REQ-UNISIG-SUB026-007461#REF# 3.13.10.3.4-1 #REQ-UNISIG-SUB026-007460#REF#
#REQ-UNISIG-SUB026-007464#REF#
The on-board equipment shall execute the transitions between the different supervision statuses as described in Table 7 (see section 4.6.1 for
details about the symbols). This table takes into account the order of precedence between the supervision statuses and the possible updates of
the MRSP while in ceiling speed monitoring (e.g. when a TSR is revoked).

Table 7: Transitions between supervision statuses in ceiling speed monitoring
Requirements for Ceiling speed monitoring
#ANALYSE-VALUNISIG-4487#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5230#REF# FCT basic function Ceiling supervision limits based on MRSP

#REQ-UNISIG-SUB026-007042#REF# 3.13.10.3.5
When the speed and distance monitoring function becomes active and the ceiling speed monitoring is the first one entered, the triggering
condition t1 defined in Table 5 shall be checked in order to determine whether the Normal status applies. If it is not the case, the on-board
shall immediately set the supervision status to the relevant value, applying a transition from the Normal status according to Table 7.
Requirements for Ceiling speed monitoring
realised by: #REQ-UNISIG-SUB026-007463#REF#

#REQ-UNISIG-SUB026-007463#REF# to.3.13.10.3.5 #REQ-UNISIG-SUB026-007042#REF#
#REQ-UNISIG-SUB026-007518#REF#
When ceiling speed monitoring becomes active the triggering condition t1 defined in Table 5 shall be checked in order to determine whether the
Normal status applies. If it is not the case, the on-board shall immediately set the supervision status to the relevant value, applying a
transition from the Normal status according to Table 7.
Rel. 8.0: 
the numeration of the tables is changed

Rel. 7.1: Verallgemeinering dahingehend, dass bei Eintritt in das CSM Monitoring der Status neu zu ermitteln ist.
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4488#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5673#REF# FCT 1, 2 Speed and distance monitoring function becomes active and CSM entered

#REQ-UNISIG-SUB026-007464#REF# 3.13.10.3.6
The Indication status is not used in ceiling speed monitoring. However, in case the ceiling speed monitoring is entered and the supervision
status was previously set to Indication, the on-board equipment shall immediately execute one of the transitions from the Indication status, as
described in Table 7.
Requirements for Ceiling speed monitoring

no more information to table 7
realised by: #REQ-UNISIG-SUB026-007461#REF#

#REQ-UNISIG-SUB026-007465#REF# 3.13.10.3.7
The locations corresponding to a speed increase of the MRSP shall be supervised by the on-board equipment taking into account the min safe front
end of the train.
Requirements for Ceiling speed monitoring
#ANALYSE-VALUNISIG-4489#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5663#REF# FCT basic function Save supervision of MRSP
#TEST-VAL-SUB026-3639#REF# EET error expectation TSR in L1(Balise)/train orientation A, reset of confidence interval

#REQ-UNISIG-SUB026-007467#REF# 3.13.10.4.2
The on-board equipment shall display to the driver the information related to one target at a time: the Most Restrictive Displayed Target
(MRDT). The MRDT shall be defined as the target of which the braking to target Permitted speed supervision limit (refer to section 3.13.9.3.5),
calculated for the current position of the train, is the lowest one amongst the supervised targets:

Requirements for Target speed monitoring
realised by: #REQ-UNISIG-SUB026-007468#REF#

#REQ-UNISIG-SUB026-007468#REF# 3.13.10.4.2 #REQ-UNISIG-SUB026-007467#REF#
The on-board equipment shall display to the driver the information related to one target at a time: the Most Restrictive Displayed Target
(MRDT). The MRDT shall be defined as the target of which the braking to target Permitted speed supervision limit (refer to section 3.13.9.3.5),
calculated for the current position of the train, is the lowest one amongst the supervised targets:


Clarification:
The information related to the target, that should be displayed, are: target speed and target distance.
Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-4490#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5229#REF# FCT basic function target supervision
#TEST-VAL-SUB026-3143#REF# EET error expectation Two TSRs on board second defines MRDT - MRDT indicated on DMI
#TEST-VAL-SUB026-5235#REF# EET error expectation Display of target speed/distance and release speed in FS

#REQ-UNISIG-SUB026-007836#REF# to.3.13.10.4.2
The condition "MRDT changed" shall consider a change in the following values:
  nominal target position of MRDT
  target speed of MRDT
  type of MRDT (EOA, SvL, ...)
  release speed commanded with the MA, only if the MRDT is either the EOA or the SvL
Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-4491#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007470#REF# 3.13.10.4.2.1
Once the service brake feedback functionality is active (see Appendix A.3.10 for details), the on-board equipment shall ensure that the
displayed Permitted speed never increases, if it results from the progressive reduction of T_bs1 and T_bs2. In other terms if the Permitted
speed calculated as above has a higher value than the previously displayed value, then the previous value shall remain displayed until a further
calculated Permitted speed is lower than the displayed one.
Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-7649#REF# FCT The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#.
#TEST-VAL-SUB026-4B82#REF# FCT basic function progressive reduction of t_bs due to SB feedback being active do not lead to an increase of dispalyed permitted speed and taget distance

#REQ-UNISIG-SUB026-007469#REF# 3.13.10.4.3 #ANA-UNISIG-CR1124-0001#REF#
The on-board equipment shall display the Permitted speed, according to following formula:

UNISIG clarification: solution of UCR 1124, part 1 is to be taken over


Requirements for Target speed monitoring
realised by: #REQ-UNISIG-SUB026-007471:01#REF#

#REQ-UNISIG-SUB026-007471:01#REF# to.3.13.10.4.3 #REQ-UNISIG-SUB026-007469#REF#
#ANA-UNISIG-CR1124-0001#REF#
The on-board equipment shall display the Permitted speed, according to following formula:

UNISIG clarification: solution of UCR 1124, part 1 is to be taken over
=> the origing is replaced

Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-4492#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007472#REF# 3.13.10.4.4
When the supervision status is Overspeed, Warning or Intervention, the on-board equipment shall display the FLOI speed, according to the
following formulas:
in case of MRSP target or LOA

in case of EOA or SvL
Requirements for Target speed monitoring
realised by: #REQ-UNISIG-SUB026-007473#REF#

#REQ-UNISIG-SUB026-007473#REF# 3.13.10.4.4 #REQ-UNISIG-SUB026-007472#REF#
When the supervision status is Overspeed, Warning or Intervention, the on-board equipment shall display the FLOI speed, according to the
following formulas:
in case of MRSP target or LOA

in case of EOA or SvL


Clarification:
If no release speed is supervised, V_release shall be replaced by 0.
Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-4493#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007477#REF# 3.13.10.4.6
If the MRDT is either the EOA or the SvL, the on-board equipment shall display the release speed, if given by the trackside or calculated
on-board.
Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-4494#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5235#REF# FCT basic function Display of target speed/distance and release speed in FS

#REQ-UNISIG-SUB026-007478#REF# 3.13.10.4.7
If the MRDT is neither the EOA nor the SvL, the indicated distance to the target shall be the distance between the maximum safe front end and
the location of the Permitted speed supervision limit calculated for the target speed (see section 3.13.9.3.5 for the calculation of this
location), but limited to zero after this location is passed.
Target distance =
Requirements for Target speed monitoring
TEST APPROACH:
The following aspect has been identified:
1) display of BC output to MMI 
#ANALYSE-VALUNISIG-4495#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F84#REF# FCT 1 Display of target speed/distance in FS: target not EoA or SvL

#REQ-UNISIG-SUB026-007480#REF# 3.13.10.4.7.1
Once the service brake feedback functionality is active (see Appendix A.3.10 for details), the on-board equipment shall ensure that the
displayed target distance never increases, if it results from the progressive reduction of T_bs1 and T_bs2. In other terms if the target
distance calculated as above has a higher value than the previously displayed value, then the previous value shall remain displayed until a
further calculated target distance is lower than the displayed one.
Requirements for Target speed monitoring
TEST APPROACH:
The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#. 
#ANALYSE-VALUNISIG-7650#REF# FCT The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#.
#TEST-VAL-SUB026-4B82#REF# FCT basic function progressive reduction of t_bs due to SB feedback being active do not lead to an increase of dispalyed permitted speed and taget distance

#REQ-UNISIG-SUB026-007481#REF# 3.13.10.4.8
If the MRDT is either the EOA or the SvL, the indicated distance to the target shall be calculated as follows:
Target distance =
Requirements for Target speed monitoring
TEST APPROACH:
The following aspect has been identified:
1) display of BC output to MMI 
#ANALYSE-VALUNISIG-4496#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5235#REF# FCT basic function Display of target speed/distance and release speed in FS

#REQ-UNISIG-SUB026-007484#REF# 3.13.10.4.9 #REQ-UNISIG-SUB026-007045#REF#
The on-board shall consider the service brake command as available for use unless:
a)	The service brake command is not implemented, OR
b)	The national value inhibits its use.
Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-4497#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5233#REF# FCT a Speed supervision no on-board interface with the service brake Q_NVEMRRLS=0
#TEST-VAL-SUB026-5232#REF# FCT b Speed supervision Q_NVSRBKTRG=0 Q_NVEMRRLS=0

#REQ-UNISIG-SUB026-007486:01#REF# 3.13.10.4.10
The on-board equipment shall compare the estimated speed and train position with the ceiling and braking to target supervision limits and shall
trigger/revoke commands to the train interface (traction cut-off if implemented, service brake if available for use or emergency brake) and
supervision statuses, as described in Table 8 and Table 10 (for target related to a MRSP speed decrease or LOA), and as described in Table 9 and
Table 11 (for target EOA/SvL with release speed).
Requirements for Target speed monitoring
#DSC-UNISIG-SUB026-003341#REF#

Table 8: Triggering of Train Interface commands and supervision statuses in target speed monitoring, MRSP target or LOA #DSC-UNISIG-SUB026-003344#REF#
Figure 55: Triggering of Train Interface commands and supervision statuses in target speed monitoring, MRSP target or LOA (number in circle corresponds with the equivalent triggering condition in Table 8) #DSC-UNISIG-SUB026-003346#REF#
Table 9: Triggering of Train Interface commands and supervision statuses in target speed monitoring, EOA/SvL with release speed #DSC-UNISIG-SUB026-003349#REF#
Figure 56: Triggering of Train Interface commands and supervision statuses in target speed monitoring, EOA/SvL with release speed (number in circle corresponds with equivalent triggering condition in Table 9) #DSC-UNISIG-SUB026-003355#REF#
Table 10: Revocation of Train Interface commands and supervision statuses in target speed monitoring, MRSP target or LOA #DSC-UNISIG-SUB026-003357:01#REF#
Table 11: Revocation of Train Interface commands and supervision statuses in target speed monitoring, EOA/SvL with release speed
realised by: #REQ-UNISIG-SUB026-007487#REF#
realised by: #REQ-UNISIG-SUB026-007489#REF#
realised by: #REQ-UNISIG-SUB026-007493#REF#
realised by: #REQ-UNISIG-SUB026-007494:01#REF#

#REQ-UNISIG-SUB026-007487#REF# 3.13.10.4.10.table.8 #REQ-UNISIG-SUB026-007486:01#REF#
The on-board equipment shall compare the estimated speed and train position with the ceiling and braking to target supervision limits and shall
trigger/revoke commands to the train interface (traction cut-off if implemented, service brake if available for use or emergency brake) and
supervision statuses, as described in Table 8 and Table 10 (for target related to a MRSP speed decrease or LOA), and as described in Table 9 and
Table 11 (for target EOA/SvL with release speed).



Table 8: Triggering of Train Interface commands and supervision statuses in target speed monitoring, MRSP target or LOA

Clarification/Correction:
In the column "TI Command triggered" the command "TCO" is also triggered for rows "t10" through "t14"
and the command "SB" is also triggered for rows "t13" and "t14". This leads to a similar behavior for the TI
Commands in TSM as in CSM (see 3.13.10.3.3) and leads to the same set of active TI Commands when the conditions are triggered one after the
other (e.g. first t7, then t10, at last t13) or when the last condition is triggered at once (e.g t13).
see also figure 55 in Subset 26

Requirements for Target speed monitoring
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4498#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5678#REF# FCT 1, 2 Transitions between supervision statuses in target speed monitoring, MRSP/LOA

#REQ-UNISIG-SUB026-007489#REF# 3.13.10.4.10.table.9 #REQ-UNISIG-SUB026-007486:01#REF#
The on-board equipment shall compare the estimated speed and train position with the ceiling and braking to target supervision limits and shall
trigger/revoke commands to the train interface (traction cut-off if implemented, service brake if available for use or emergency brake) and
supervision statuses, as described in Table 8 and Table 10 (for target related to a MRSP speed decrease or LOA), and as described in Table 9 and
Table 11 (for target EOA/SvL with release speed).





Table 9: Triggering of Train Interface commands and supervision statuses in target speed monitoring, EOA/SvL with release speed

Clarification/Correction:
In the column "TI Command triggered" the command "TCO" is also triggered for rows "t10" through "t14"
and the command "SB" is also triggered for rows "t13" and "t14". This leads to a similar behavior for the TI
Commands in TSM as in CSM (see 3.13.10.3.3) and leads to the same set of active TI Commands when the conditions are triggered one after the
other (e.g. first t7, then t10, at last t13) or when the last condition is triggered at once (e.g t13).
see also figure 56 in Subset 26

Requirements for Target speed monitoring
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4499#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5679#REF# FCT 1, 2 Transitions between supervision statuses in target speed monitoring, EoA/SvL

#REQ-UNISIG-SUB026-007493#REF# 3.13.10.4.10.table.10 #REQ-UNISIG-SUB026-007046#REF#
#REQ-UNISIG-SUB026-007486:01#REF#
The on-board equipment shall compare the estimated speed and train position with the ceiling and braking to target supervision limits and shall
trigger/revoke commands to the train interface (traction cut-off if implemented, service brake if available for use or emergency brake) and
supervision statuses, as described in Table 8 and Table 10 (for target related to a MRSP speed decrease or LOA), and as described in Table 9 and
Table 11 (for target EOA/SvL with release speed).

Table 10: Revocation of Train Interface commands and supervision statuses in target speed monitoring, MRSP target or LOA


Clarification:
The condition "V_target ≠ 0" was removed in row r1 from "EB" in column "TI Command revoked" and in rows r1 and r2
from "Intervention status" in column "Supervision status revoked", because this condition was used inconsistent and is
contained in r0 (standstill).
The row r2 was divided into rows r2a and r2b to reflect the different behavior with change of displayed target and without  (see note
3.13.10.4.14).
Requirements for Target speed monitoring
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4500#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5678#REF# FCT 1, 2 Transitions between supervision statuses in target speed monitoring, MRSP/LOA

#REQ-UNISIG-SUB026-007494:01#REF# 3.13.10.4.10.table.11 #REQ-UNISIG-SUB026-007046#REF#
#REQ-UNISIG-SUB026-007486:01#REF#
The on-board equipment shall compare the estimated speed and train position with the ceiling and braking to target supervision limits and shall
trigger/revoke commands to the train interface (traction cut-off if implemented, service brake if available for use or emergency brake) and
supervision statuses, as described in Table 8 and Table 10 (for target related to a MRSP speed decrease or LOA), and as described in Table 9 and
Table 11 (for target EOA/SvL with release speed).



Table 11: Revocation of Train Interface commands and supervision statuses in target speed monitoring, EOA/SvL with release speed

Clarification:
The condition "V_target ≠ 0" was removed in row r1 from "EB" in column "TI Command revoked" and in rows r1 and r2
from "Intervention status" in column "Supervision status revoked", because this condition was used inconsistent and is
contained in r0 (standstill).
The row r0, r1 and r2 were divided into rows r0a, r0b, r1a, r2a and r1b, r2b to reflect the different behavior with change of displayed target
and without (see note 3.13.10.4.14).
Requirements for Target speed monitoring
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4501#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5679#REF# FCT 1, 2 Transitions between supervision statuses in target speed monitoring, EoA/SvL

#REQ-UNISIG-SUB026-007495#REF# 3.13.10.4.13
In case of target EOA/SvL without any supervised release speed, the Table 9 and Table 11 shall be applied, by substituting V_release with the
value 0.
Requirements for Target speed monitoring
#ANALYSE-VALUNISIG-4502#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007496#REF# 3.13.10.4.15
The on-board equipment shall execute the transitions between the different supervision statuses as described in Table 12 (see section 4.6.1 for
details about the symbols). This table takes into account the order of precedence between the supervision statuses and the possible changes of
the displayed target (MRDT), e.g. when the list of supervised targets is updated.
Requirements for Target speed monitoring
#DSC-UNISIG-SUB026-003365#REF#

Table 12: Transitions between supervision statuses in target speed monitoring
realised by: #REQ-UNISIG-SUB026-007497:01#REF#

#REQ-UNISIG-SUB026-007497:01#REF# 3.13.10.4.15 #REQ-UNISIG-SUB026-007496#REF#
The on-board equipment shall execute the transitions between the different supervision statuses as described in Table 12 (see section 4.6.1 for
details about the symbols). This table takes into account the order of precedence between the supervision statuses and the possible changes of
the displayed target (MRDT), e.g. when the list of supervised targets is updated.



Table 12: Transitions between supervision statuses in target speed monitoring
Clarification:
The conditions
- r0, r1  correspondend with table 10,
- r0a, r0b, r1a, r1b, r2a, r2b correspondend with table 11
- r2a, r2b correspondend with table 10 and 11
to clarify the reactions concerning the condition "only in case of change of displayed target".
Requirements for Target speed monitoring
TEST APPROACH:
The following aspects have been identified, regarding BC-MMI integration:
1) EoA/SvL
2) MRSP/LOA
#ANALYSE-VALUNISIG-4503#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5679#REF# FCT 1 Transitions between supervision statuses in target speed monitoring, EoA/SvL
#TEST-VAL-SUB026-5678#REF# FCT 2 Transitions between supervision statuses in target speed monitoring, MRSP/LOA

#REQ-UNISIG-SUB026-007043#REF# 3.13.10.4.16
When the speed and distance monitoring function becomes active and the target speed monitoring is the first one entered, the triggering
conditions t1 and t2 defined in Table 8 or Table 9 shall be checked in order to determine whether the Normal status applies. If it is not the
case, the on-board shall immediately set the supervision status to the relevant value, applying a transition from the Normal status according to
Table 12.
Requirements for Target speed monitoring
realised by: #REQ-UNISIG-SUB026-007499#REF#

#REQ-UNISIG-SUB026-007499#REF# 3.13.10.4.16 #REQ-UNISIG-SUB026-007043#REF#
#REQ-UNISIG-SUB026-007518#REF#
When target speed monitoring becomes active the triggering conditions t1 and t2 defined in Table 8 or Table 9 shall be checked in order to
determine whether the Normal status applies. If it is not the case, the on-board shall immediately set the supervision status to the relevant
value, applying a transition from the Normal status according to Table 12.
Rel. 7.1: Verallgemeinering dahingehend, dass bei Eintritt in das TSM Monitoring der Status neu zu ermitteln ist.
TEST APPROACH:
The following aspects have been identified:
1) TSM entered, PIM
1.1) DMI indications
1.2) TIU interface commands
2) TSM entered, no PIM
2.1) DMI indications
2.2) TIU interface commands
#ANALYSE-VALUNISIG-4504#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5674#REF# FCT 1.1, 1.2 Speed and distance monitoring function becomes active and TSM(PIM) entered
#TEST-VAL-SUB026-5675#REF# FCT 2.1, 2.2 Speed and distance monitoring function becomes active and TSM(no PIM) entered

#REQ-UNISIG-SUB026-007501#REF# 3.13.10.5.1
The on-board equipment shall display the Release speed.
Requirements for release speed monitoring
#ANALYSE-VALUNISIG-4505#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5235#REF# FCT basic function Display of target speed/distance and release speed in FS

#REQ-UNISIG-SUB026-007502#REF# 3.13.10.5.2
The on-board equipment shall display the target distance, in the same way as for target speed monitoring.
Requirements for release speed monitoring
#TEST-VAL-SUB026-5235#REF# FCT basic function Display of target speed/distance and release speed in FS

#REQ-UNISIG-SUB026-007500#REF# 3.13.10.5.3
The braking to target Permitted speed supervision limit related to the MRDT (i.e. EOA or SvL), as calculated in target speed monitoring from the
EBD or SBD, shall also be displayed.
Requirements for release speed monitoring
realised by: #REQ-UNISIG-SUB026-007503#REF#

#REQ-UNISIG-SUB026-007503#REF# 3.13.10.5.3 #REQ-UNISIG-SUB026-007500#REF#
The braking to target Permitted speed supervision limit related to the MRDT (i.e. EOA or SvL), as calculated in target speed monitoring from the
EBD or SBD, shall also be displayed.

Clarification:
The permitted speed according to 3.13.10.4.3 shall be displayed.
Requirements for release speed monitoring
#ANALYSE-VALUNISIG-4506#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5666#REF# FCT basic function Indication of permitted speed in CSM/PIM/TSM/RSM

#REQ-UNISIG-SUB026-007505#REF# 3.13.10.5.4 #REQ-UNISIG-SUB026-007379#REF#
The on-board equipment shall compare the estimated speed with the release speed and shall trigger/revoke commands to the train interface
(emergency brake) and supervision statuses as described in Table 13 and Table 14.

#DSC-UNISIG-SUB026-003379#REF#

Table 13: Triggering of Train Interface commands and supervision statuses in release speed monitoring #DSC-UNISIG-SUB026-003381#REF#
Table 14: Revocation of Train Interface commands and supervision statuses in release speed monitoring
realised by: #REQ-UNISIG-SUB026-007504#REF#

#REQ-UNISIG-SUB026-007504#REF# 3.13.10.5.4-2 #REQ-UNISIG-SUB026-007505#REF#
The on-board equipment shall compare the estimated speed with the release speed and shall trigger/revoke commands to the train interface
(emergency brake) and supervision statuses as described in Table 13 and Table 14.

Table 13: Triggering of Train Interface commands and supervision statuses in release speed monitoring


Table 14: Revocation of Train Interface commands and supervision statuses in release speed monitoring
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4507#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5677#REF# FCT 1, 2 Transitions between supervision statuses in release speed monitoring

#REQ-UNISIG-SUB026-007506#REF# 3.13.10.5.5
The on-board equipment shall execute the transitions between the different supervision statuses as described in Table 15 (see section 4.6.1 for
details about the symbols). This table takes into account the order of precedence between the supervision statuses and the possible updates of
the release speed while in release speed monitoring.

#DSC-UNISIG-SUB026-003385#REF#

Table 15: Transitions between supervision statuses in release speed monitoring
realised by: #REQ-UNISIG-SUB026-007507#REF#

#REQ-UNISIG-SUB026-007507#REF# 3.13.10.5.5-1 #REQ-UNISIG-SUB026-007506#REF#
#REQ-UNISIG-SUB026-007510#REF#
The on-board equipment shall execute the transitions between the different supervision statuses as described in Table 15 (see section 4.6.1 for
details about the symbols). This table takes into account the order of precedence between the supervision statuses and the possible updates of
the release speed while in release speed monitoring.



Table 15: Transitions between supervision statuses in release speed monitoring
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4508#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5677#REF# FCT 1 Transitions between supervision statuses in release speed monitoring
#TEST-VAL-SUB026-3820#REF# FCT 2 Release speed calculation depending on V_RELEASEOL and V_RELEASEDP

#REQ-UNISIG-SUB026-007047#REF# 3.13.10.5.6
When the speed and distance monitoring function becomes active and the release speed monitoring is the first one entered, the triggering
condition t1 defined in Table 13 shall be checked in order to determine whether the Indication status applies. If it is not the case, the
on-board shall immediately set the supervision status to the Intervention status, applying a transition from the Indication status according to
Table 15.
realised by: #REQ-UNISIG-SUB026-007509#REF#

#REQ-UNISIG-SUB026-007509#REF# 3.13.10.5.6 #REQ-UNISIG-SUB026-007047#REF#
#REQ-UNISIG-SUB026-007518#REF#
When the release speed monitoring function becomes active the triggering condition t1 defined in Table 11 shall be checked in order to determine
whether the Indication status applies. If it is not the case, the on-board shall immediately set the supervision status to the Intervention
status, applying a transition from the Indication status according to Table 13.
Rel. 7.1: Verallgemeinering dahingehend, dass bei Eintritt in das RSM der Status neu zu ermitteln ist.
TEST APPROACH:
The following aspects have been identified:
1) DMI indications
2) TIU interface commands
#ANALYSE-VALUNISIG-4509#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5676#REF# FCT 1, 2 Speed and distance monitoring function becomes active and RSM entered

#REQ-UNISIG-SUB026-007510#REF# 3.13.10.5.7
The Normal, Warning and Overspeed statuses are not used in release speed monitoring. However, in case the release speed monitoring is entered
and the supervision status was previously set to Normal, Warning or Overspeed, the on-board equipment shall immediately execute one of the
transitions from respectively the Normal, Warning or Overspeed status, as described in Table 15.
realised by: #REQ-UNISIG-SUB026-007507#REF#

#REQ-UNISIG-SUB026-007512#REF# 3.13.10.6.1
The transitions between the Ceiling speed monitoring, the Target speed monitoring and the Release speed monitoring shall be achieved as
described in the Table 16:

#DSC-UNISIG-SUB026-003395#REF#

Table 16: Transitions between types of Speed and distance monitoring
realised by: #REQ-UNISIG-SUB026-8100#REF#

#REQ-UNISIG-SUB026-8100#REF# to.3.13.10.6.1 #REQ-UNISIG-SUB026-007512#REF#
The transitions between the Ceiling speed monitoring, the Target speed monitoring (including substate PIM) and the Release speed monitoring
shall be achieved as described in the Table 16:



Table 16: Transitions between types of Speed and distance monitoring
The transition for condition [5] of the original requirement was included in the transition for condition [2]. Part of the transition for
condition [4] in the original requirement is already included in the transition for condition [1].
#ANALYSE-VALUNISIG-4510#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5246#REF# FCT basic function Transition between CSM, PIM/TSM and RSM

#REQ-UNISIG-SUB026-007514#REF# 3.13.10.6.2
If a transition of speed and distance monitoring occurs while a brake command is already applied, the concerned command shall be maintained
until the revocation condition, if specified for the newly entered speed and distance monitoring, is fulfilled.
#ANALYSE-VALUNISIG-4511#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-7170#REF# EET CFX00178729 Outage of NTC in level transition announcement phase (ToP NTC, L0)
#TEST-VAL-SUB026-7171#REF# EET CFX00178729 Outage of NTC in level transition announcement phase (ToP NTC(1), NTC(2))
#TEST-VAL-SUB026-8161#REF# EET CFX00178729 brakes applied, switch to a mode where there's no MRSP
#TEST-VAL-SUB026-8302#REF# EET CFX00178729 TCO, SB, EB applied when switching to NTC (Q_NVEMMRLS = 0)
#TEST-VAL-SUB026-5667#REF# FCT EB Brake handling when switching between CSM and RSM
#TEST-VAL-SUB026-5668#REF# FCT SB Entering TSM with active SB

#REQ-UNISIG-SUB026-007516#REF# 3.13.10.6.3
If a transition from target speed monitoring to ceiling speed or release speed monitoring occurs while a traction cut-off command is already
applied, the traction cut-off command shall be immediately revoked.
#ANALYSE-VALUNISIG-4512#REF# FCT The functionality is realised by BC. Verification takes place via BC module test. L211
#TEST-VAL-SUB026-5669#REF# FCT basic function Entering CSM/RSM with active TCO

#REQ-UNISIG-SUB026-007517#REF# 3.13.10.6.4
If a transition from target speed monitoring to release speed monitoring occurs while a service brake command is already applied, the service
brake command shall be immediately revoked.
#ANALYSE-VALUNISIG-4513#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-5246#REF# FCT basic function Transition between CSM, PIM/TSM and RSM

#REQ-UNISIG-SUB026-007518#REF# 3.13.10.6.5
On executing a transition between types of speed and distance monitoring, the supervision status shall be determined according to the
requirements specified for the newly entered speed and distance monitoring.
is realized thorugh the specifying req. to 3.13.10.3.5, 3.13.10.4.16 and 3.13.10.5.6
realised by: #REQ-UNISIG-SUB026-007463#REF#
realised by: #REQ-UNISIG-SUB026-007499#REF#
realised by: #REQ-UNISIG-SUB026-007509#REF#

#REQ-UNISIG-SUB026-008126#REF# 3.13.10- #REQ-SRS-004372#REF#
#REQ-UNISIG-SUB026-008094#REF#
The brake models shall be parametrizable.

The relevant parametrizable values are defined in chapter 3.13 and A3.7-A3.10.
TEST APPROACH:
The following aspects have been identified:
1) Kn +/-
2) pre-programmed brake model parameters: EB/SB deceleration models (speed limit, speed dependent deceleration), Kdry, Kwet, T_brake_emergency,
T_brake_service
3) Normal service brake model
4) T_traction_cut_off
5) Nominal rotating mass
6) Limits for conversion brake model selection (brake position, brake percentage, maximum train length, maximum train speed) 
6.1) default UNISIG values
6.2) non-UNISIG values
7) parameters defined in A3.7
7.1) default UNISIG values
7.2) non-UNISIG values
8) parameters defined in A3.8
8.1) default UNISIG values
8.2) non-UNISIG values 
9) parameters defined in A3.9
9.1) default UNISIG values
9.2) non-UNISIG values 
10) parameters defined in A3.10
10.1) UNISIG values
10.2) non-UNISIG values

Note 1: Aspect 6.1 is tested at the appropiate requirement (REQ-UNISIG-SUB026-007088).
Note1: For aspects 7, 8 and 9, the dependency on Passenger train (PP), Freight train G (FG) and Freight train P (FP) are considered.
Note2: for aspect 10, the two types of feedback from the service brake are considered: main brake pipe pressure and brake cylinder pressure.
#TEST-VAL-SUB026-4F83#REF# BVA 1 (in range values) Normal SB brake model correction factors for gradient Kn+/-
#TEST-VAL-SUB026-4F85#REF# BVA 1 (min/max values) Normal SB brake model correction factors for gradient Kn+/-: min/max values
#TEST-VAL-SUB026-4F92#REF# BVA 2 Pre-programmed brake model parameters: EB/SB deceleration models, Kdry, Kwet, T_brake_emergency/_service
#TEST-VAL-SUB026-4F89#REF# BVA 3 Normal Service Brake Model
#TEST-VAL-SUB026-4F77#REF# BVA 5 Value range for nominal rotating mass: min, max, unknown
#TEST-VAL-SUB026-4F94#REF# BVA 6.2 Validity limits for selection of conversion model: decreased non-UNISIG intervals
#TEST-VAL-SUB026-4F82#REF# FCT 7.1, 8.1 (PP), 9.1 (PP) Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values
#TEST-VAL-SUB026-4F73#REF# FCT 7.2 Configuration change of fixed values taken into account in calculation of the basic deceleration
#TEST-VAL-SUB026-3B68#REF# FCT 8.1 (FG), 9.1 (FG) Parameters defined in A.3.8, A.3.9 for Freight train in G: UNISIG values
#TEST-VAL-SUB026-3B67#REF# FCT 8.1 (FP), 9.1 (FP) Parameters defined in A.3.8, A.3.9 for Freight train in P: UNISIG values
#TEST-VAL-SUB026-4F74#REF# FCT 8.2 (FG), 9.2 (FG) Configuration change of values for calculation of EB/SB equivalent time for freight trains in P
#TEST-VAL-SUB026-3B93#REF# FCT 8.2 (FP), 9.2 (FP) Configuration change of values for calculation of EB/SB equivalent time for freight trains in P
#TEST-VAL-SUB026-4F72#REF# FCT 8.2 (PP), 9.2 (PP) Configuration change of values for calculation of EB/SB equivalent time for passenger trains
#TEST-VAL-SUB026-4B79#REF# FCT 10.1 (brake cylinder pressure) conversion of brake cylinder pressure
#TEST-VAL-SUB026-4B78#REF# FCT 10.1 (main brake pipe pressure) once T_bs is locked, it remains so, even if pressure on main brake pipe increases
#TEST-VAL-SUB026-4B89#REF# FCT 10.2 (brake cylinder pressure) Configuration change of SB feedback parameter k1 taken into consideration
#TEST-VAL-SUB026-4B88#REF# FCT 10.2 (main brake pipe pressure) Configuration change of SB feedback parameters taken into consideration at BC input (main brake pipe configured)
#TEST-VAL-SUB026-4F76#REF# BVA 4 (max value - 40950ms) Value range for T_tractio_cut_off: max value
#TEST-VAL-SUB026-4F75#REF# BVA 4 (min value - 0ms) Value range for T_tractio_cut_off: min value
#TEST-VAL-SUB026-4F95#REF# EET error expectation Validity limits for selection of conversion model: increased non-UNISIG intervals

Chapter 3.14

#REQ-UNISIG-SUB026-0086#REF# 3.14.1.2
In case only the application of  (the non-vital) service brake has been commanded and the service brake fails to be applied, the emergency brake
command shall be given.
TEST APPROACH:
The following aspects have been identified:
1) speed monitoring (refer #REQ-UNISIG-SUB026-010626#REF#)
2) linking
3) runaway movement
4) PT supervision
5) STM ordered SB (refer #REQ-UNISIG-SUB026-010626#REF#)
6) mode not acknowledged
7) level not acknowledged
8) radio link supervision
9) data entry supervision
10) unsupported level
11) data inconsistency 
12) text message not acknowledged
#TEST-VAL-SUB026-3160#REF# FCT 2 SB Supervision by odometric data
#TEST-VAL-SUB026-7158#REF# FCT 3, 4, 12 Service brake supervision for runaway movement, D_NVPOTRP and text message
#TEST-VAL-SUB026-7157#REF# FCT 6 Service brake supervision for speed supervision and mode acknowledgement
#TEST-VAL-SUB026-7156#REF# FCT 7 Service brake supervision for STM(STM-128) and level acknowledgement
#TEST-VAL-SUB026-3163#REF# FCT 8 SB due to radio link supervision
#TEST-VAL-SUB026-4026#REF# FCT 9 Change Staff Responsible Speed / Staff Responsible Distance via DMI possible at standstill only
#TEST-VAL-SUB026-3841#REF# FCT 10 Brake command due to transition to L3 and brake release after execution of LTO L2
#TEST-VAL-FFFIS_JRU-0007#REF# FCT 11 JRU recording limit target distance, brake reason and INTERNAL FIXED TEXT MESSAGES
#TEST-VAL-SUB026-8221#REF# EET error expectation SB applied due to two reason, one with SB supervision one without SB supervision

#REQ-UNISIG-SUB026-010626#REF# to.3.14.1.2 #ANA-UNISIG-SUB035-Chapter7-0015:01#REF#
Exception to #REQ-UNISIG-SUB026-0086#REF#:
The application of the service brake shall not be supervised, when the
- service brake commands due to speed and distance monitoring
OR
- service brake commands from a STM.
UNISIG clarification: 
When a SB is applied due to speed supervision, SB should not be  supervised.
The same is also applies for SB commanded by a STM.
TEST APPROACH:
The following aspects have been identified:
1) speed monitoring
2) STM ordered SB
#TEST-VAL-SUB026-7157#REF# FCT 1 Service brake supervision for speed supervision and mode acknowledgement
#TEST-VAL-SUB026-7156#REF# FCT 2 Service brake supervision for STM(STM-128) and level acknowledgement

#REQ-UNISIG-SUB026-0087#REF# 3.14.1.3 #REQ-DESIGN-CR-0179:01#REF#
If the emergency brake command was triggered due to a trip condition (see chapter 4) the emergency brake command shall be released at standstill
and after driver acknowledgement of the trip condition.
#TEST-VAL-SUB026-3161#REF# FCT basic function EB revocation in TR
#TEST-VAL-SUB026-3304#REF# EET error expectation Release of Emergency Brake applied for two different brake reasons

#REQ-UNISIG-SUB026-0622#REF# 3.14.1.5 #REQ-UNISIG-SUB026-010404#REF#
#REQ-UNISIG-SUB026-010405#REF#
#REQ-UNISIG-SUB026-010406#REF#
If the brake command was triggered due to roll away protection, reverse movement protection or standstill supervision the brake command shall be
released at standstill and after driver acknowledgement.
TEST APPROACH:
The following aspects have been identified:
1) Service brake
1.1) roll away protection
1.2) reverse movement protection
1.3) standstill supervision
2) Emergency brake
2.1) roll away protection
2.2) reverse movement protection
2.3) standstill supervision
#TEST-VAL-SUB026-4541#REF# FCT 1.1, 1.2, 1.3 RAP, RMP and Standstill supervision with service brake
#TEST-VAL-SUB026-4A35#REF# FCT 2.1 Supervise train movements - Roll Way Protection at mode UN
#TEST-VAL-SUB026-4A37#REF# FCT 2.2 Supervise train movements - Reverse Movement Protection at mode FS
#TEST-VAL-SUB026-3168#REF# FCT 2.3 Standstill supervision
#TEST-VAL-SUB026-3703#REF# EET CFX00032469 RAP D_NVROLL passed after fractional roll away, last section smaller than 20cm
#TEST-VAL-SUB026-3304#REF# EET error expectation Release of Emergency Brake applied for two different brake reasons

#REQ-UNISIG-SUB026-010174#REF# to.3.14.1.5
If the brake command was triggered due to roll away protection, reverse movement protection or standstill supervision the brake command shall be
released also, when the supervision is deactivated (i.e. the mode is changed).
UNISIG clarification:
A requirement for clarification for this case is necessary.
#TEST-VAL-SUB026-5792#REF# FCT basic function RMP, RAP, standstill supervision brake when switching to mode where the supervision is inactive

#REQ-DESIGN-CR-0032#REF# 3.14.1.6
If the brake command was triggered due to linking error, balise group message inconsistency or RAMS related supervision error, the brake command
shall be released at standstill.
#TEST-VAL-SUB026-3162#REF# FCT BG message inconsistency Braking because of BG-inconsistency
#TEST-VAL-SUB026-3275#REF# FCT RAMS 2 consecutive linked balise groups announced by linking not detected
#TEST-VAL-SUB026-3965#REF# EET error expectation Linking reaction for missing balise groups
#TEST-VAL-SUB026-3160#REF# FCT link error SB Supervision by odometric data

#REQ-UNISIG-SUB026-0090#REF# 3.14.1.7
If the brake command was triggered due to supervision of the safe radio connection (T_NVCONTACT) the brake command shall be released at
standstill or if a new consistent message has been received from the RBC.
#TEST-VAL-SUB026-3163#REF# FCT basic function SB due to radio link supervision
#TEST-VAL-SUB026-8272#REF# EET error expectation Revocation of brake command triggered due to supervision of the safe radio connection in RBC/RBC Handover 2 mobiles
#TEST-VAL-SUB026-8274#REF# EET error expectation Revocation and trigger T_NVCONTACT with same RBC message

#REQ-UNISIG-SUB026-3098#REF# 3.14.1.7.1 #REQ-UNISIG-SUB026-010407#REF#
If the brake command was triggered due to an overpassed reversing distance related to a reversing area or due to any further movement in the
direction opposite to the train orientation while the reversing distance is still overpassed, the brake command shall be released if the
reversing distance becomes extended so that the reversing distance is no longer overpassed, or at standstill after driver acknowledgement.
UNISIG clarification:
if obu left the the mode RV, the brake is also released
TEST APPROACH:
The following aspects have been identified:
1) brake triggered due to an over passed reversing distance related to a reversing area
1.1) reversing distance extended
1.2) driver acknowledgement
2) further movement in the direction opposite to the train orientation
2.1) reversing distance extended
2.2) driver acknowledgement
#TEST-VAL-SUB026-5626#REF# FCT 1.1 EB applied due to RV supervision released after receiving increased D_REVERS (reversing distance is no longer exceeded)
#TEST-VAL-SUB026-3580#REF# FCT 1.2 D_REVERSE supervision
#TEST-VAL-SUB026-5955#REF# FCT 2.1, 2.2 Brake release - further movement in the direction opposite to the train orientation while the reversing distance is still overpassed
#TEST-VAL-SUB026-4H83#REF# EET error expectation EB triggered by overpassing reversing distance in RV revoked after mode transition

#REQ-DESIGN-CR-0630:02#REF# to.3.14.1.7 #ANA-UNISIG-Leveltransition-0002:02#REF#
If the brake command was triggered due to transition to an unsupported level or a not available STM, the brake command shall be released
- after a transition to a supported level
OR
- after a transition to an available STM
OR
- the mode SN is left with no change of level.
TEST APPROACH:
The following aspects have been identified:
1) Precondition: brake applied due to
1.1) unsupported ETCS level
1.2) unsupported STM
1.3) unavailable STM
2) Action: level transition due to 
2.1) trackside order
2.2) driver request 
3) Result: brake released due to transition to 
3.1) supported level
3.2) available STM
3.3) other mode than SN in level STM
#TEST-VAL-SUB026-3841#REF# FCT 1.1, 2.1 Brake command due to transition to L3 and brake release after execution of LTO L2
#TEST-VAL-SUB026-3294#REF# FCT 1.2, 3.1 Level transition to unsupported Levels STM
#TEST-VAL-SUB026-3A97#REF# FCT 1.3, 2.2 Brake command triggered by a STM failure is released at standstill if the driver changes the level
#TEST-VAL-SUB026-3856#REF# FCT 3.2 Brake triggered due to transition to not supported NTC, revoked after transition to available NTC
#TEST-VAL-SUB026-7148#REF# FCT 3.3 Brake release due to leaving SN without level change
#TEST-VAL-SUB026-3A03#REF# EET error expectation Brake command triggered by a STM failure is released at standstill if level transition order is receieved

#REQ-UNISIG-SUB026-003427#REF# 3.14.1.7.2 #REQ-UNISIG-SUB026-010408#REF#
If the brake command was triggered due to change of Train Data while running (see section 5.17 procedure "Changing Train Data from sources
different from the driver”), the brake command shall be released at standstill and after driver acknowledgement.

#REQ-UNISIG-SUB026-003429#REF# 3.14.1.7.3
If the brake command was triggered due to the detection of a train movement while modifying/revalidating train data or while entering SR
speed/distance limits, the brake command shall be released at standstill and after driver acknowledgement..
#TEST-VAL-SUB026-4026#REF# FCT SR data Change Staff Responsible Speed / Staff Responsible Distance via DMI possible at standstill only
#TEST-VAL-SUB035-0423#REF# EET error expectation SUB035 V2.1.6 Kap. 13.1.1.2.7(train data entry/specific STM data cancelled by ETCS-Onboard)
#TEST-VAL-SUB026-5885#REF# FCT modifying/revalidating train data Train movement is detected while the driver is modifying or revalidating the Train Data

#REQ-UNISIG-SUB026-3548:01#REF# 3.14.1.7.4 #REQ-UNISIG-SUB026-010123#REF#
If the brake command was triggered due to an overpassed distance allowed for moving backwards in Post Trip mode or due to any further movement
in the direction opposite to the train orientation while the distance allowed for moving backwards in Post Trip mode is still overpassed, the
brake command shall be released at standstill and after driver acknowledgement.
UNISIG clarification:
if obu left the the mode PT, the brake is also	released
#TEST-VAL-SUB026-4779#REF# FCT basic function SB due to PT distance exceeded released at standstill and after driver ack
#TEST-VAL-SUB026-4H84#REF# EET error expectation EB triggered by overpassing reversing distance in PT revoked after mode transition

#REQ-UNISIG-SUB026-003435#REF# 3.14.1.7.5
If the brake command was triggered due to the driver not having acknowledged a text message, the brake command shall be released after the
driver has acknowledged the text message.
#TEST-VAL-SUB026-3761#REF# FCT basic function P72/76 Q_TEXTCONFIRM 3/2

#REQ-UNISIG-SUB026-0091#REF# 3.14.1.8
An indication shall be given to the driver to indicate when the brakes can be released and when an acknowledgement is requested.
#TEST-VAL-SUB026-4A37#REF# FCT basic function Supervise train movements - Reverse Movement Protection at mode FS

#REQ-UNISIG-SUB026-0092#REF# 3.14.2.2
The Roll Away Protection (RAP) shall prevent the train from moving in a direction, which conflicts with the current position of the direction
controller in the active desk.
#TEST-VAL-SUB026-4A35#REF# FCT DIRECTION_A Supervise train movements - Roll Way Protection at mode UN
#TEST-VAL-SUB026-4440#REF# FCT DIRECTION_B train data in RV

#REQ-UNISIG-SUB026-0623#REF# 3.14.2.3
If the controller is in neutral position, the RAP shall prevent forward and reverse movements of the train.
#TEST-VAL-SUB026-4A35#REF# FCT basic function Supervise train movements - Roll Way Protection at mode UN

#REQ-UNISIG-SUB026-0624#REF# 3.14.2.4
When the system recognises a movement exceeding the national value for the allowed roll away distance the brakes shall be triggered.
realised by: #REQ-UNISIG-SUB026-3749#REF#
realised by: #REQ-UNISIG-SUB026-3684:01#REF#
realised by: #REQ-UNISIG-SUB026-3685:01#REF#

#REQ-UNISIG-SUB026-3749#REF# to.3.14.2.4 #REQ-UNISIG-SUB026-0624#REF#
#ANA-UNISIG-MovementProtection-0001#REF#
The allowed roll away distance shall be supervised as safety distance.
#TEST-VAL-SUB026-4541#REF# FCT Supervision based on min/max safe RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-3684:01#REF# to.3.14.2.4 #REQ-UNISIG-SUB026-0624#REF#
It shall be configurable which brake, i.e. emergency brake (=default) or service brake is used in case of exceeding the roll away distance.
Da UNISIG keinen Bremstyp vorgibt, wird die Möglichkeit bereitgestellt, dass der Bremstyp konfigurierbar ist
#TEST-VAL-SUB026-4A35#REF# FCT EB Supervise train movements - Roll Way Protection at mode UN
#TEST-VAL-SUB026-4541#REF# FCT SB RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-3685:01#REF# to.3.14.2.4 #REQ-UNISIG-SUB026-0624#REF#
When the system recognises a movement exceeding the national value for the allowed roll away distance the configured brake shall be triggered.
#TEST-VAL-SUB026-4A35#REF# FCT EB Supervise train movements - Roll Way Protection at mode UN
#TEST-VAL-SUB026-4541#REF# FCT SB RAP, RMP and Standstill supervision with service brake
#TEST-VAL-SUB026-4F67#REF# EET error expectation Roll Away Prot. - New D_NVROLL taken into account and reference point does not change
#TEST-VAL-SUB026-8300#REF# EET error expectation Reception of P3 with D_NVROLL=0 during train movement

#REQ-UNISIG-SUB026-0625#REF# 3.14.2.6
An indication shall be given to the driver showing when the RAP is commanding the brakes.
#TEST-VAL-SUB026-4A35#REF# FCT RAP commanded EB Supervise train movements - Roll Way Protection at mode UN
#TEST-VAL-SUB026-4541#REF# FCT RAP commanded SB RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-0626#REF# 3.14.2.7
After revocation of the brake command the RAP will be re-initialised using the current position of the train as the new reference location.
#TEST-VAL-SUB026-4A35#REF# FCT basic function Supervise train movements - Roll Way Protection at mode UN

#REQ-UNISIG-SUB026-0093#REF# 3.14.3.1
The Reverse Movement Protection (RMP) shall prevent the train from moving in the opposite direction to the permitted one. The permitted movement
direction of a train shall be the one of the currently valid MA, if available on-board. See chapter 4 concerning permitted direction for special
cases.
#TEST-VAL-SUB026-4A37#REF# FCT backward movement Supervise train movements - Reverse Movement Protection at mode FS
#TEST-VAL-SUB026-5846#REF# EET error expectation Switch of direction controller and cab from A to B
#TEST-VAL-SUB026-4A40#REF# FCT forward movement Supervise train movements - Reverse Movement Protection at mode PT

#REQ-UNISIG-SUB026-0627#REF# 3.14.3.2
When a reverse movement is detected, the brake command shall be triggered after a distance specified by the national value.
realised by: #REQ-UNISIG-SUB026-3750#REF#
realised by: #REQ-UNISIG-SUB026-3686:01#REF#
realised by: #REQ-UNISIG-SUB026-3687:01#REF#

#REQ-UNISIG-SUB026-3750#REF# to.3.14.3.2 #REQ-UNISIG-SUB026-0627#REF#
#ANA-UNISIG-MovementProtection-0001#REF#
The allowed reverse movement distance shall be supervised as safety distance.
#TEST-VAL-SUB026-4F64#REF# FCT Supervision based on max safe Reverse Movement Protection in PT - Supervision based on max safe front RAW end
#TEST-VAL-SUB026-4541#REF# FCT Supervision based on min safe RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-3686:01#REF# to.3.14.3.2 #REQ-UNISIG-SUB026-0627#REF#
It shall be configurable which brake, i.e. emergency brake (=default) or service brake is used in case of exceeding the reverse movement
distance.
Da UNISIG keinen Bremstyp vorgibt, wird die Möglichkeit bereitgestellt, diesen konfigurieren zu können
#TEST-VAL-SUB026-4F64#REF# FCT EB Reverse Movement Protection in PT - Supervision based on max safe front RAW end
#TEST-VAL-SUB026-4541#REF# FCT SB RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-3687:01#REF# to.3.14.3.2 #REQ-UNISIG-SUB026-0627#REF#
When a reverse movement is detected, the configured brake command shall be triggered after a distance specified by the national value.
#TEST-VAL-SUB026-4F64#REF# FCT EB Reverse Movement Protection in PT - Supervision based on max safe front RAW end
#TEST-VAL-SUB026-4541#REF# FCT SB RAP, RMP and Standstill supervision with service brake
#TEST-VAL-SUB026-4F66#REF# EET error expectation Reverse Mov. Prot. - New D_NVROLL taken into account and reference point does not change

#REQ-UNISIG-SUB026-0628#REF# 3.14.3.4
An indication shall be given to the driver showing when the RMP is commanding the brakes.
#TEST-VAL-SUB026-4A37#REF# FCT RMP commanded EB Supervise train movements - Reverse Movement Protection at mode FS
#TEST-VAL-SUB026-4541#REF# FCT RMP commanded SB RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-0629#REF# 3.14.3.5
After revocation of the brake command the RMP will be reinitialised using the current position of the train as the new reference location.
#TEST-VAL-SUB026-4F64#REF# FCT Supervision based on max safe Reverse Movement Protection in PT - Supervision based on max safe front RAW end
#TEST-VAL-SUB026-4A37#REF# FCT Supervision based on min safe Supervise train movements - Reverse Movement Protection at mode FS

#REQ-UNISIG-SUB026-0094#REF# 3.14.3.6
Information received from balises during reverse movement shall be rejected.
#TEST-VAL-SUB026-3A98#REF# FCT basic function Information from balise rejected in reverse movement

#REQ-UNISIG-SUB026-003468#REF# to.3.14.3.6
If a balise group is read completely and the last balise of this balise group is read again in the same direction and at the same position, this
balise shall be ignored.
UNISIG clarification: a roll back situation after reading a balise group should not lead to a balise group error.
TEST APPROACH:
The scope of the requirement is to suppress a error reaction if the train rolls back into a BG (passing the last balise of the BG) and moves
later on in forward direction.
A movement into and out of a BG does not lead to a balise consistency reaction if the part of the balise is the same for both (refer System
group protocol 634, 3.16.2.1.3 a, b maximal balise distance not passed). This applies for modes where Reverse Movement Protection is inactive.
Balise passed in reverse movement are rejected it is hence not possible to read the balise in forward and backward direction if Reverse Movement
Protection is active.

The following aspects have been identified:
1) ETCS mode with active Reverse Movement Protection 
1.1) ignoring last balise only
1.2) ignoring balise at same location only
1.3) last balise not ignored if not read before
2) ETCS mode with inactive Reverse Movement Protection
2.1) partly passed BG normal operation (balise recognized in both direction)
2.2) partly passed BG exception (balise not recognized in both direction)
2.3) last BG not ignored in if passed in other direction
#TEST-VAL-SUB026-8305#REF# FCT 1.1, 1.2 Forward/backward movement leads to partly read BG, RMP active
#TEST-VAL-SUB026-8306#REF# FCT 1.3 Partly read BG after start-up
#TEST-VAL-SUB026-8304#REF# FCT 2.1, 2.3 Forward/backward movement leads to partly read BG, RMP inactive
#TEST-VAL-SUB026-8069#REF# FCT 2.2 Second read of last balise in BG
#TEST-VAL-SUB026-8070#REF# EET error expectation Second read of last balise (N_PIG=0) in BG

#REQ-UNISIG-SUB026-0095#REF# 3.14.4.1
This function shall prevent the train from moving.
#TEST-VAL-SUB026-3168#REF# FCT basic function Standstill supervision

#REQ-UNISIG-SUB026-0630#REF# 3.14.4.2
When a movement is detected, the brake command shall be triggered after a distance specified by the national value.
realised by: #REQ-UNISIG-SUB026-3751#REF#
realised by: #REQ-UNISIG-SUB026-3688:01#REF#
realised by: #REQ-UNISIG-SUB026-3689:01#REF#

#REQ-UNISIG-SUB026-3751#REF# to.3.14.4.2 #REQ-UNISIG-SUB026-0630#REF#
#ANA-UNISIG-MovementProtection-0001#REF#
The allowed standstill supervision distance shall be supervised as safety distance.
#TEST-VAL-SUB026-5624#REF# EET CFX00077486 Standstill supervision in combination with cab change
#TEST-VAL-SUB026-4541#REF# FCT Supervision based on min/max safe RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-3688:01#REF# to.3.14.4.2 #REQ-UNISIG-SUB026-0630#REF#
It shall be configurable which brake, i.e. emergency brake (=default) or service brake is used in case of exceeding the standstill moving
distance.
Da UNISIG keinen Bremstyp vorgibt, wird die Möglichkeit bereitgestellt, dass der Bremstyp konfigurierbar ist
#TEST-VAL-SUB026-3168#REF# FCT EB Standstill supervision
#TEST-VAL-SUB026-4541#REF# FCT SB RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-3689:01#REF# to.3.14.4.2 #REQ-UNISIG-SUB026-0630#REF#
When a movement in Stand By is detected, the configured brake command shall be triggered after a distance specified by the national value.
#TEST-VAL-SUB026-3168#REF# FCT EB Standstill supervision
#TEST-VAL-SUB026-4541#REF# FCT SB RAP, RMP and Standstill supervision with service brake
#TEST-VAL-SUB026-5624#REF# EET error expectation Standstill supervision in combination with cab change

#REQ-UNISIG-SUB026-0631#REF# 3.14.4.4
After revocation of the brake command the standstill supervision will be re-initialised.
#TEST-VAL-SUB026-3168#REF# FCT basic function Standstill supervision
#TEST-VAL-SUB026-5624#REF# EET error expectation Standstill supervision in combination with cab change

#REQ-DESIGN-CR-0045#REF# 3.14.4.5
If a cab is active, an indication shall be given to the driver showing when the Standstill Supervision is commanding the brakes.
TEST APPROACH:
The following aspects have been identified:
Standstill supervision with
1) service brake
2) emergency brake (default)
#TEST-VAL-SUB026-4541#REF# FCT 1 RAP, RMP and Standstill supervision with service brake
#TEST-VAL-SUB026-3168#REF# FCT 2 Standstill supervision

Chapter 3.15

#REQ-UNISIG-SUB026-3348#REF# 3.15.1.3.1
When receiving an order to switch to another RBC at a given location, the on-board equipment shall:
a)	Establish the communication session with the Accepting RBC;
b)	Send a position report to the Handing Over RBC when the maximum safe front end of the train passes the given location;
c)	Send a position report to the Handing Over RBC when the minimum safe rear end of the train passes the given location;
the handover procedure with one and two mobiles is described in chapter 5.15
realised by: #REQ-UNISIG-SUB026-0886#REF#
realised by: #REQ-UNISIG-SUB026-0887#REF#
realised by: #REQ-UNISIG-SUB026-0889#REF#
realised by: #REQ-UNISIG-SUB026-0891#REF#
realised by: #REQ-UNISIG-SUB026-0892#REF#
realised by: #REQ-UNISIG-SUB026-0894#REF#

#REQ-DESIGN-CR-0751#REF# to.3.15.1.3.1
If a Handover to the handing over RBC is received, this handover shall be ignored.
Exception: If this handover is received during another handover, see the requirements for 5.15.1.5.
UNISIG clarification:
a HO to the same RBC makes no sence.
#TEST-VAL-SUB026-5534#REF# FCT basic function RBC transition order - handing over RBC same as accepting RBC

#REQ-UNISIG-SUB026-003555#REF# 3.15.1.3.2
It is up to the on-board equipment to manage the establishment of one communication session and the release of the other one:
a)	If it is able to handle two communication sessions at the same time, the radio session with the Accepting RBC shall be established as
soon as it receives the RBC transition order .
b)	If it is able to handle one communication session only at a given time, it shall wait until the session with the Handing over RBC is
terminated due to crossing the border (refer to 3.5.5.1e and 3.15.1.2.7) and then establish the session with the Accepting RBC.
the handover procedure with one and two mobiles is described in chapter 5.15

a) realize through 5.15.2.2.1
b) realize through 5.15.3.2.5.1
realised by: #REQ-UNISIG-SUB026-0886#REF#
realised by: #REQ-UNISIG-SUB026-0894#REF#

#REQ-UNISIG-SUB026-0635:01#REF# 3.15.1.3.3
As soon as the on-board equipment has established the session with the Accepting RBC, it shall send its Train Data unless it is in sleeping or
non leading mode.
realised by: #REQ-DESIGN-CR-0748:02#REF#

#REQ-UNISIG-SUB026-3580#REF# 3.15.1.3.4
When the on-board equipment is connected to both RBCs, it shall send its position reports to both of them with the use of the position report
parameters valid for the Handing Over RBC.
realised by: #REQ-UNISIG-SUB026-0636:02#REF#

#REQ-DESIGN-CR-0046#REF# 3.15.1.3.4.1
If the on-board equipment is connected to both RBCs, and it executes an End of Mission, it shall execute the End of Mission procedure with both
RBCs
#TEST-VAL-SUB026-5124#REF# FCT OBU supervised by accepting RBC , CFX00035202 End of Mission zu beiden RBCs bei RBC/RBC Handover
#TEST-VAL-SUB026-3971#REF# FCT OBU supervised by handing over RBC EoM execution during RBC handover

#REQ-UNISIG-SUB026-0636:02#REF# to.3.15.1.3.4 #REQ-UNISIG-SUB026-3580#REF#
#ANA-UNISIG-RBCHandover-0007:01#REF#
If the on-board equipment is connected to both RBCs, every position report message to the supervising RBC shall be sent also to the not
supervising RBC.

Exception: The position report to the Handing Over RBC for termination the session to Handing Over RBC, if the border is passed with min safe
rear end, shall not be send to the Accepting RBC.
UNISIG clarification:
PRs to the supervising RBC shall be sent also to the not supervising RBC independentfrom an ongoing handover.
TEST APPROACH:
The following aspects have been identified:
1) OBU supervised by handing over RBC
1.1) PR due to P58
1.2) PR due to mode change
1.3) PR due to standstill 
2) OBU supervised by accepting RBC
2.1) PR due to P58
2.2) PR due to mode change
2.3) PR due to standstill 
3) Exception
#TEST-VAL-SUB026-4839#REF# FCT 1.1, 2.1 RBC transition PR according to P58 from supervising RBC send to both RBCs
#TEST-VAL-SUB026-3817#REF# ECT 1.2, 1.3 Position reports after aborted RBC handover
#TEST-VAL-SUB026-3819#REF# FCT 2.2, 2.3, 3 Cancellation of RBC transition order due to mode change not taken into account after max safe front end passed the border

#REQ-UNISIG-SUB026-3250#REF# 3.15.1.3.5
When the on-board sends a position report directly to the Accepting RBC with its maximum safe front end having passed the border, it shall use
information received from the Accepting RBC and only a disconnection order shall be accepted from the Handing Over RBC.
realised by: #REQ-UNISIG-SUB026-3575:01#REF#

#REQ-UNISIG-SUB026-3355#REF# 3.15.1.3.6
In case two communication sessions are opened, if information is received from the Accepting RBC before a position report is sent to the
Accepting RBC with the maximum safe front end having passed the border, this information shall be stored on-board.
Exception: The acknowledgement of Train Data shall be immediately accepted by the on-board equipment.
is realized through 4.8.2.1 c
realised by: #REQ-UNISIG-SUB026-3121#REF#

#REQ-UNISIG-SUB026-3113#REF# 3.15.4.1.1 #REQ-UNISIG-SUB026-010263#REF#
#REQ-UNISIG-SUB040-3037#REF#
A new reversing area given from the trackside shall replace the one already available on-board.
#TEST-VAL-SUB026-3598#REF# FCT BG New RV information replace the one already available on-board
#TEST-VAL-SUB026-5243#REF# EET CFX00041576 New RV information replace the one already available on-board (new area starts within old area)
#TEST-VAL-SUB026-5297#REF# EET CFX00041576 New RV information replace the one already available on-board (new area same as old area, new information received after entering RV area)
#TEST-VAL-SUB026-5298#REF# EET CFX00041576 New RV information replace the one already available on-board (new area same as old area)
#TEST-VAL-SUB026-5299#REF# EET CFX00041576 New RV information replace the one already available on-board (new area attached to old area)
#TEST-VAL-SUB026-3597#REF# FCT RBC , CFX00039857 New RV information replace the one already available on-board
#TEST-VAL-SUB026-5219#REF# EET error expectation Reception of new RV area (P138/P139) while RV acknowledgment request active

#REQ-DESIGN-CR-0321:01#REF# 3.15.4.2
Together with start and end of reversing area, the following supervision information shall be sent:
a)	Maximum distance to run in the direction opposite to the orientation of the reversing area, the fixed reference location being the end
location of the area where reversing of movement is permitted at the time of reception of this reversing area information.
b)	Reversing mode speed limit allowed during reverse movement.
Festlegung, dass Paket 138 zusammen mit Paket 139 gesendet werden muss.

a) und b) definieren die Verwendung der Informationen des Paketes 139

see figure 57 also
#DSC-UNISIG-SUB026-003625#REF#

Figure 57: Reversing area and maximum distance to run
realised by: #REQ-UNISIG-SUB026-3108#REF#
realised by: #REQ-UNISIG-SUB026-3107#REF#
realised by: #REQ-UNISIG-SUB026-3663#REF#

#REQ-UNISIG-SUB026-3108#REF# 3.15.4.2.a #REQ-DESIGN-CR-0321:01#REF#
The reversing supervision information "maximum distance to run in RV mode" in the direction opposite to the orientation of the
reversing area shall be started at the fixed reference location being the end location of the area where reversing of movement is permitted at
the time of reception of this reversing area information.
realizes 3.15.4.2 a)
#TEST-VAL-SyAnfSpezCR-0058#REF# FCT D_REVERSE < L_REVERSEAREA Reversing Distance Management, D_REVERSE smaller than L_REVERSEAREA
#TEST-VAL-SyAnfSpezCR-0056#REF# FCT D_REVERSE > L_REVERSEAREA Reversing Distance Management, D_REVERSE greater than L_REVERSEAREA

#REQ-UNISIG-SUB026-3107#REF# 3.15.4.2.b #REQ-DESIGN-CR-0321:01#REF#
The reversing supervision information "Reversing mode speed limit" defines the allowed speed limit during reverse movement in mode RV
(see 3.11.7.1.2).
realizes 3.15.4.2 b)

realizes through 4.4.18.1.3 a and definition of P139
realised by: #REQ-UNISIG-SUB026-3095#REF#
realised by: #REQ-UNISIG-SUB026-0358#REF#

#REQ-UNISIG-SUB026-3663#REF# to.3.15.4.2 #REQ-DESIGN-CR-0321:01#REF#
If received the Reversing Area information not together with Reversing Supervision information, the Reversing Area information shall be ignored.
In this case a basic diagnostic event shall be created.
definition, when P138 is received alone
#TEST-VAL-SUB026-3762#REF# FCT basic function Reversing Area information not received together with Reversing Supervision information

#REQ-UNISIG-SUB026-0645#REF# 3.15.4.3
New distance to run and Reversing mode speed limit given from the trackside shall replace the one already available on-board.
#TEST-VAL-SUB026-3599#REF# FCT basic function New Reversing supervision information replace the one already available on-board
#TEST-VAL-SUB026-3601#REF# EET error expectation New RV distance to run and maximum speed information replace the one already available on-board (RV/L2 overspeed)
#TEST-VAL-SUB026-3602#REF# EET error expectation New shorter RV distance to run replace the one already available on-board (RV/L2)

#REQ-DESIGN-CR-0322#REF# 3.15.4.3.1
In case of update of distance to run in reverse movement, the fixed reference location for reversing distance shall remain unchanged.
see figure 59 also
#DSC-UNISIG-SUB026-003637#REF#

Figure 59: New maximum distance to run
#TEST-VAL-SUB026-5742#REF# FCT basic function Reception of new Reversing Supervision Information in RV
#TEST-VAL-SyAnfSpezCR-0057#REF# EET error expectation Reception of new P139, new D_REVERSE already passed

#REQ-DESIGN-CR-0323#REF# 3.15.4.4
While at standstill with the front end of the train inside the indicated area, it shall be possible for the driver to reverse the direction of
movement.
#TEST-VAL-SUB026-5743#REF# FCT basic function Possibility to switch to RV in side RV area

#REQ-DESIGN-CR-0324#REF# 3.15.4.5
The on-board equipment shall allow movement in the direction opposite to the train orientation, supervising it according to distance and speed
received.
Rel. 8.0:
the part ", without the need of a confirmation from the RBC" of laste sentence is deleted now.

is realized now with 4.4.18.1.3
realised by: #REQ-UNISIG-SUB026-3095#REF#
realised by: #REQ-UNISIG-SUB026-3096:02#REF#

#REQ-DESIGN-CR-0325#REF# 3.15.4.7 #REQ-UNISIG-SUB026-006459#REF#
When at standstill the on-board equipment shall inform the driver if the reversing of movement is permitted.
#TEST-VAL-SUB026-5743#REF# FCT basic function Possibility to switch to RV in side RV area

#REQ-DESIGN-CR-0326:01#REF# 3.15.4.8
If the end location of the maximum distance to run in the opposite direction is passed by the train front end, the emergency brake command shall
be triggered.
realizes through 4.18.1.3 b
realised by: #REQ-UNISIG-SUB026-3096:02#REF#

#REQ-UNISIG-SUB026-003651#REF# 3.15.5.1
In a level 2/3 area, the ERTMS/ETCS on-board equipment shall be able to handle a track ahead free request given by the RBC.
correspond with 4.8.3
realised by: #REQ-UNISIG-SUB026-010033#REF#

#REQ-UNISIG-SUB026-0647#REF# 3.15.5.2
The track ahead free request from the RBC shall indicate to the on-board
a)	at which location the ERTMS/ETCS on-board equipment shall begin to display the request to the driver.
b)	at which location the ERTMS/ETCS on-board equipment shall stop to display the request to the driver (in case the driver did not
acknowledge).
#TEST-VAL-SUB026-5845#REF# FCT basic function START/STOP TAF request

#REQ-UNISIG-SUB026-0648#REF# 3.15.5.3
The driver shall have the possibility to acknowledge the track ahead free request (meaning the driver confirms that the track between the head
of the train and the next signal or board marking signal position is free).
#TEST-VAL-SUB026-5845#REF# FCT basic function START/STOP TAF request

#REQ-UNISIG-SUB026-0649#REF# 3.15.5.4
When the driver acknowledges, the ERTMS/ETCS on-board equipment shall stop displaying the request, and shall inform the RBC that the track ahead
is free.
#TEST-VAL-SUB026-5845#REF# FCT basic function START/STOP TAF request

#REQ-UNISIG-SUB026-003663#REF# 3.15.5.6
A new track ahead free request shall replace the one previously received and stored.
#TEST-VAL-SUB026-5844#REF# FCT basic function New TAF request replaces previously received and stored TAF request

#REQ-UNISIG-SUB026-003677#REF# 3.15.6.5
Amongst the data to be used by applications outside ERTMS/ETCS that can be transmitted by trackside over the ERTMS/ETCS transmission channels,
it shall be possible to send from balises or RBC data to be forwarded to a National System.

#REQ-DESIGN-CR-0506#REF# 3.15.7.2 #REQ-DESIGN-CR-0507#REF#
#ANA-UNISIG-BMM-0001#REF#
In Levels 0/NTC, the alarms which may be triggered by metal masses shall be ignored for a defined distance (see A.3.1). If the alarm persists
for a longer distance the ERTMS/ETCS on-board equipment shall trigger a safety reaction.
different handling between ELBE5A and ELBE5K is necessary (see analysis)
TEST APPROACH:
The following aspects have been identified:
1) handling with ELBE5A
1.1) L0
1.2) NTC
2) handling with ELBE5K
2.1) L0
2.2) NTC
2.3) continuous supervision with ELBE5K
#ANALYSE-VALUNISIG-0047#REF# FCT The ESBO solution for ELBE5A ensures a continuous supervision of the alarm state.
#TEST-VAL-SUB026-3975#REF# FCT 1.1 Fixed distance of metal immunity in L0
#TEST-VAL-SUB026-7765#REF# FCT 1.2 Fixed distance of metal immunity in level NTC
#TEST-VAL-SUB026-8139#REF# FCT 2.1 Fixed distance of metal immunity in level 0 (handling with ELBE5K)
#TEST-VAL-SUB026-8138#REF# FCT 2.2 Fixed distance of metal immunity in level NTC (handling with ELBE5K)
#TEST-VAL-SUB026-8144#REF# FCT 2.3 BMM alarm handling with ELBE5K - continuous supervision

#REQ-UNISIG-SUB026-003693#REF# 3.15.8.1
After being switched off (i.e. once in No Power mode), the ERTMS/ETCS on-board equipment shall be capable, if fitted with, to detect and record
whether the engine has been moved or not, during a period of at least 72 hours.

#REQ-UNISIG-SUB026-003695#REF# 3.15.8.2
When powered on again, the ERTMS/ETCS on-board equipment shall use, if available, the memorised information about cold movement in order to
update the status of information stored by on-board equipment (see chapter 4 section 4.11 for details).
is realized with 4.11
realised by: #REQ-UNISIG-SUB026-005544#REF#

#REQ-UNISIG-SUB026-003705#REF# 3.15.9.2
During a start of mission, the driver shall have the opportunity to set a new VBC, or to remove an existing one.
The Enabling of the Set/Remove VBC on DMI is defined in ERA SRS DMI

#REQ-UNISIG-SUB026-003707#REF# 3.15.9.3
As long as a VBC is stored on-board:
a)	The ERTMS/ETCS on-board equipment shall ignore any balise telegram that includes a VBC marker and a country/region identity that both
match the VBC identity.
b)	No reaction shall be applied if errors in the reading of the rest of such balise telegram occur.
VBC function is not realized
TEST APPROACH:
The following aspects have been identified:
1) VBC marker and country/region identity match the stored VBC
1.1) rest of the information is valid
1.2) data inconsistency
2) VBC marker and country/region identity do not match the stored VBC
2.1) mismatch because of the VBC marker
2.2) mismatch because of the country/region identity
2.3) error free BG
2.4) BG with data inconsistency

#REQ-UNISIG-SUB026-003709#REF# 3.15.9.4
If the ERTMS/ETCS on-board equipment receives from balise or from driver a new VBC with the same VBC identity as an already stored VBC, the new
VBC shall replace the previous one, including its validity period.
VBC function is not realized

#REQ-UNISIG-SUB026-003711#REF# 3.15.9.5
A VBC shall be retained on-board when the on-board equipment is switched off (i.e. enters No Power mode) and shall remain applicable when
powered on again. It shall be deleted when:
a)	it is ordered by trackside, or
b)	its validity period has elapsed, or
c)	it is removed by the driver (during Start of Mission), or
d)	a mismatch is detected between the country/region identity read from a balise group and the country/region identity of the VBC. Note:
this means that the reception of a consistent balise group message is a necessary condition for deleting a VBC due to mismatching country/region
identities.
VBC function is not realized

#REQ-UNISIG-SUB026-007778:01#REF# 3.15.10.1 #REQ-UNISIG-SUB026-010427#REF#
#REQ-UNISIG-SUB026-010428#REF#
#REQ-UNISIG-SUB026-010429#REF#
#REQ-UNISIG-SUB026-010430#REF#
The ERTMS/ETCS on-board equipment shall offer the possibility to display, only on driver request, an overview of the gradient profile (as
received from trackside), of the MRSP, of the track conditions (except the tunnel stopping areas), of the indication location at MRSP speed (see
3.13.10.4.11) and of the first target at zero speed, if any (e.g. the EOA or the start location of a mode profile), with the remaining distances
referred to the train front end position.
TEST APPROACH:
The following aspects have been identified:
1) MRSP/GP
2) indication location
3) track conditions 
4) dependency on driver request
Aspect 4 is covered by #REQ-SAS_DMI-003363#REF#, #REQ-SRS_DMI-001646#REF#, #REQ-SAS_DMI-003408#REF#
#TEST-VAL-SUB026-7624#REF# FCT 1 Planning area within the MA and up to the first target at zero speed
#TEST-VAL-SUB026-7667#REF# FCT 2 Planning area within the MA and up to the first target at zero speed
#TEST-VAL-SUB026-7779#REF# FCT 3 Display orders and announcements of TCs in Planning Area within MA and up to the first target at zero speed

#REQ-UNISIG-SUB026-007779:01#REF# 3.15.10.2 #REQ-DESIGN-CR-0124#REF#
#REQ-UNISIG-SUB026-002106#REF#
#REQ-UNISIG-SUB026-002108#REF#
With regards to the MRSP, the track conditions, the indication location at MRSP speed and the first target at zero speed, the remaining
distances shall be computed taking into account the min safe, the estimated or the max safe train front end position depending on their
respective supervision.
TEST APPROACH:
The following aspects have been identified:
1) MRSP/GP
2) indication location
3) track conditions 
#TEST-VAL-SUB026-7624#REF# FCT 1 Planning area within the MA and up to the first target at zero speed
#TEST-VAL-SUB026-7667#REF# FCT 2 Planning area within the MA and up to the first target at zero speed
#TEST-VAL-SUB026-7779#REF# FCT 3 Display orders and announcements of TCs in Planning Area within MA and up to the first target at zero speed

#REQ-UNISIG-SUB026-007780#REF# 3.15.10.3
With regards to the gradient profile, the remaining distances shall be computed taking into account the estimated train front end position.
#TEST-VAL-SUB026-7624#REF# FCT basic function Planning area within the MA and up to the first target at zero speed

#REQ-UNISIG-SUB026-007781:02#REF# 3.15.10.4
The overview of route related information shall be restricted to the elements contained within the movement authority and up to the first target
at zero speed, if any.
#TEST-VAL-SUB026-7668#REF# FCT basic function Planning area indicated up to the first target at zero speed

Chapter 3.16

#REQ-UNISIG-SUB026-0106#REF# 3.16.1.1 #REQ-UNISIG-SUB026-3119#REF#
The on-board shall not consider a message transmitted from the trackside if any of the following criteria is not fulfilled.
a)	Correctness of the received message: the whole message shall be complete and respect the ETCS language; variables shall not have invalid
values
b)	The message shall be received in due time.
c)	The message shall be received at the right expected location.
as stated below.
realised by: #REQ-UNISIG-SUB026-0411#REF#
realised by: #REQ-DESIGN-CR-0365#REF#
realised by: #REQ-DESIGN-CR-0366#REF#
realised by: #REQ-DESIGN-CR-0330#REF#
realised by: #REQ-UNISIG-SUB026-3016#REF#
realised by: #REQ-UNISIG-SUB026-0672#REF#

#REQ-UNISIG-SUB026-0107#REF# 3.16.2.1.3
A balise within a balise group shall be regarded as missed if
a)	No balise is found within the maximum distance between balises from the previous balise in the group.
or
b)	A following balise within the group has been passed.
#TEST-VAL-SUB026-3173#REF# FCT basic function Balise missing within a balise group

#REQ-UNISIG-SUB026-0108#REF# 3.16.2.2.1
If the on-board is not able to recognise whether a balise group is linked or unlinked (if none of the balises in the balise group can be read
correctly), it shall consider it as unlinked.
#TEST-VAL-SUB026-3174#REF# FCT basic function Gelinkt/ungelinkt kann nicht bestimmt werden

#REQ-UNISIG-SUB026-0109#REF# 3.16.2.3.1
If linking information is used the on-board shall react according to the linking reaction information in the following cases:
a)	If the location reference of the expected balise group is found in rear of the expectation window
b)	If the location reference of the expected balise group is not found inside the expectation window (i.e. the end of the expectation
window has been reached without having found the expected balise group)
c)	If inside the expectation window of the expected balise group another announced balise group, expected later, is found.
#TEST-VAL-SUB026-3360#REF# EET CFX00034396 Erneutes Senden der Linkinginformationen nach einer Linking-Reaction
#TEST-VAL-SUB026-3361#REF# EET CFX00034396 Erneutes Senden der Linkinginformationen nach einer Linking-Reaction
#TEST-VAL-SUB026-3589#REF# EET CFX00034396 Linking Consistency - BG not found inside expectation window - ref. BG passed with different train orientation
#TEST-VAL-SUB026-3590#REF# EET CFX00034396 Linking Consistency - BG not found inside expectation window - ref. BG passed with different train orientation (with antenna switch)
#TEST-VAL-SUB026-3591#REF# EET CFX00034396 Linking Consistency - BG not found inside expectation window - ref. BG passed with different train orientation (with antenna and q_dlrbg switch)
#TEST-VAL-SUB026-3594#REF# EET CFX00034396 Linking Consistency - linking information received while estimated front end cab A nominal antenna A reverse of BG
#TEST-VAL-SUB026-3592#REF# EET CFX00037498 Linking in MA with Shifted Location Reference - ref. BG passed with different train orientation
#TEST-VAL-SUB026-3593#REF# EET CFX00037498 Linking Consistency - BG not found inside expectation window - ref. BG passed with different train orientation (cab reverse antenna nominal of ref. BG)
#TEST-VAL-SUB026-3595#REF# EET CFX00037498 Linking in MA with Shifted Location Reference - ref. BG passed with different train orientation (with antenna switch)
#TEST-VAL-SUB026-3012#REF# FCT a) Acceptance of announced linked BGs according to the expectation window
#TEST-VAL-SUB026-3932#REF# FCT b) Replacement of linking information
#TEST-VAL-SUB026-3311#REF# FCT c) BG not found in announced order
#TEST-VAL-SUB026-7002#REF# EET error expectation BG mehrfach im Linking

#REQ-DESIGN-CR-0586#REF# 3.16.2.3.1.1
The ERTMS/ETCS on-board equipment shall ignore (i.e. it will not consider as LRBG) a balise group found with its location reference outside its
expectation window.
realised by: #REQ-UNISIG-SUB026-0411#REF#

#REQ-UNISIG-SUB026-3246#REF# to.3.16.2.3.1.1 #ANA-UNISIG-LinkReaction-0001#REF#
Die Anwendersoftware muss sicherstellen, dass eine Verzögerung der Verarbeitung einer gelesenen Balise innerhalb der vorgegebenen
Performance-Anforderungen nicht zum Ausführen der Link Reaktion wegen Nichtlesens innerhalb des Erwartungsfensters führt.
Die Performance-Anforderung von maximal 1 Sekunde aus /UNISIG SUBSET 041/, Kap. 5.2.1.1 für das Verarbeiten einer Balisenmessage bis zum
Auslösen der Emergency Brake ist als Grundlage für die Ermittlung der maximalen Verzögerung des Auslösens der Link Reaktion zu verwenden.
Rel. 6.4: 
Die konkrete maximale Verzögerung kann erst im Rahmen der SW-Architektur aus der Zykluszeit, der watchtime sowie der Festlegung der
Verarbeitungsreihenfolge der einzelnen Ereignisse erfolgen.
TEST APPROACH:
The following aspects have been identified:
1) OBU ensures the performance requirement for evaluating balise messages - verified by SWHWINT test
2) OBU delay of linking reaction for end of the expectation window passed
#TEST-VAL-SUB026-7178#REF# FCT 2 Delayed evaluation of end of linking expectation window
#TEST-SWHWINT-PERFORMANCE-0001#REF# PER 1 Empfang einer Balisenmessage -> Auslösen der Zwangsbremse

#REQ-UNISIG-SUB026-0654#REF# 3.16.2.3.2
The on-board shall reject the message from the expected group and trip the train if the balise group is passed in the unexpected direction.
#TEST-VAL-SUB026-3175#REF# FCT basic function passage of announced BG in wrong direction

#REQ-DESIGN-CR-0191#REF# 3.16.2.3.3
If the location reference balise of the group is duplicated and the on-board is only able to correctly evaluate the duplicating one, the
duplicating one shall be used as location reference instead.
TEST APPROACH:
The following aspects have been identified:
1) BG passed in nominal direction
2) BG passed in reverse direction
#TEST-VAL-SUB026-5747#REF# FCT 1 Location reference balise of the group is missing but duplicated, duplicated earlier than expected
#TEST-VAL-SUB026-5749#REF# FCT 2 Location reference balise of the group is missing but duplicated, reverse movement

#REQ-DESIGN-CR-0192#REF# 3.16.2.3.4
If the balise duplicating the location reference balise is used as location reference for the group, and is found within the expectation window,
no linking reaction shall be applied.
TEST APPROACH:
The following aspects have been identified:
1) Duplicated balise found earlier than expected
2) Duplicated balise found later than expected
#TEST-VAL-SUB026-5747#REF# FCT 1 Location reference balise of the group is missing but duplicated, duplicated earlier than expected
#TEST-VAL-SUB026-5748#REF# FCT 2 Location reference balise of the group is missing but duplicated, duplicated later than expected

#REQ-DESIGN-CR-0365#REF# 3.16.2.4.1 #REQ-UNISIG-SUB026-0106#REF#
#REQ-UNISIG-SUB026-1011:01#REF#
If linking information is used, the on-board shall reject the message from a linked balise group found in the expected location and react
according to the linking reaction in the following cases:
a)	A balise is missed inside the group.
b)	A balise is detected but no telegram is decoded (e.g. wrong CRC,...).
c)	Variables in the balise group message have invalid values.
d)	Message counters do not match (see 3.16.2.4.7)
#TEST-VAL-SUB026-3343#REF# EET CFX00034440 Fahrzeugreaktion auf identische Baliseninhalte (keine Linking Information vorhanden)
#TEST-VAL-SUB026-3344#REF# EET CFX00034440 Fahrzeugreaktion auf identische Baliseninhalte, Linking available (Q_LOCACC=2, angekündigte BG)
#TEST-VAL-SUB026-3894#REF# EET CFX00034440 Reaktion on reading First balise of BG multiple times (other balises in BG not read)
#TEST-VAL-SUB026-3177#REF# FCT a) A balise is missed inside the group
#TEST-VAL-SUB026-3178#REF# FCT b) A balise is detected but no telegram is decoded
#TEST-VAL-SUB026-3179#REF# FCT c) , CFX00037276 Variables in the balise group message have invalid values
#TEST-VAL-SUB026-5289#REF# FCT d) Linking information stored on-board, message counter do not match
#TEST-VAL-SUB026-5616#REF# EET error expectation Linking consistency revers announced BG found but incomplete

#REQ-DESIGN-CR-0193:01#REF# 3.16.2.4.2
Exception: Concerning a) and b) above, the ERTMS/ETCS on-board equipment shall not reject the message and shall not apply the linking reaction
if the balise not found, or not decoded, is duplicated within the balise group and the duplicating one is correctly read.
#TEST-VAL-SUB026-3177#REF# FCT 3.16.2.4.1 a) A balise is missed inside the group
#TEST-VAL-SUB026-3178#REF# FCT 3.16.2.4.1 b) A balise is detected but no telegram is decoded
#TEST-VAL-SUB026-3179#REF# FCT 3.16.2.4.1 c) Variables in the balise group message have invalid values
#TEST-VAL-SUB026-5289#REF# FCT 3.16.2.4.1 d) Linking information stored on-board, message counter do not match
#TEST-VAL-SUB026-3448#REF# EET error expectation missing balise and balise with crc error inside linked BG - balise duplicated

#REQ-UNISIG-SUB026-0658#REF# 3.16.2.4.3 #REQ-UNISIG-SUB026-003956#REF#
#REQ-UNISIG-SUB026-1011:01#REF#
If linking information is used, the on-board shall reject the message from a balise group marked as linked but not included in the linking
information. No reaction shall be applied, even if errors in the reading of the balise group occur.
#TEST-VAL-SUB026-3345#REF# EET CFX00034440 Unannounced and incomplete BG read twice
#TEST-VAL-SUB026-3180#REF# FCT basic function , CFX00031295 Processing of announced BGs
#TEST-VAL-SUB026-3888#REF# EET error expectation Validity of un-announced BG starts after reading of last expected BG of pkt5
#TEST-VAL-SUB026-5859#REF# EET error expectation Inhibition of balise group message consistency reaction in FS

#REQ-DESIGN-CR-0366#REF# 3.16.2.4.4 #REQ-UNISIG-SUB026-0106#REF#
#REQ-UNISIG-SUB026-1012:02#REF#
If no linking information is used, the on-board shall reject the message from a balise group marked as linked and command application of the
service brake in the following cases:
a)	A balise is missed inside the group.
b)	A balise is detected, but no telegram is decoded (e.g. wrong CRC).
c)	Variables in the balise group message have invalid values.
d)	Message counters do not match (see 3.16.2.4.7)
TEST APPROACH:
In addition to the straight-forward aspects a, b, c and d, the balise group message consistency is also tested for each mode. 
However, mode NP is not realised by the ASW (see #REQ-UNISIG-SUB026-004698#REF#). Mode IS is realized by hardware and the EVC In is powered off
in isolation (see #REQ-UNISIG-SUB026-004676#REF#). OBU does permanently command the Emergency Brakes in the ETCS mode SF. Balise as well as RBC
messages are ignored in IS and SF (see #REQ-UNISIG-SUB026-3008#REF# and #REQ-UNISIG-SUB026-3009#REF#). Hence, the modes NP, IS and SF will be
omitted.
#TEST-VAL-SUB026-4705#REF# FCT FS, UN, SR, SN Table 4.5.2 --> Balise Group Message Consistency if no linking consistency is checked (FS,UN,SR,SN)
#TEST-VAL-SUB026-4F11#REF# FCT LS Table 4.5.2 --> Balise Group Message Consistency if no linking consistency is checked(LS)
#TEST-VAL-SUB026-4706#REF# FCT OS, SL, SH, SB Table 4.5.2 --> Balise Group Message Consistency if no linking consistency is checked (OS,SB,SL,SH)
#TEST-VAL-SUB026-4708#REF# FCT TR, PT, RV, NL Table 4.5.2 --> Balise Group Message Consistency if no linking consistency is checked (TR,PT,RV,NL)
#TEST-VAL-SUB026-3181#REF# FCT a) Missing Balise in BG (Q_LINK=1, no linking on-board)
#TEST-VAL-SUB026-3183#REF# FCT b) Balise mit Fehler (keine Telegramm-Dekodierung, kein Linking, gelinkte BG)
#TEST-VAL-SUB026-3185#REF# FCT c) Fehlerhafte Variablenwerte in Balisentelegramm (gelinkt), kein Linking onboard
#TEST-VAL-SUB026-5286#REF# FCT d) No linking information is used, message counter do not match

#REQ-UNISIG-SUB026-003793#REF# 3.16.2.4.4.1
Exceptions: Concerning a) and b) of clause 3.16.2.4.4, the ERTMS/ETCS on-board equipment:
a)	shall not reject the message and shall not command application of the service brake if the balise not found, or not decoded, is
duplicated within the balise group, the duplicating one is correctly read and contains:
∙	directional information while the orientation of the balise group can still be evaluated, or
∙	only information valid for both directions, or
∙	neither directional information nor information valid for both directions, or
∙	only data to be used by applications outside ERTMS/ETCS, or
∙	only data to be used by applications outside ERTMS/ETCS together with other information valid for both directions.
b)	shall not command application of the service brake if the telegram correctly read from another balise of the group contains the
information “Inhibition of balise group message consistency reaction”.
realised by: #REQ-DESIGN-CR-0194:01#REF#
realised by: #REQ-UNISIG-SUB026-010127#REF#

#REQ-DESIGN-CR-0194:01#REF# 3.16.2.4.4.1.a #REQ-UNISIG-SUB026-003793#REF#
Exceptions: Concerning a) and b) of clause 3.16.2.4.4, the ERTMS/ETCS on-board equipment shall not reject the message and shall not command
application of the service brake if the balise not found, or not decoded, is duplicated within the balise group, the duplicating one is
correctly read and contains:
∙	directional information while the orientation of the balise group can still be evaluated, or
∙	only information valid for both directions, or
∙	neither directional information nor information valid for both directions, or
∙	only data to be used by applications outside ERTMS/ETCS, or
∙	only data to be used by applications outside ERTMS/ETCS together with other information valid for both directions.
TEST APPROACH:
The aspect a) and b) of clause 3.16.2.4.4 have the sub aspects. 
1) directional information while the orientation of the balise group can still be evaluated, or
2) only information valid for both directions, or
3) neither directional information nor information valid for both directions, or
4) only data to be used by applications outside ERTMS/ETCS, or
5) only data to be used by applications outside ERTMS/ETCS together with other information valid for both directions.
Note: The forwarding of P44 information without orientation is limited to P44 with NID_XUSER = 102 (refer #REQ-UNISIG-SUB026-001148#REF#). This
function is not part of R8 (refer #REQ-SWAnf-009262#REF#) the check of the acceptance of P44 is hence omitted.

The outlined test aspects indicate aspect and sub aspect separated by a dash.
#TEST-VAL-SUB026-3181#REF# FCT a-1 Missing Balise in BG (Q_LINK=1, no linking on-board)
#TEST-VAL-SUB026-5745#REF# FCT a-2, b-2 A group of two balises duplicating each other treated as a single BG in case where only one balise is correctly read
#TEST-VAL-SUB026-5746#REF# FCT a-3, b-3 Two balise group duplicating each other no information included, one balise missing
#TEST-VAL-SUB026-4H85#REF# FCT a-4, b-4 Linked BG with duplicated balises and error - data used outside ERTM/ETCS
#TEST-VAL-SUB026-4H86#REF# FCT a-5, b-5 Linked BG with duplicated balises and error - data used outside ERTM/ETCS and info for both directions
#TEST-VAL-SUB026-3183#REF# FCT b-1 Balise mit Fehler (keine Telegramm-Dekodierung, kein Linking, gelinkte BG)
#TEST-VAL-SUB026-3267#REF# EET error expectation Balise not found duplicated, the duplicating balise is correctly read
#TEST-VAL-SUB026-7709#REF# EET error expectation Linked BG with duplicated balises and error - data used outside ERTM/ETCS and info for one direction
#TEST-VAL-SUB026-3185#REF# EET error expectation (3.16.2.4.4 c) Fehlerhafte Variablenwerte in Balisentelegramm (gelinkt), kein Linking onboard
#TEST-VAL-SUB026-5286#REF# EET error expectation (3.16.2.4.4 d) No linking information is used, message counter do not match

#REQ-UNISIG-SUB026-010127#REF# 3.16.2.4.4.1.b #REQ-UNISIG-SUB026-003793#REF#
Exceptions: Concerning a) and b) of clause 3.16.2.4.4, the ERTMS/ETCS on-board equipment shall not command application of the service brake if
the telegram correctly read from another balise of the group contains the information “Inhibition of balise group message consistency reaction”.
#TEST-VAL-SUB026-5858#REF# FCT 3.16.2.4.4 a) Inhibition of balise group message consistency reaction (balise missing)
#TEST-VAL-SUB026-5856#REF# FCT 3.16.2.4.4 b) Inhibition of balise group message consistency reaction (balise decoding error)
#TEST-VAL-SUB026-5862#REF# EET error expectation Missing duplicated balise in BG with P145

#REQ-DESIGN-CR-0195:02#REF# 3.16.2.4.4.2
Concerning clause 3.16.2.4.4, if the service brake is applied, the location based information stored on-board shall be shortened to the current
position when the train has reached standstill. Refer to appendix A.3.4 for the exhaustive list of information, which shall be shortened.
is realized through A3.4.1.2 m)
realised by: #REQ-UNISIG-SUB026-3024:01#REF#

#REQ-UNISIG-SUB026-3010:01#REF# to.3.16.2.4.4.2 #ANA-UNISIG-ErrorReport-0001:02#REF#
If no linking information is used and a data consistency error is detected by a linked balise group, the RBC shall be informed about the linked
balise group message consistency error.
Packet 4 with M_ERROR=1
#TEST-VAL-SUB026-3054#REF# FCT L0 Error reporting to RBC in UN/L0
#TEST-VAL-SUB026-3058#REF# FCT L1 Error reporting to RBC in SR/L1
#TEST-VAL-SUB026-3181#REF# FCT L2 Missing Balise in BG (Q_LINK=1, no linking on-board)
#TEST-VAL-SUB026-3056#REF# FCT NTC Error reporting to RBC in SN/STM

#REQ-UNISIG-SUB026-007062#REF# to.3.16.2.4.4.2 #ANA-UNISIG-ErrorReport-0004#REF#
The RBC shall be informed also, when a balise is not found or decoded and therefore a duplicate balise is used.
The value M_ERROR shall be the same as the situation without using the duplicate balise.

remark:
This requirement is valid for linked and unlinked balise groups.
TEST APPROACH:
The following aspects have been identified:
1) Balise could not be decoded 
2) balise not found
3) linked BG
4) unlinked BG
#TEST-VAL-SUB026-3183#REF# FCT 1 Balise mit Fehler (keine Telegramm-Dekodierung, kein Linking, gelinkte BG)
#TEST-VAL-SUB026-3181#REF# FCT 2, 3 Missing Balise in BG (Q_LINK=1, no linking on-board)
#TEST-VAL-SUB026-3187#REF# FCT 4 Missing balise in unlinked BG

#REQ-DESIGN-CR-0002#REF# 3.16.2.4.4.3
Concerning clause 3.16.2.4.4, if the service brake is applied, the driver shall be informed that this is due to a balise group message
consistency problem.
the driver have to be informed via system status message (see ERA SRS DMI, chapter 15)
#TEST-VAL-SUB026-3181#REF# FCT basic function Missing Balise in BG (Q_LINK=1, no linking on-board)

#REQ-DESIGN-CR-0327#REF# 3.16.2.4.6
Instead of a message counter corresponding to a given balise group message, it shall be possible to identify a telegram as always fitting all
possible messages of the group.
#TEST-VAL-SUB026-7471#REF# FCT basic function Variablentest M_MCOUNT (M_MCOUNT minimal=0, maximal=253), AKT (M_MCOUNT erlaubt=96, fit all=255)

#REQ-DESIGN-CR-0328#REF# 3.16.2.4.6.1
It shall also be possible to identify a telegram as never fitting any message of the group.
#TEST-VAL-SyAnfSpezCR-0096#REF# FCT basic function Variablentest M_MCOUNT mit Wert 254 (never fitting any message)

#REQ-UNISIG-SUB026-3699#REF# 3.16.2.4.7
Comparing message counters of the received telegrams of a balise group message, excluding the ones complying with 3.16.2.4.6, if their values
are not all identical, or at least one of them complies with 3.16.2.4.6.1, this shall be considered as a message consistency error. The balise
group can, however, be used for location information.
realised by: #REQ-DESIGN-CR-0329:01#REF#

#REQ-UNISIG-SUB026-003812#REF# 3.16.2.4.7.1
In case of single balise group, if the message counter of the received telegram complies with 3.16.2.4.6.1, this shall also be considered as a
message consistency error.
realised by: #REQ-DESIGN-CR-0329:01#REF#

#REQ-DESIGN-CR-0329:01#REF# 3.16.2.4.7 #REQ-UNISIG-SUB026-3699#REF#
#REQ-UNISIG-SUB026-003812#REF#
Comparing message counters of the received telegrams of a balise group message, excluding the ones complying with 3.16.2.4.6, if their values
are not all identical, or at least one of  them complies with 3.16.2.4.6.1, this shall be considered as a message consistency error. The balise
group shall be used for location information.
Rel. 6.4:
Präzisierung des "kann" in ein "muss"
TEST APPROACH:
The following aspects have been identified:
1) Mismatch of M_MCOUNT
2) Multi balise group one with M_MCOUNT=254
3) Single balise group M_MCOUNT=254
#TEST-VAL-SUB026-7136#REF# FCT 1 Message counters of the received telegrams of a balise group message do not match
#TEST-VAL-SUB026-7137#REF# FCT 2 On balsie of BG with M_MCOUNT=254
#TEST-VAL-SUB026-5752#REF# FCT 3 Single balise group, M_MCOUNT = 254 (The telegram never fits any message of the group)

#REQ-DESIGN-CR-0469#REF# 3.16.2.4.8.1
If one (and only one) out of a pair of duplicated balise telegrams received by the on-board includes the information “default balise
information”, the on-board shall ignore any other information included in this telegram and shall consider information from the telegram not
containing “default balise information".
#TEST-VAL-SUB026-3935#REF# FCT basic function Duplicate balises having different data

#REQ-DESIGN-CR-0484#REF# 3.16.2.4.8.2
When duplicated balises are both found and decoded correctly, and both, or none of them, contain "default balise information", the
ERTMS/ETCS on-board equipment shall compose the message using the telegram from the last received balise out of the pair.
#TEST-VAL-SUB026-3935#REF# FCT nominal Duplicate balises having different data
#TEST-VAL-SUB026-5753#REF# FCT reverse Duplicated balise with different content passed revers

#REQ-DESIGN-CR-0395#REF# 3.16.2.4.9 #REQ-UNISIG-SUB026-009509#REF#
If a message has been received containing the information "default balise information", the driver shall be informed.
UNISIG clarification:
The driver is also informed, if a corrected duplicate balise is read.

The information is reset, when the next balise group is read.
TEST APPROACH:
The following points have been identified:
1. Display of "trackside malfunction" status message depending on modes where a DMI is active
2. Display of "trackside malfunction" status message depending on duplicated / not duplicated balises
3. Revocation of "trackside malfunction" status message

For point 1, aspects: 1.1. SB, 1.2. SH, 1.3. FS, 1.4. LS, 1.5. SR, 1.6. OS, 1.7. UN, 1.8. TR, 1.9 PT, 1.10 SN, 1.11 RV and 1.12 NL, were
identified. 
Aspect 1.12 is covered by verification of #REQ-UNISIG-SUB026-010495#REF#
Regarding point 2, aspects 2.1. P254 contained only in one of the duplicated balises, 2.2. P254 contained in both duplicated balises and 2.3.
P254 is contained in a not duplicated balise, were identified.
Point 3 is covered by verification of #REQ-SRS_DMI-004319:01#REF#.
#TEST-VAL-SUB026-4536#REF# FCT 1.1 SB/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4692#REF# FCT 1.2, 1.3, 1.5, 1.6 acceptance P254 in FS/OS/SR/SH
#TEST-VAL-SUB026-4691#REF# FCT 1.4 LS System Configuration Management, Default Balise Information, OBU supports M_VERSION = 0x20
#TEST-VAL-SUB026-4B34#REF# FCT 1.7 acceptance of 'Default Balise/Loop/RIU information' (P254) depending on level
#TEST-VAL-SUB026-4537#REF# FCT 1.8 TR/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4538#REF# FCT 1.9 PT/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4736#REF# FCT 1.10 SN/STM - PR at every passage of an LRBG compliant balise, System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4535#REF# FCT 1.11 RV/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-3935#REF# FCT 2.1, 2.2 Duplicate balises having different data
#TEST-VAL-SUB026-3283#REF# FCT 2.3 Default balise information received together with other packet in the same balise telegram (no duplicated balises)

#REQ-DESIGN-CR-0330#REF# 3.16.2.5.1 #REQ-UNISIG-SUB026-0106#REF#
#REQ-UNISIG-SUB026-1013:02#REF#
An on-board equipment shall reject the message received from a balise group marked as unlinked and command application of the service brake in
the following cases:
a)	A balise is missed inside the unlinked balise group.
b)	A balise is detected, but no telegram is decoded (e.g. wrong CRC).
c)	Variables in the balise group message have invalid values.
d)	Message counters do not match (see 3.16.2.4.7)
TEST APPROACH:
In addition to the straight-forward aspects a, b, c and d, the unlinked balise group message consistency is also tested for each mode. 
However, mode NP is not realised by the ASW (see #REQ-UNISIG-SUB026-004698#REF#). Mode IS is realized by hardware and the EVC In is powered off
in isolation (see #REQ-UNISIG-SUB026-004676#REF#). OBU does permanently command the Emergency Brakes in the ETCS mode SF. Balise as well as RBC
messages are ignored in IS and SF (see #REQ-UNISIG-SUB026-3008#REF# and #REQ-UNISIG-SUB026-3009#REF#). Hence, the modes NP, IS and SF will be
omitted.
#TEST-VAL-SUB026-4702#REF# FCT FS, NL, SB, SR, UN, SH Table 4.5.2 --> Check Balise Group Message Consistency unlinked balise group (FS,NL,SB,SR,UN,SH)
#TEST-VAL-SUB026-4F12#REF# FCT LS Table 4.5.2 --> Unlinked Balise Group Message Consistency (LS)
#TEST-VAL-SUB026-4704#REF# FCT OS, TR, PT, RV Table 4.5.2 --> Unlinked Balise Group Message Consistency (OS,TR,PT,RV)
#TEST-VAL-SUB026-4707#REF# FCT SL, SN Table 4.5.2 --> Unlinked Balise Group Message Consistency (SL,SN)
#TEST-VAL-SUB026-3187#REF# FCT a) Missing balise in unlinked BG
#TEST-VAL-SUB026-3189#REF# FCT b) Balise mit Fehler (keine Telegramm-Dekodierung, ungelinkte BG)
#TEST-VAL-SUB026-3191#REF# FCT c) , CFX00032941 Variables with invalid values in BG marked as unlinked
#TEST-VAL-SUB026-5290#REF# FCT d) Unlinked BG, message counter do not match

#REQ-UNISIG-SUB026-003830#REF# 3.16.2.5.1.1
Exceptions: Concerning a) and b) of clause 3.16.2.5.1, the ERTMS/ETCS on-board equipment:
a)	shall not reject the message and shall not command application of the service brake if the balise not found, or not decoded, is
duplicated within the balise group, the duplicating one is correctly read and contains:
∙	directional information while the orientation of the balise group can still be evaluated, or
∙	only information valid for both directions, or
∙	neither directional information nor information valid for both directions, or
∙	only data to be used by applications outside ERTMS/ETCS, or
∙	only data to be used by applications outside ERTMS/ETCS together with other information valid for both directions.
b)	shall not command application of the service brake if the telegram correctly read from another balise of the group contains the
information “Inhibition of balise group message consistency reaction”.
realised by: #REQ-DESIGN-CR-0196:01#REF#
realised by: #REQ-UNISIG-SUB026-010129#REF#

#REQ-DESIGN-CR-0196:01#REF# 3.16.2.5.1.1.a) #REQ-UNISIG-SUB026-003830#REF#
Exceptions: Concerning a) and b) of clause 3.16.2.5.1, the ERTMS/ETCS on-board equipment shall not reject the message and shall not command
application of the service brake if the balise not found, or not decoded, is duplicated within the balise group, the duplicating one is
correctly read and contains:
∙	directional information while the orientation of the balise group can still be evaluated, or
∙	only information valid for both directions, or
∙	neither directional information nor information valid for both directions, or
∙	only data to be used by applications outside ERTMS/ETCS, or
∙	only data to be used by applications outside ERTMS/ETCS together with other information valid for both directions.
TEST APPROACH:
The aspect a) and b) of clause 3.16.2.5.1 have the sub aspects. 
1) directional information while the orientation of the balise group can still be evaluated, or
2) only information valid for both directions, or
3) neither directional information nor information valid for both directions, or
4) only data to be used by applications outside ERTMS/ETCS, or
5) only data to be used by applications outside ERTMS/ETCS together with other information valid for both directions.
Note: The forwarding of P44 information without orientation is limited to P44 with NID_XUSER = 102 (refer #REQ-UNISIG-SUB026-001148#REF#). This
function is not part of R8 (refer #REQ-SWAnf-009262#REF#) the check of the acceptance of P44 is hence omitted.

The outlined test aspects indicate aspect and sub aspect separated by a dash.
#TEST-VAL-SUB026-3187#REF# FCT a-1 Missing balise in unlinked BG
#TEST-VAL-SUB026-5750#REF# FCT a-2, b-2 A group of two balises duplicating each other treated as a single BG in case where only one balise is correctly read
#TEST-VAL-SUB026-5751#REF# FCT a-3, b-3 Two balise group duplicating each other no information included, one balise missing
#TEST-VAL-SUB026-4H87#REF# FCT a-4, b-4 Unlinked BG with duplicated balises and error - data used outside ERTM/ETCS
#TEST-VAL-SUB026-4H88#REF# FCT a-5, b-5 Unlinked BG with duplicated balises and error - data used outside ERTM/ETCS and info for both directions
#TEST-VAL-SUB026-3189#REF# FCT b-1 Balise mit Fehler (keine Telegramm-Dekodierung, ungelinkte BG)
#TEST-VAL-SUB026-3191#REF# EET error expectation (3.16.2.4.1 c) Variables with invalid values in BG marked as unlinked
#TEST-VAL-SUB026-5290#REF# EET error expectation (3.16.2.4.1 d) Unlinked BG, message counter do not match
#TEST-VAL-SUB026-7710#REF# EET error expectation for a-5 and b-5 Unlinked BG with duplicated balises and error - data used outside ERTM/ETCS and info for one direction

#REQ-UNISIG-SUB026-010129#REF# 3.16.2.5.1.1.b) #REQ-UNISIG-SUB026-003830#REF#
Exceptions: Concerning a) and b) of clause 3.16.2.5.1, the ERTMS/ETCS on-board equipment shall not command application of the service brake if
the telegram correctly read from another balise of the group contains the information “Inhibition of balise group message consistency reaction”.
#TEST-VAL-SUB026-5857#REF# FCT 3.16.2.5.1 a) Inhibition of balise group message consistency reaction (balise missing)
#TEST-VAL-SUB026-5855#REF# FCT 3.16.2.5.1 b) Inhibition of balise group message consistency reaction (balise decoding error)
#TEST-VAL-SUB026-5864#REF# EET error expectation Missing duplicated balise in BG with P145

#REQ-DESIGN-CR-0197:02#REF# 3.16.2.5.2
Concerning clause 3.16.2.5.1, if the service brake is applied, the location based information stored on-board shall be shortened to the current
position when the train has reached standstill. Refer to appendix A.3.4 for the exhaustive list of information, which shall be shortened.
realize through A3.4.1.2 g)
realised by: #REQ-UNISIG-SUB026-2207:01#REF#

#REQ-UNISIG-SUB026-3012:01#REF# to.3.16.2.5.2 #ANA-UNISIG-ErrorReport-0001:02#REF#
If a data consistency error is detected by an unlinked balise group, the RBC shall be informed about the unlinked balise group message
consistency error.
Packet 4 with M_ERROR=2
#TEST-VAL-SUB026-3054#REF# FCT L0 Error reporting to RBC in UN/L0
#TEST-VAL-SUB026-3058#REF# FCT L1 Error reporting to RBC in SR/L1
#TEST-VAL-SUB026-3187#REF# FCT L2 Missing balise in unlinked BG
#TEST-VAL-SUB026-3056#REF# FCT NTC Error reporting to RBC in SN/STM

#REQ-DESIGN-CR-0003#REF# 3.16.2.5.3
Concerning clause 3.16.2.5.1, if the service brake is applied, the driver shall be informed that this is due to a balise group message
consistency problem.
the driver have to be informed via system status message (see ERA SRS DMI, chapter 15)
#TEST-VAL-SUB026-3187#REF# FCT basic function Missing balise in unlinked BG

#REQ-UNISIG-SUB026-0112#REF# 3.16.2.6.1
When the linking reaction leads to train trip or a service brake application, the driver shall be informed that the intervention is due to data
consistency problem with the expected balise group.
the driver have to be informed via system status message (see ERA SRS DMI, chapter 15)
#TEST-VAL-SUB026-3193#REF# FCT basic function Missing Balise in BG (Q_LINK=1, linking on-board)

#REQ-UNISIG-SUB026-0665:01#REF# 3.16.2.6.2
If the service brake is initiated due to the linking reaction, the location based information stored on-board shall be shortened to the current
position when the train has reached standstill. Refer to appendix A.3.4 for the exhaustive list of information, which shall be shortened.
realize through A3.4.1.2 h)
realised by: #REQ-UNISIG-SUB026-2208#REF#

#REQ-UNISIG-SUB026-3014:01#REF# to.3.16.2.6.2 #ANA-UNISIG-ErrorReport-0001:02#REF#
If is detected a linking consistency error (see 3.16.2.3.1 or 3.16.2.3.2), the RBC shall be informed about the balise group linking consistency
error.
Packet 4 with M_ERROR=0
#TEST-VAL-SUB026-3193#REF# FCT basic function Missing Balise in BG (Q_LINK=1, linking on-board)

#REQ-UNISIG-SUB026-003851#REF# 3.16.2.7.1.1
If 2 consecutive linked balise groups announced by linking are not detected and the end of the expectation window of the second balise group has
been passed, the ERTMS/ETCS on-board shall command the service brake and the driver shall be informed. At standstill, the location based
information stored on-board shall be shortened to the current position. Refer to appendix A.3.4 for the exhaustive list of information, which
shall be shortened.
The second part is realized through A.3.4.1.2 l)
realised by: #REQ-DESIGN-CR-0031:01#REF#
realised by: #REQ-DESIGN-CR-0701#REF#

#REQ-DESIGN-CR-0031:01#REF# 3.16.2.7.1.1 #REQ-UNISIG-SUB026-003851#REF#
If 2 consecutive linked balise groups announced by linking are not detected and the end of the expectation window of the second balise group has
been passed, the ERTMS/ETCS on-board shall command the service brake and the driver shall be informed.
#TEST-VAL-SUB026-3275#REF# FCT basic function 2 consecutive linked balise groups announced by linking not detected

#REQ-UNISIG-SUB026-3206:02#REF# to.3.16.2.7.1.1 #ANA-UNISIG-ErrorReport-0001:02#REF#
If is detected a linking RAMS error (see 3.16.2.7.1.1), the RBC shall be informed about the error as a double linking error.
Packet 4 with M_ERROR=7
#TEST-VAL-SUB026-5754#REF# FCT basic function Error report to RBC

#REQ-DESIGN-CR-0745#REF# to.3.16.2.7.1.1
Regarding 3.16.2.7.1: If inside the area of two consecutive announced balise groups a further announced balise group is read, the reaction
according to 3.16.2.7.1 shall not apply.
clarification:
no reaction, when another announced bg is read
#TEST-VAL-SUB026-3959#REF# FCT basic function , CFX00036500 BG validity based on position in expectation window when linking information available

#REQ-UNISIG-SUB026-3001#REF# 3.16.2.7.2.1
If repositioning is announced and the expected repositioning balise group has been found, the ERTMS/ETCS on-board equipment shall keep looking
for a balise group that satisfies the same criteria as this previously expected and already found repositioning balise group, until one of the
following events occurs:
a)	the on-board antenna leaves the expectation window of the repositioning balise group that was announced and already found
b)	a linked balise group that has been announced with known identity is found.
TEST APPROACH:
The following aspects have been identified:
1) second repositioning BG found in expectation window
2) second repositioning BG found outside expectation window 
3) second repositioning BG found in expectation window after linked BG that has been announced with known identity is found
3.1) linking information included in P5 announcing the repositioning BG
3.2) linking information received from repositioning BG
4) second repositioning BG that does not satisfy the same criteria as this previously
found in expectation window
#TEST-VAL-SUB026-3680#REF# FCT 1 first possible location for repo BG start from the previously linked balise group
#TEST-VAL-SUB026-3608#REF# FCT 2 second unannounced repositioning BG outside expectation window former repositioning BG
#TEST-VAL-SUB026-3367#REF# FCT 3.1 OBU stops to look for other BG which agrees former announced repo BG after announced linked BG with known identity has been found
#TEST-VAL-SUB026-3611#REF# FCT 3.2 announced BG and second announced repositioning BG inside expectation window of former repositioning BG
#TEST-VAL-SUB026-3644#REF# FCT 4 lnk repo BG announced, pass BG with valid repo info, repo BG Q_DIR=0, single balise BG and valid repo BG
#TEST-VAL-SUB026-3609#REF# EET error expectation second announced repositioning BG outside expectation window former repositioning BG
#TEST-VAL-SUB026-3657#REF# EET error expectation lnk repo BG announced, pass BG with valid repo info + lnk and valid repo BG

#REQ-UNISIG-SUB026-003859#REF# 3.16.2.7.2.2
If a second balise group is found that satisfies the same criteria as the previously expected and already found repositioning balise group, the
ERTMS/ETCS on-board equipment shall command the service brake and the driver shall be informed. At standstill, the location based information
stored on-board shall be shortened to the current position. Refer to appendix A.3.4 for the exhaustive list of information, which shall be
shortened.
The second part is realized through A.3.4.1.2 l)
realised by: #REQ-UNISIG-SUB026-3002:01#REF#
realised by: #REQ-DESIGN-CR-0701#REF#

#REQ-UNISIG-SUB026-3002:01#REF# 3.16.2.7.2.2 #REQ-UNISIG-SUB026-003859#REF#
If a second balise group is found that satisfies the same criteria as the previously expected and already found repositioning balise group, the
ERTMS/ETCS on-board equipment shall command the service brake and the driver shall be informed.
#TEST-VAL-SUB026-3276#REF# FCT basic function Second repositioning balise group found

#REQ-UNISIG-SUB026-3129#REF# to.3.16.2.7.2.2
If a second balise group is found that satisfies the same criteria as the previously expected and already found repositioning balise group, this
second balisegroup shall not be used.
#TEST-VAL-SUB026-3764#REF# FCT basic function information from second repositioning BG not taken into account

#REQ-UNISIG-SUB026-010132#REF# to.3.16.2.7.2.2 #ANA-UNISIG-ErrorReport-0001:02#REF#
If is detected a repositioning RAMS error (see 3.16.2.7.2.2), the RBC shall be informed about the error as a double repositioning error.
Packet 4 with M_ERROR=8
#TEST-VAL-SUB026-5755#REF# FCT basic function Error report to RBC

#REQ-UNISIG-SUB026-3130:01#REF# zu.3.16.2.7 #ANA-UNISIG-CR0791-0001:01#REF#
If the OBU leaved the modes FS, LS or OS, the RAMS related supervision functions (see 3.16.2.7) shall be ended.
#TEST-VAL-SUB026-3773#REF# FCT FS repositioning info RAMS related supervision functions ended when leaving FS
#TEST-VAL-SUB026-3328#REF# FCT FS two consecutive BGs missing RAMS related supervision function 3.16.2.7.1 stopped when leaving FS
#TEST-VAL-SUB026-3772#REF# FCT LS repositioning info RAMS related supervision functions ended when leaving LS
#TEST-VAL-SUB026-3362#REF# FCT LS two consecutive BGs missing RAMS related supervision function 3.16.2.7.1 stopped when leaving LS
#TEST-VAL-SUB026-3774#REF# FCT OS repositioning info RAMS related supervision functions ended when leaving OS
#TEST-VAL-SUB026-3329#REF# FCT OS two consecutive BGs missing RAMS related supervision function 3.16.2.7.1 stopped when leaving OS

#REQ-UNISIG-SUB026-3698#REF# 3.16.3.1.1
A radio message is consistent when all checks have been completed successfully:
a)	Checks performed by Euroradio protocol have been passed (see Subset-037)
b)	Time stamps checks have been passed (see 3.16.3.3.3)
c)	Variables in the messages do not have in-valid values.

--- FINALISED ---
Subset 37 is realized through the components KBS (part of DCC) and the TCC subsystem SALSA (see realization of Req.
#REQ-IF-ESBO_GSM-0001:02#REF# from /ESBO_SyAnfSpez/).
realised by: #REQ-UNISIG-SUB026-3015:01#REF#

#REQ-UNISIG-SUB026-3016#REF# 3.16.3.1.1.1 #REQ-UNISIG-SUB026-0106#REF#
The on-board shall reject a message transmitted from the trackside if the message is not consistent.
TEST APPROACH:
Following error types can occur
1) Checks performed by Euroradio protocol fails (see Subset-037) 
2) Time stamps checks fails (see 3.16.3.3.3) 
3) Variables in the messages have in-valid values
4) in valid message structure 

Point a) is not in the scope of the ASW refer realization of #REQ-IF-ESBO_GSM-0001:01#REF# and hence omitted.
#TEST-VAL-SUB026-4D11#REF# FCT 2 Check correctness of radio messages; SR, NL
#TEST-VAL-SUB026-4D03#REF# FCT 3 Check correctness of radio messages; FS, SB, SL
#TEST-VAL-SUB026-8009#REF# FCT 4 same packets type for the same direction in the same message
#TEST-VAL-SUB026-3436#REF# EET error expectation Packet 72 - NID_STM

#REQ-UNISIG-SUB026-3017#REF# 3.16.3.1.1.2
The on-board shall inform the trackside if a not consistent message is received.
realised by: #REQ-UNISIG-SUB026-3019#REF#
realised by: #REQ-UNISIG-SUB026-3020#REF#

#REQ-UNISIG-SUB026-3019#REF# 3.16.3.1.1.2 #REQ-UNISIG-SUB026-3017#REF#
#ANA-UNISIG-ErrorReport-0003:01#REF#
If is detected a radio message consistency error (see 3.16.3.1.1 c), the RBC shall be informed about the radio message consistency error.
Paket 4
M_ERROR=3
#TEST-VAL-SUB026-3054#REF# FCT L0 Error reporting to RBC in UN/L0
#TEST-VAL-SUB026-3058#REF# FCT L1 Error reporting to RBC in SR/L1
#TEST-VAL-SUB026-4D03#REF# FCT L2 Check correctness of radio messages; FS, SB, SL
#TEST-VAL-SUB026-3056#REF# FCT NTC Error reporting to RBC in SN/STM

#REQ-UNISIG-SUB026-3020#REF# 3.16.3.1.1.2 #REQ-UNISIG-SUB026-3017#REF#
#ANA-UNISIG-ErrorReport-0003:01#REF#
If is detected a sequence error (see 3.16.3.1.1 b), the RBC shall be informed about the radio sequence error.
Paket 4
M_ERROR=4
#TEST-VAL-SUB026-3054#REF# FCT L0 Error reporting to RBC in UN/L0
#TEST-VAL-SUB026-3058#REF# FCT L1 Error reporting to RBC in SR/L1
#TEST-VAL-SUB026-4D08#REF# FCT L2 Check radio sequence; FS, SB, SL
#TEST-VAL-SUB026-3056#REF# FCT STM Error reporting to RBC in SN/STM

#REQ-UNISIG-SUB026-3015:01#REF# 3.16.3.1.1 #REQ-UNISIG-SUB026-3698#REF#
#REQ-UNISIG-SUB026-1014:02#REF#
#REQ-UNISIG-SUB026-1015:02#REF#
A radio message is consistent when following checks have been completed successfully:
- Time stamps checks have been passed (see 3.16.3.3.3)
AND
- Variables in the message do not have invalid values.
TEST APPROACH:
The following aspects have been identified:
1) Time stamps checks have been passed 
1.1) SB 
1.2) SH 
1.3) PS 
1.4) FS 
1.5) LS
1.6) SR
1.7) OS
1.8) SL
1.9) NL
1.10) UN
1.11) TR 
1.12) PT 
1.13) SN
1.14) RV
2) Variables in the message do not have invalid values
2.1) SB 
2.2) SH 
2.3) PS 
2.4) FS 
2.5) LS
2.6) SR
2.7) OS
2.8) SL
2.9) NL
2.10) UN
2.11) TR 
2.12) PT 
2.13) SN
2.14) RV
#TEST-VAL-SUB026-4D08#REF# FCT 1.1, 1.4, 1.8 Check radio sequence; FS, SB, SL
#TEST-VAL-SUB026-4D09#REF# FCT 1.2, 1.11, 1.12 Check radio sequence; SH, TR, PT
#TEST-VAL-SUB026-7833#REF# FCT 1.3, 2.3 Check correctness of radio messages: PS
#TEST-VAL-SUB026-4D60#REF# FCT 1.5 Check radio sequence; LS
#TEST-VAL-SUB026-4D11#REF# FCT 1.6, 1.9 Check correctness of radio messages; SR, NL
#TEST-VAL-SUB026-4D12#REF# FCT 1.7, 1.14 Check radio sequence; OS, RV
#TEST-VAL-SUB026-3054#REF# FCT 1.10, 2.10 Error reporting to RBC in UN/L0
#TEST-VAL-SUB026-3056#REF# FCT 1.13, 2.13 Error reporting to RBC in SN/STM
#TEST-VAL-SUB026-4D03#REF# FCT 2.1, 2.4, 2.8 Check correctness of radio messages; FS, SB, SL
#TEST-VAL-SUB026-4D04#REF# FCT 2.2, 2.11, 2.12 Check correctness of radio messages; SH, TR, PT
#TEST-VAL-SUB026-4F13#REF# FCT 2.5 Check correctness of radio messages; LS
#TEST-VAL-SUB026-4D06#REF# FCT 2.6, 2.9 Check correctness of radio messages; SR, NL
#TEST-VAL-SUB026-4D07#REF# FCT 2.7, 2.14 Check correctness of radio messages; OS, RV
#TEST-VAL-SUB026-3968#REF# EET CFX00039594 Error reporting and optional packets handling, time stamp is unknown
#TEST-VAL-SUB026-5461#REF# EET CFX00040174 Message with P12 from RBC rejected
#TEST-VAL-SUB026-3838#REF# EET error expectation Data consistency check in PT

#REQ-UNISIG-SUB026-3753#REF# 3.16.3.1.2
Emergency messages shall be transmitted either as high priority data or as normal priority data.
The OBU-part is derived from the fact, that EMs have to be accepted via the high as well as from normal priority channel.
realised by: #REQ-DESIGN-CR-0100#REF#

#REQ-UNISIG-SUB026-3679#REF# 3.16.3.1.3
Other messages shall be sent as normal priority data.
is realized through 8.5.2
realised by: #REQ-DESIGN-CR-0033#REF#
realised by: #REQ-UNISIG-SUB026-3680#REF#

#REQ-UNISIG-SUB026-3678#REF# 3.16.3.1.3.1
Messages shall only be accepted when received with the data priority for which they are specified.
realised by: #REQ-DESIGN-CR-0100#REF#
realised by: #REQ-DESIGN-CR-0033#REF#

#REQ-DESIGN-CR-0100#REF# to..3.16.3.1.3.1 #REQ-UNISIG-SUB026-3753#REF#
#REQ-UNISIG-SUB026-3678#REF#
Emergency messages shall be accepted as normal priority and as high priority data.
#TEST-VAL-SyAnfSpezCR-0006#REF# ECT M15 high/normal priority data M15 accepted as normal priority and as high priority data
#TEST-VAL-SUB026-4A51#REF# ECT M16 high priority data Unconditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-4993#REF# ECT M16 normal priority data Check table 4.5.2 Information->TC Excluding Big Metal Masses (TR - L1, L2, STM)

#REQ-DESIGN-CR-0033#REF# to.3.16.3.1.3.1 #REQ-UNISIG-SUB026-3679#REF#
#REQ-UNISIG-SUB026-3678#REF#
All radio messages from trackside, exception the emergency messages, shall only be accepted when received as normal priority data.
#TEST-VAL-SUB026-8039#REF# ECT basic function SSP, ASP, TSR, TrackCondition, RouteSuitability, PlainTxtMsg over High Priority Channel

#REQ-UNISIG-SUB026-0668#REF# 3.16.3.1.4
The chapters 3.16.3.2 to 3.16.3.5 define data consistency principles and corresponding checks for data transmitted as normal priority data.
For high priority data, the checks shall not apply.
#TEST-VAL-SUB026-3253#REF# FCT high priority data no time stamp check for high priority data
#TEST-VAL-SUB026-3913#REF# FCT normal priority data Usage of message timeStamp sent as normal/priority radio data

#REQ-UNISIG-SUB026-010303#REF# 3.16.3.2.2 #ANA-UNISIG-RBC-Message-Consistency-0002#REF#
If the train receives a message from trackside with an time stamp in the future, this message shall not be accepted.
UNISIG clarification: this is derived from the second sentence in 3.16.3.2.2
#TEST-VAL-SUB026-7643#REF# FCT basic function Message time stamp in the future

#REQ-UNISIG-SUB026-0671#REF# 3.16.3.3.2
There shall always be a time stamp increment between consecutive messages.
#TEST-VAL-SUB026-3913#REF# FCT same time stamp Usage of message timeStamp sent as normal/priority radio data
#TEST-VAL-SUB026-3969#REF# FCT time stamp increment Usage of message timeStamp sent over normal/priority radio channel

#REQ-UNISIG-SUB026-0672#REF# 3.16.3.3.3 #REQ-UNISIG-SUB026-0106#REF#
If the time stamp of the last received message is lower than or equal to the former one its content shall not be used.
#TEST-VAL-SUB026-3913#REF# FCT timestamp equal to former one Usage of message timeStamp sent as normal/priority radio data
#TEST-VAL-SUB026-3969#REF# FCT timestamp lower than former one Usage of message timeStamp sent over normal/priority radio channel

#REQ-UNISIG-SUB026-3401#REF# 3.16.3.3.3.1
Only time stamps of messages received as normal priority data shall be used.
#TEST-VAL-SUB026-3969#REF# FCT basic function Usage of message timeStamp sent over normal/priority radio channel
#TEST-VAL-SUB026-3913#REF# EET error expectation Usage of message timeStamp sent as normal/priority radio data

#REQ-UNISIG-SUB026-0673#REF# 3.16.3.3.4
If, at the initiation of the communication session, the time stamp is set to unknown the message shall be accepted.

#DSC-UNISIG-SUB026-003906#REF#

Figure 60: Supervision of sequence
#TEST-VAL-SUB026-3019#REF# FCT basic function Initiation of a communication session by RBC

#REQ-UNISIG-SUB026-0116#REF# 3.16.3.4.1
When the difference between the time stamp of the latest consistent received message and the current on-board time is greater than the
T_NVCONTACT parameter (national value), the on-board shall apply the reaction as defined in the next section.
#TEST-VAL-SUB026-3584#REF# EET CFX00038180 driver manually changes to level 2 communication session to the respective RBC already exists - T_NVCONTACT expiry
#TEST-VAL-SUB026-7023#REF# EET CFX00123026 T_NVCONTACT expiry during termination of communication session
#TEST-VAL-SUB026-7024#REF# EET CFX00123026 T_NVCONTACT expiry during during termination of safe connection
#TEST-VAL-SUB026-8270#REF# FCT CFX00176435 Reinitialization of T_NVCONTACT supervision by outdated RBC message
#TEST-VAL-SUB026-3197#REF# FCT M_NVCONTACT=0 NVCONTACT supervision, M_NVCONTACT=0 - Train trip
#TEST-VAL-SUB026-4H29#REF# FCT M_NVCONTACT=1 T_NVCONTACT supervision is based on RBC message T_TRAIN
#TEST-VAL-SUB026-3199#REF# FCT M_NVCONTACT=2 NVCONTACT supervision, M_NVCONTACT=2 - No reaction
#TEST-VAL-SUB026-3300#REF# EET error expectation T_NVCONTACT bei RBC-Handover mit einer Session
#TEST-VAL-SUB026-4D53#REF# EET error expectation Check radio link (only level 2/3): SN/STM
#TEST-VAL-SUB026-7932#REF# EET error expectation Messages sent with high priority data are not subject to radio data consistency checks

#REQ-DESIGN-CR-0557#REF# 3.16.3.4.1.1
After the on-board equipment has switched to L2 or 3 with no communication session established, the current onboard time shall be compared with
the on-board time at the moment of the level transition (instead of the time stamp of the latest consistent received message) until a new
consistent message has been received.
realised by: #REQ-DESIGN-CR-0754:02#REF#

#REQ-DESIGN-CR-0754:02#REF# 3.16.3.4.1.1 #REQ-DESIGN-CR-0557#REF#
#ANA-UNISIG-CR0787-0001:01#REF#
If no consistent message from the RBC is received starting from the level announce up to the switch to level 2/3 (for example no communication
session is established), the current on board time shall be compared with the on board time at the moment of the level transition, until a new
consistent message has been received.
TEST APPROACH:
The following aspects have been identified:
1) communication session is established but no consistent message from the RBC is received
2) communication session is established consistent message from the RBC is received
2.1) T_NVCONTACT expired when passing level transition location 
2.2) T_NVCONTACT not expired when passing level transition location
3) no communication session established
#TEST-VAL-SUB026-3926#REF# FCT 1 Time used for radioLinkSupervision during levelTransition, radioHoleArea
#TEST-VAL-SUB026-3721#REF# FCT 2.1 UN->TR due to radio link supervision failure - no save radio connection after receiving MA/SSP/GP from RBC
#TEST-VAL-SUB026-5880#REF# FCT 2.2 Supervision of safe radio connection during level transition to L2/3
#TEST-VAL-SUB026-3887#REF# FCT 3 Supervision of T_NVCONTACT starts at time of lvlTransition when no session exists
#TEST-VAL-SUB026-8269#REF# EET CFX00177153 T_NVCONTACT supervision last message in L1 area includes level transition announcement

#REQ-UNISIG-SUB026-3132#REF# 3.16.3.4.1.2
When an RBC/RBC handover has been announced, the current onboard time shall be compared with the time stamp of the latest consistent message
from the Handing over RBC until the train considers the Accepting RBC as the supervising one (refer to 3.15.1.3.5). From then on the current
onboard time shall be compared with the time stamp of the latest received consistent message from the Accepting RBC.
#TEST-VAL-SUB026-3779#REF# FCT basic function Supervision of safe radio connection RBC/RBC handover connection to both RBCs

#REQ-UNISIG-SUB026-3569#REF# to.3.16.3.4.1.2 #ANA-UNISIG-CR0748-0001#REF#
Exception to 3.16.3.4.1.2:
If no consistent message from the Accepting RBC is available, the current onboard time shall be compared with the on-board time at the moment of
the change of supervision to the Accepting RBC, until a new consistent message has been received.
TEST APPROACH:
The following aspects have been identified:
1) one mobile available
2) two mobiles available
#TEST-VAL-SUB026-4849#REF# FCT 1 One mobile RBC transition, T_NVCONTACT before and after supervision change
#TEST-VAL-SUB026-7184#REF# FCT 2 Supervision of the disconnect delay time during RBC/RBC handover
#TEST-VAL-SUB026-8228#REF# EET error expectation T_NVCONTACT supervision based on current OBU time of supervision change to ACC-RBC

#REQ-DESIGN-CR-0556#REF# 3.16.3.4.1.3
After a train has passed an announced radio hole and until a new consistent message has been received, the current onboard time shall be
compared with the on-board time when the train front end left the radio hole (instead of the time stamp of the latest consistent received
message).
see figures 61 and 62
#DSC-UNISIG-SUB026-003918#REF#

Figure 61: Supervision of the safe radio connection (Message received within the Window) #DSC-UNISIG-SUB026-003920#REF#
Figure 62: Supervision of the safe radio connection (No message received within the Window)
#TEST-VAL-SUB026-3926#REF# FCT basic function Time used for radioLinkSupervision during levelTransition, radioHoleArea

#REQ-UNISIG-SUB026-0674#REF# 3.16.3.4.2
It shall be possible to select one of the following reactions (National value) :
a)	Train trip
b)	Apply service brake
c)	No reaction
#TEST-VAL-SUB026-3197#REF# ECT a) NVCONTACT supervision, M_NVCONTACT=0 - Train trip
#TEST-VAL-SUB026-3198#REF# ECT b) NVCONTACT supervision, M_NVCONTACT=1 - Apply service brake
#TEST-VAL-SUB026-3199#REF# ECT c) NVCONTACT supervision, M_NVCONTACT=2 - No reaction

#REQ-UNISIG-SUB026-0675:01#REF# 3.16.3.4.3 #REQ-UNISIG-SUB026-010111#REF#
For all reactions, if no new consistent message has been received after an additional delay time (as defined in A.3.1), the on-board shall
release the safe radio connection and then set-up it again (maintaining the communication session).
This is only relevant, when a session is established.
TEST APPROACH:
The following aspects have been identified:
1) one connection
2) two connections
#TEST-VAL-SUB026-5731#REF# FCT 1 T_NVCONTACT supervision causes delayed release of safe connection
#TEST-VAL-SUB026-5736#REF# FCT 2 T_NVCONTACT supervision, delayed release of safe connection in combination with RBC transition
#TEST-VAL-SUB026-3837#REF# EET error expectation Error reaction for supervision of safe radio connection does not lead to establishment of safe radio connection

#REQ-UNISIG-SUB026-010124#REF# to.3.16.3.4.3
Exception to 3.16.3.4.3:
The on-board shall stop the supervision of the disconnect delay time, when the safe radio connection is lost at the beginning or during the
disconnect delay time.
On-board shall not release the safe radio connection once more.
TEST APPROACH:
The following aspects have been identified:
1) outage before the delay
2) outage during the delay
3) outage when T_NVCONTACT expires
4) session handling
#TEST-VAL-SUB026-5744#REF# FCT 1 T_NVCONTACT supervision, short outage of safe connection before disconnect delay timer start
#TEST-VAL-SUB026-5735#REF# FCT 2 T_NVCONTACT supervision, delayed release of safe connection in combination short outage of safe connection within delay time
#TEST-VAL-SUB026-5738#REF# FCT 3 T_NVCONTACT supervision, delayed release of safe connection in combination outage of safe connection when T_NVCONTACT expires
#TEST-VAL-SUB026-5734#REF# FCT 4 T_NVCONTACT supervision, delayed release of safe connection in combination with session release

#REQ-UNISIG-SUB026-010622#REF# to.3.16.3.4.3
Exception to 3.16.3.4.3:
The on-board shall stop the supervision of the disconnect delay time, if another RBC becomes the supervised RBC.
UNISIG clarification: the release of the safe connection to another RBC should be avoided
#TEST-VAL-SUB026-7183#REF# FCT basic function Supervision of the disconnect delay time, if another RBC becomes the supervised RBC
#TEST-VAL-SUB026-7184#REF# EET error exectation Supervision of the disconnect delay time during RBC/RBC handover

#REQ-UNISIG-SUB026-010125#REF# to.3.16.3.4.3
clarifications to 3.16.3.4.3:
1.) The on-board shall release the safe radio connection and then set-up it again, even if the function
"supervision of safe radio connection" is not active anymore (i.e. onboard changes the mode/level).

2.) The new set up shall be execute also in a radio hole. After this 3.5.4.2 and 3.5.4.4 are valid.
reasons of clarification:
1.) Otherwise the requirement cannot executed with M_NVCONTACT=Train Trip
2.) A regulation for radio hole is necessary
TEST APPROACH:
The following aspects have been identified:
1) T_NVCONTACT supervision not active anymore
2) radio hole
#TEST-VAL-SUB026-5733#REF# FCT 1 T_NVCONTACT supervision, delayed release of safe connection in combination change mode/level where T_NVCONTACT supervision inactive
#TEST-VAL-SUB026-5732#REF# FCT 2 T_NVCONTACT supervision, delayed release of safe connection in combination with TC radio hole

#REQ-UNISIG-SUB026-3023:01#REF# to.3.16.3.4.3 #ANA-UNISIG-ErrorReport-0003:01#REF#
If is detected a radio message consistency error (see 3.16.3.4.1), the RBC shall be informed about the safe radio connection error.
Paket 4
M_ERROR=5
#TEST-VAL-SUB026-4680#REF# FCT basic function Supervision of safe radio connection in LS

#REQ-UNISIG-SUB026-0676#REF# 3.16.3.4.4
When the reaction leads to train trip or a service brake application, the driver shall be informed that no safe radio message has been received
in due time.
#TEST-VAL-SUB026-3197#REF# FCT M_NVCONTACT=0 NVCONTACT supervision, M_NVCONTACT=0 - Train trip
#TEST-VAL-SUB026-3198#REF# FCT M_NVCONTACT=1 NVCONTACT supervision, M_NVCONTACT=1 - Apply service brake
#TEST-VAL-SUB026-3199#REF# EET M_NVCONTACT=2 NVCONTACT supervision, M_NVCONTACT=2 - No reaction

#REQ-UNISIG-SUB026-0677#REF# 3.16.3.4.5
If the service brake is initiated, the following reaction shall be taken;
a)	For brake command release conditions refer to section 3.14.1.7.
b)	If no new consistent message is received until the train reaches standstill, the location based information stored on-board shall be
shortened to the current position. Refer to appendix A.3.4 for the exhaustive list of information, which shall be shortened.
point a is only a reference
realised by: #REQ-UNISIG-SUB026-3209#REF#

#REQ-UNISIG-SUB026-3209#REF# 3.16.34.5.b #REQ-UNISIG-SUB026-0677#REF#
If the service brake is initiated after a radio link error and no new message is received until the train reaches standstill, the current MA,
track description and linking information shall be shortened to the current position.
realize through A3.4 i an table A3.4
realised by: #REQ-UNISIG-SUB026-2209#REF#

#REQ-UNISIG-SUB026-3721#REF# to.3.16.3.4.5 #ANA-UNISIG-T_CONTACT-0003#REF#
The reception of following messages shall not restart radio link supervision:
- Configuration Determination
- Initiation of Communication Session
- Acknowledgement of Termination
#TEST-VAL-SUB026-3776#REF# FCT M32 Reception of Configuration Determination does not restart radio link supervision
#TEST-VAL-SUB026-3775#REF# FCT M38, M39 T_NVCONTACT supervision M_NVCONTAC=1

#REQ-UNISIG-SUB026-0117#REF# 3.16.3.5.1 #ANA-UNISIG-Preprocessing-Message-0001#REF#
As soon as a consistent message (see 3.16.3.1.1) including the request for acknowledgement is received, the on-board shall send an
acknowledgement to the trackside.
TEST APPROACH:
The following aspects have been identified:
1) message for the current level
2) buffered message
#TEST-VAL-SUB026-5793#REF# ECT 1 Variable test M_ACK
#TEST-VAL-SUB026-7169#REF# FCT 2 Evaluation of M_ACK for buffered messages

#REQ-UNISIG-SUB026-0680#REF# 3.16.3.5.3
The acknowledgement message shall refer to the identity of the concerned message sent by the RBC.
#TEST-VAL-SUB026-5793#REF# FCT basic function Variable test M_ACK

#REQ-UNISIG-SUB026-3752#REF# 3.16.4.1
In level 2/3, if a radio communication session is established, errors shall be reported as soon as the availability of a safe radio connection
permits.
realised by: #REQ-UNISIG-SUB026-3022:01#REF#

#REQ-UNISIG-SUB026-3022:01#REF# 3.16.4.1 #REQ-UNISIG-SUB026-3752#REF#
#ANA-UNISIG-CR0296-0001#REF#
An error shall be reported when
- a radio communication session is established
AND
- a safe radio connection is available.
UNISIG clarification:
if no communication is exists, the error report is considered as sent (see 3.5.4.5)
TEST APPROACH:
The following aspects have been identified:
1) level dependency (for all levels)
2) error report is considered as sent when no communication exists
2.1) announced radio hole
2.2) no session / session setup
2.3) safe radio connection down
2.4) safe radio connection setup
#TEST-VAL-SUB026-3058#REF# FCT 1) L1 Error reporting to RBC in SR/L1
#TEST-VAL-SUB026-5754#REF# FCT 1) L2 Error report to RBC
#TEST-VAL-SUB026-3056#REF# FCT 1) NTC Error reporting to RBC in SN/STM
#TEST-VAL-SUB026-3612#REF# FCT 2.1 OBU does not reports the accumulated error reports after leaving radio hole
#TEST-VAL-SUB026-7053#REF# FCT 2.2 OBU does not reports the accumulated error reports after session establishment
#TEST-VAL-SUB026-3614#REF# FCT 2.3 loss of the safe radio connection, OBU does not send accumulated error reports after connection is set-up again
#TEST-VAL-SUB026-3613#REF# FCT 2.4 T_NVCONTACT expiry, OBU does not report BG error report after connection is set-up again
#TEST-VAL-SUB026-3054#REF# FCT 1) L0 Error reporting to RBC in UN/L0

#REQ-UNISIG-SUB026-3579#REF# to.3.16.4.1 #ANA-UNISIG-RBCHandover-0008#REF#
A radio error report during handover shall be sent to the inducing RBC. All other error reports shall be sent to the supervisiing RBC.
#TEST-VAL-SUB026-3722#REF# FCT basic function RBC1/RBC2 Handover; RBC1 version 0x10, RBC2 version 0x20
#TEST-VAL-SUB026-3779#REF# EET error expectation Supervision of safe radio connection RBC/RBC handover connection to both RBCs

#REQ-UNISIG-SUB026-003956#REF# 3.16.4.3
If linking information is used on-board, no error reporting shall be done for balise groups marked as linked but not included in the linking
information.
is duplicated to 3.16.2.4.3
realised by: #REQ-UNISIG-SUB026-0658#REF#

Chapter 3.17

#REQ-UNISIG-SUB026-003970#REF# 3.17.2.1
The on-board equipment shall be able to operate with (i.e. shall support) any of the ERTMS/ETCS system version numbers X included in the
envelope of legally operated system versions, as defined in chapter 6.
realised by: #REQ-UNISIG-SUB026-3544:03#REF#
realised by: #REQ-UNISIG-SUB026-3543:03#REF#

#REQ-UNISIG-SUB026-3544:03#REF# to.3.17.2.1 #REQ-SRS-004278:01#REF#
#REQ-UNISIG-SUB026-003970#REF#
The highest major version X supported by the on-board equipment shall be parameterizable.

The following major system versions are at least possible:
X=1
X=2 -  default for baseline 3
It should be possible to restrict a baseline 3 OBU for a track with baseline 2 only
#TEST-VAL-SUB026-7089#REF# FCT X=1 Determining of opperated system version, OBU suports major version 1
#TEST-VAL-SUB026-7092#REF# FCT X=2 Determining of opperated system version, OBU suports major version 2

#REQ-UNISIG-SUB026-3543:03#REF# to.3.17.2.1 #REQ-SRS-004278:01#REF#
#REQ-UNISIG-SUB026-003970#REF#
The OBU shall use the parameterized major system version for determining the operated system version and for the handling of trackside data.
TEST APPROACH:
Following aspects have been identified:
1) parameterized system version X=1
2) parameterized system version X=2
#TEST-VAL-SUB026-7089#REF# FCT 1 Determining of opperated system version, OBU suports major version 1
#TEST-VAL-SUB026-7092#REF# FCT 2 Determining of opperated system version, OBU suports major version 2

#REQ-UNISIG-SUB026-003972#REF# 3.17.2.2
The on-board equipment shall operate with only one system version at a time, i.e. it shall behave according to the whole set of requirements
applicable to a system version (refer to chapter 6 in case the operated system version is older than the last one introduced in this release of
the SRS).
realised by: #REQ-UNISIG-SUB026-010595#REF#
realised by: #REQ-UNISIG-SUB026-003978#REF#
realised by: #REQ-UNISIG-SUB026-003986#REF#
realised by: #REQ-UNISIG-SUB026-003995#REF#

#REQ-UNISIG-SUB026-010595#REF# 3.17.2.3 #REQ-UNISIG-SUB026-003972#REF#
The on-board equipment shall determine the operated system version, in relation to non-RBC trackside constituents, as the system version number
X transmitted by any balise, loop or RIU, if this system version number X is higher than the currently operated one.
RIU isn't realized
realised by: #REQ-UNISIG-SUB026-003974#REF#

#REQ-UNISIG-SUB026-003974#REF# to.3.17.2.3 #REQ-UNISIG-SUB026-010595#REF#
The on-board equipment shall determine the operated system version, in relation to non-RBC trackside constituents, as the system version number
X transmitted by any balise or loop, if this system version number X is higher than the currently operated one.
#TEST-VAL-SUB026-7093#REF# FCT basic functiom Determining the operated system version, in relation to non-RBC trackside constituents
#TEST-VAL-SUB026-7094#REF# EET error expectation Determining the operated system version of multiple M_VERSION BG

#REQ-UNISIG-SUB026-003975#REF# to.3.17.2.3 #ANA-UNISIG-Versionsmanagement-0007#REF#
The on-board equipment shall determine the operated system version from balises only, if:
- the balise is used for the balise group message (balise is not ignored because of version management, VBC or duplicate)
AND
- the balise group message is used (not rejected/ignored due to message consistency error, linking).
UNISIG clarification: see analysis
TEST APPROACH:
The following aspects have been identified:
1) data consistency error
2) balise group isn't announced by linking
3) not compatible balise
4) balise with default balise information
5) duplicated balise
6) balise marked by VBC

VBC is not part of R8 refer #REQ-SWAnf-008828#REF#.
#TEST-VAL-SUB026-7095#REF# FCT 1 Determining the operated system version of erroneous BG
#TEST-VAL-SUB026-7097#REF# FCT 2 Determining the operated system version, ignored BG
#TEST-VAL-SUB026-7092#REF# FCT 3 Determining of opperated system version, OBU suports major version 2
#TEST-VAL-SUB026-7096#REF# FCT 4, 5 Determining the operated system version of BG with duplicated balise
#TEST-VAL-SUB026-7098#REF# FCT 6 Determining the operated system version, VBC marked balise

#REQ-UNISIG-SUB026-003977#REF# to.3.17.2.3 #ANA-UNISIG-Versionsmanagement-0008#REF#
The on-board equipment shall determine the operated system version from loop only, if
- loop is announced
AND
- loop version is compatible.
UNISIG clarification: see analysis
TEST APPROACH:
The following aspects have been identified:
1) unannounced loop
2) not compatible loop
#TEST-VAL-SUB026-7130#REF# FCT 1, 2 Evaluation of operated system version from not accepted loop message

#REQ-UNISIG-SUB026-003978#REF# 3.17.2.5 #REQ-UNISIG-SUB026-003972#REF#
On receiving the order to operate system version from balise group, the on-board equipment shall immediately operate the system version given in
the order. After the order is executed, the requirement 3.17.2.3 shall be again applied for any further received balise telegram/loop message or
any further contacted RIU.
realised by: #REQ-UNISIG-SUB026-010594#REF#

#REQ-UNISIG-SUB026-010594#REF# to.3.17.2.5 #REQ-UNISIG-SUB026-003978#REF#
On receiving the order to operate system version from balise group, the on-board equipment shall evaluate the system version given in the order
first and translate the other information from the balisegroup on basis the new operated system version.

remark: The new system version is initial valid after the whole balise group is read.
UNISIG clarification: the balise information should be translate with the defined system version in the same balise telegram, if available.
TEST APPROACH:
The operated system version is relevant for the evaluation of 
1) driver acknowledgment of text messages 
2) received P3
The requirement is relevant for 2) only.
#TEST-VAL-SUB026-7099#REF# FCT 2 Evaluation of balise message according to received system version order

#REQ-UNISIG-SUB026-010506#REF# to.3.17.2.5
If the received order to operate system version contains a version greater than the highest version number X supported by the on-board
equipment, the system version order shall be ignored and a basic diagnostic event shall be triggered.
UNISIG clarification: the definition of an obu reaction for this case is necessary
#TEST-VAL-SUB026-7103#REF# FCT basic function Evaluation of system version order

#REQ-UNISIG-SUB026-003982#REF# 3.17.2.6
If a mismatch has been detected between the country or region identifier read from a balise/loop and the corresponding identifier(s) for which a
set of national values is used onboard, the on-board equipment shall consider the system version number X transmitted by this balise/loop as the
operated one and shall comply again with requirement 3.17.2.3.
UNISIG clarification:
the default NVs are valid for all NID_C
#TEST-VAL-SUB026-7104#REF# FCT basic function Determining the operated system version, NID_C mismatch

#REQ-UNISIG-SUB026-003984#REF# 3.17.2.7
If the on-board equipment does not support the system version number X transmitted by a non-RBC trackside constituent or the one specified in
the balise group order, it shall consider the operated system version as unchanged.
TEST APPROACH:
Following aspects were identified:
1) System Version order
2) Version number X transmitted by a non-RBC trackside constituent
Aspect 1) is covered by #REQ-UNISIG-SUB026-010506#REF#
#TEST-VAL-SUB026-7106#REF# FCT 2 Version number X transmitted by a non-RBC trackside constituent ot supported by OBU

#REQ-UNISIG-SUB026-003986#REF# 3.17.2.8 #REQ-UNISIG-SUB026-003972#REF#
In case of communication session established with an RBC, the system version of the RBC shall take precedence on the operated system version in
relation to non-RBC constituents and on system version ordered from balise group; the operated system version shall be determined according to
the following principles:
a)	if the on-board equipment is in level 0, NTC or 1 (e.g. entrance in level 2/3 area), the RBC system version shall be operated when the
transition to level 2/3 is executed;
b)	if the on-board equipment is in level 2/3 (SoM procedure or order received from trackside), the RBC system version shall be operated
immediately;
c)	in case of session established with an accepting RBC (RBC/RBC Handover), the accepting RBC system version shall be operated as soon as
the engine has passed the RBC/RBC border location with its maximum safe front end;
d)	in case the on-board equipment switches from level 2/3 to another level (e.g. exit from a level 2/3 area), the system version control in
relation to non-RBC constituents shall be again applied and the balise group orders shall be again considered;
e)	in case the engine passes the RBC/RBC border location with its maximum safe front end and no session is established with the accepting
RBC, the system version control in relation to non-RBC constituents shall be again applied and the balise group orders shall be again
considered.
realised by: #REQ-UNISIG-SUB026-010477#REF#
realised by: #REQ-UNISIG-SUB026-010479#REF#
realised by: #REQ-UNISIG-SUB026-010478#REF#
realised by: #REQ-UNISIG-SUB026-010552#REF#

#REQ-UNISIG-SUB026-010477#REF# 3.17.2.8.a,.b #REQ-UNISIG-SUB026-003986#REF#
In case of communication session established with an RBC, the system version of the RBC shall take precedence on the operated system version in
relation to non-RBC constituents and on system version ordered from balise group; the operated system version shall be determined according to
the following principles:
- if the on-board equipment is in level 0, NTC or 1, the RBC system version shall be operated when the transition to level 2/3 is executed;

- if the on-board equipment is in level 2/3, the RBC system version shall be operated immediately.
TEST APPROACH:
The communication session is established when receiving M32 (refer 3.5.3.8) from OBU point of view.
The communication session is considered as terminated when receiving M39 (3.5.5.2c) from OBU point of view. 
#TEST-VAL-SUB026-7107#REF# FCT basic function Determining the operated system version based on session state and level
#TEST-VAL-SUB026-8275#REF# EET error expectation Processing of BL2 and BL3 information at level transition

#REQ-UNISIG-SUB026-010479#REF# 3.17.2.8.c #REQ-UNISIG-SUB026-003986#REF#
In case of communication session established with an RBC, the system version of the RBC shall take precedence on the operated system version in
relation to non-RBC constituents and on system version ordered from balise group; the operated system version shall be determined according to
the following principles:
- in case of an executive RBC/RBC Handover and a session is established with the accepting RBC, the accepting RBC system version shall be
operated as soon as the supervision is changed from the handing over RBC to the accepting RBC.
UNISIG clarification:
the system version of the accepting RBC is used, when this RBC is the supervised RBC.
#TEST-VAL-SUB026-7108#REF# FCT basic function Determining the operated system version during RBC handover

#REQ-UNISIG-SUB026-010478#REF# 3.17.2.8.d #REQ-UNISIG-SUB026-003986#REF#
#ANA-UNISIG-Versionsmanagement-0009#REF#
In case of communication session established with an RBC, the system version of the RBC shall take precedence on the operated system version in
relation to non-RBC constituents and on system version ordered from balise group; the operated system version shall be determined according to
the following principles:
- in case the on-board equipment switches from level 2/3 to another level, the system version control in relation to non-RBC constituents shall
be again applied and the balise group orders shall be again considered

clarification:
The system version control in relation to non-RBC constituents starts with the next message/telegram from non-RBC trackside constituents on the
current system version.
UNISIG clarification:
The "non RBC constituents"system version shall not be determined in parallel, if the RBC system version is in use.
TEST APPROACH:
The following aspects have been identified:
1) border BG with System Version order = 0x10
2) border BG with M_VERSION=0x20
#TEST-VAL-SUB026-7109#REF# FCT 1 Determining the operated system version, LTO from BG with System Version order
#TEST-VAL-SUB026-7132#REF# FCT 2 Determining the operated system version, LTO from BG with increased M_VESRSION

#REQ-UNISIG-SUB026-010552#REF# to.3.17.2.8.e #REQ-UNISIG-SUB026-003986#REF#
#ANA-UNISIG-Versionsmanagement-0009#REF#
In case no session is established to the supervising RBC  (i.e., session is lost or the supervision is changed to an accepting RBC without a
established session), the system version control in relation to non-RBC constituents shall be again applied and the balise group orders shall be
again considered.

clarification:
The system version control in relation to non-RBC constituents starts with the next message/telegram from non-RBC trackside constituents on the
current system version.
UNISIG clarification:
generalization, if the session is lost inside a L2/3 area

clarification point: see 3.17.2.8 d
#TEST-VAL-SUB026-7110#REF# FCT basic function Determining the operated system version based on session status to supervising RBC

#REQ-UNISIG-SUB026-003993#REF# 3.17.2.9 #REQ-UNISIG-SUB026-010244#REF#
The system version currently operated when the on-board equipment is switched off (i.e. enters No Power mode) shall be retained and re-used when
powered on.
#TEST-VAL-SUB026-7111#REF# FCT basic function Storage of operated system version

#REQ-UNISIG-SUB026-003995#REF# 3.17.2.9.1 #REQ-UNISIG-SUB026-003972#REF#
If the on-board equipment loses the information (failure situation), the highest supported system version shall be used.
realised by: #REQ-UNISIG-SUB026-008069#REF#

#REQ-UNISIG-SUB026-008069#REF# to.3.17.2.9.1 #REQ-UNISIG-SUB026-003995#REF#
If no operated system version is stored on-board equipment (first start up, failure situation), the parametrized version number X shall be used
as supported system version when powered on.

In this case Y=0 shall be used.
UNISIG clarification: 
the parametrized version is used
TEST APPROACH:
Following aspects have been identified:
1) parameterized system version X=1
2) parameterized system version X=2
#TEST-VAL-SUB026-7089#REF# FCT 1 Determining of opperated system version, OBU suports major version 1
#TEST-VAL-SUB026-7092#REF# FCT 2 Determining of opperated system version, OBU suports major version 2

#REQ-UNISIG-SUB026-0687#REF# 3.17.3.2
All messages transmitted by an RBC shall contain data only related to one system version.
TEST APPROACH:
The paragraph defines basically a track side requirement. The OBU requirement is to hold independent system version for each RBC connection.
#TEST-VAL-SUB026-7108#REF# FCT basic function Determining the operated system version during RBC handover

#REQ-DESIGN-CR-0590#REF# 3.17.3.3
The on-board equipment shall check the system version prior to any further checks (data consistency, ..), as they depend on the system version.
#TEST-VAL-SUB026-3986#REF# FCT basic function Consistency with old M_VERSION
#TEST-VAL-SUB026-5465#REF# EET error expectation Processing of BG with not compatible version and several data inconsistencies

#REQ-UNISIG-SUB026-0691#REF# 3.17.3.5
The on-board equipment shall check the ERTMS/ETCS system version number X transmitted by any balise:
a)	In all levels, if this system version number X equals to 0, the balise information shall be ignored.
b)	In all levels, if this system version number X is different from 0 and lower than the lowest system version number X supported by the
on-board equipment, it shall be able to interpret the balise information, to the extent defined for each type of information (see chapter 6 for
detailed requirements). If the on-board is not able to interpret the information, this shall be considered as a message consistency error.
c)	In all levels, if this system version number X is amongst its supported ones, the on-board equipment shall be able to interpret the
balise information. See chapter 6 for detailed requirements.
d)	In levels 1, 2 and 3, if this system version number X is greater than the highest version number X supported by the on-board equipment,
the information from this balise shall be ignored, the train shall be tripped and an indication shall be given to the driver.
e)	In levels 0 and NTC, if this system version number X is greater than the highest version number X supported by the on-board equipment,
the information from this balise shall be ignored and no reaction shall be applied.
realised by: #REQ-UNISIG-SUB026-3736#REF#
realised by: #REQ-UNISIG-SUB026-0690:01#REF#
realised by: #REQ-UNISIG-SUB026-010442#REF#
realised by: #REQ-UNISIG-SUB026-010474#REF#
realised by: #REQ-UNISIG-SUB026-3735:01#REF#

#REQ-UNISIG-SUB026-3736#REF# to.3.17.3.5 #REQ-UNISIG-SUB026-0691#REF#
The on-board equipment shall check the ERTMS/ETCS system version transmitted by any read balise.
TEST APPROACH:
Following aspects have been identified:
1) all balise of BG taking into account
2) version check for ignored BG
#TEST-VAL-SUB026-7113#REF# FCT 1 Multiple TRIP due to BG with unsupported M_VERSION
#TEST-VAL-SUB026-7114#REF# FCT 2 CHECK of ERTMS/ETCS system version for ignored BG

#REQ-UNISIG-SUB026-0690:01#REF# 3.17.3.5.a) #REQ-UNISIG-SUB026-0691#REF#
If the system version number X from a balise equals to 0, the balise including all information shall be ignored.
UNISIG clarification:
A reading of an old balise  with version X=0 within an ETCS balise group has be no influence on the evaluation of this balise group.
#TEST-VAL-SUB026-7123#REF# FCT basic function , CFX00035504 System version number X from a balise equals to 0
#TEST-VAL-SUB026-3812#REF# EET error expectation Balise with version=0 within a ETCS balise group does no influence ETCS balise group

#REQ-UNISIG-SUB026-010442#REF# 3.17.3.5.b) #REQ-UNISIG-SUB026-0691#REF#
If the system version number X	from a balise is different from 0 and lower than the lowest system version number X supported by the on-board
equipment, it shall be able to interpret the balise information, to the extent defined for each type of information (see chapter 6 for detailed
requirements). If the on-board is not able to interpret the information, this shall be considered as a message consistency error.

--- FINALISED ---
The case, that the system version number X  from trackside is different from 0 and lower than the lowest system version number X  supported by
the on-board equipment, cannot occur with baseline 3.
#ANALYSE-VALUNISIG-5348#REF# FCT The requirement has not functional relevance in R8 refer column FINALISED.

#REQ-UNISIG-SUB026-010474#REF# 3.17.3.5.c) #REQ-UNISIG-SUB026-0691#REF#
If this system version number X  from a balise is amongst its supported ones, the on-board equipment shall be able to interpret the balise
information.
every balise telegramm is decoded with his own version
#TEST-VAL-SUB026-7112#REF# FCT basic function Every balise telegramm is decoded with his own version

#REQ-UNISIG-SUB026-3735:01#REF# 3.17.3.5.d,.e) #REQ-UNISIG-SUB026-0691#REF#
#REQ-UNISIG-SUB026-005196#REF#
#ANA-UNISIG-Versionsmanagement-0001:01#REF#
If the system version number X	from a balise is greater than the highest version number X supported by the on-board equipment, the information
from this balise shall be ignored.
Additional a trip shall be applied and an indication shall be given to the driver, if
- the train is in level 1, 2 or 3
AND
- the train is not in mode SB, PS, SL, NL, PT or RV.

In all other situations no reaction and no indication to the driver shall be applied.
UNISIG clarification:
mode PS is added
TEST APPROACH:
Following aspects have been identified:
1) mode dependency 
1.1) SB
1.2) PS
1.3) SH
1.4) FS
1.5) LS
1.6) SR
1.7) OS
1.8) SL
1.9) NL
1.10) UN
1.11) TR
1.12) PT
1.13) SN
1.14) RV
2) level dependency
2.1) L0
2.2) NTC
2.3) L1
2.4) L2/L3
#TEST-VAL-SUB026-4536#REF# FCT 1.1 SB/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-7116#REF# FCT 1.2 Determining the operated system version, in relation to non-RBC trackside constituents
#TEST-VAL-SUB026-4878#REF# FCT 1.3 Balise telegram with a non compatible version of the ERTMS/ETCS language received SH/L1
#TEST-VAL-SUB026-3206#REF# FCT 1.4 BG with unsupported M_VERSION: transition into TR
#TEST-VAL-SUB026-4690#REF# FCT 1.5 System Configuration Management in LS, OBU supports M_VERSION = 0x10 and 0x20
#TEST-VAL-SUB026-4254#REF# FCT 1.6, 2.3 transition SR(L2) -> SR(L1) -> TR(L1)[65]
#TEST-VAL-SUB026-4119#REF# FCT 1.7, 2.4 Mode transition from OS to TR due to BG with incompatible version
#TEST-VAL-SUB026-4539#REF# FCT 1.8 SL/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4534#REF# FCT 1.9 NL/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-3209#REF# FCT 1.10, 2.1 BG with unsupported M_VERSION in L0
#TEST-VAL-SUB026-4537#REF# FCT 1.11 TR/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4538#REF# FCT 1.12 PT/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4736#REF# FCT 1.13, 2.2 SN/STM - PR at every passage of an LRBG compliant balise, System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4535#REF# FCT 1.14 RV/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-3259#REF# EET error expectation One balise with in BG has incompatible version SN/NTC

#REQ-UNISIG-SUB026-004018#REF# 3.17.3.6
In level 1 the on-board equipment shall check the ERTMS/ETCS system version number X transmitted by any Euroloop found:
a)	if this system version number X is lower than the lowest system version number X supported by the on-board equipment, it shall be able
to interpret the loop information, to the extent defined for each type of information (see chapter 6 for detailed requirements). If the on-board
is not able to interpret the information, this shall be considered as a message consistency error.
b)	if this system version number X is amongst its supported ones, the on-board equipment shall be able to interpret the loop information.
See chapter 6 for detailed requirements.
c)	If this system version number X is greater than the highest version number X supported by the on-board equipment, no reaction shall be
applied and the information from this loop shall be ignored.

--- FINALISED ---
The case, that the system version number X  from trackside is different from 0 and lower than the lowest system version number X  supported by
the on-board equipment, cannot occur with baseline 3.
realised by: #REQ-UNISIG-SUB026-0693:01#REF#

#REQ-UNISIG-SUB026-0693:01#REF# 3.17.3.6 #REQ-UNISIG-SUB026-004018#REF#
In level 1 the on-board equipment shall check the ERTMS/ETCS system version number X transmitted by any Euroloop found:
∙	If this system version number X is amongst its supported ones, the on-board equipment shall be able to interpret the loop information.
∙	If this system version number X is greater than the highest version number X supported by the on-board equipment, no reaction shall be
applied and the information from this loop shall be ignored.
#TEST-VAL-SUB026-7115#REF# FCT basic function Check of ERTMS/ETCS system version number X transmitted by Euroloop

#REQ-UNISIG-SUB026-0694:01#REF# 3.17.3.7
The on-board equipment shall check the ERTMS/ETCS system version number X transmitted the first time any RBC is contacted (including RBC hand
over) or any RIU is contacted. Refer to section 3.5.3.8 for details.
is realized through the reference 3.5.3.8
realised by: #REQ-UNISIG-SUB026-0421:01#REF#

#REQ-UNISIG-SUB026-0697:02#REF# 3.17.3.11
For trackside information only differing by Y with regards to the highest system version number X supported by on-board, the on-board equipment
shall not consider the reception of unknown packet/message as a message data consistency error (i.e. use of spare value for NID_PACKET or
NID_MESSAGE) and shall ignore the content of the unknown packet/message in the following cases:
a)	unknown packet included in a balise telegram/loop message related to the higher system version;
b)	unknown radio message from an RBC or RIU operating with the higher system version;
c)	unknown packet from an RBC or RIU operating with the higher system version, included in a message in which one or more optional packet
can be added according to the version operated by on-board.
TEST APPROACH:
The following aspects have been identified:
1) unknown packet from BG
2) unknown packet from LOOP
3) unknown packet from RBC
4) unknown message from RBC
5) unknown packet from RIU
6) unknown message from RIU
The function radio infill is not part of R8 the verification of aspect 5 and 6 is hence omitted. 
#TEST-VAL-SUB026-7117#REF# FCT 1 Unknown packet from BG
#TEST-VAL-SUB026-3646#REF# FCT 2 loop trackside minor version > OBU minor version, with infill MA, unknown pkt infill/none infill
#TEST-VAL-SUB026-7118#REF# FCT 3, 4 Unknown message/packet from RBC

#REQ-UNISIG-SUB026-010387#REF# to.3.17.3.11 #ANA-UNISIG-Versionsmanagement-0006#REF#
If obu checks the minor version of a trackside information, the following own minor versions shall be used depend of the supported major
version:
X=1 => Y=1
X=2 => Y=0
UNISIG clarification: a definiion of a own minor version for obu is necessary
#TEST-VAL-SUB026-7117#REF# FCT basic function Unknown packet from BG

#REQ-UNISIG-SUB026-3254#REF# to.3.17.3.11 #ANA-UNISIG-CR0796-0002#REF#
If OBU received an unknown RBC or RIU message the syntax and time stamp shall be checked at first (see /UNISIG SUBSET 026/, Kap. 3.16.3.1.1).
The check for the variables shall be contained only the invariant part of the message, i.e. the Message ID and the length of the message.
#TEST-VAL-SUB026-7119#REF# FCT basic function Syntax and time stamp check for unknown RBC message

#REQ-UNISIG-SUB026-3255#REF# to.3.17.3.11 #ANA-UNISIG-CR0796-0003#REF#
If the syntax or the time stamp of an unknown RBC or RIU message not corrected, a error message for a syntax or time stamp error shall be send.
#TEST-VAL-SUB026-7119#REF# FCT basic function Syntax and time stamp check for unknown RBC message

#REQ-UNISIG-SUB026-3256#REF# to.3.17.3.11 #ANA-UNISIG-CR0796-0003#REF#
If OBU ignored an unknown RBC or RIU message during the version check the acknowledge for this message shall be send, if the syntax and time
stamp of this message is corrected and if the acknowledgement is requested.
#TEST-VAL-SUB026-3650#REF# FCT basic function trackside minor version > OBU minor version, acknowledgment for unknown message send by RBC

#REQ-UNISIG-SUB026-3257#REF# to.3.17.3.11 #ANA-UNISIG-CR0796-0003#REF#
If OBU ignored an unknown RBC or RIU message during the version check but the syntax and the time stamp of this message is corrected, the
message shall be considered for supervision of T_CONTACT.
#TEST-VAL-SUB026-3648#REF# FCT basic function trackside minor version > OBU minor version, RBC sends unknown message, syntax and time stamp correct

Chapter 3.18

#REQ-DESIGN-CR-0394#REF# 3.18.2.2
Trains shall be supervised according to the National Values of the current infrastructure if they are available on-board.
#TEST-VAL-SUB026-3210#REF# FCT basic function Supervised according to the National Values of the current infrastructure
#TEST-VAL-SUB026-3458#REF# EET error expectation Appliance of NV (V_NVONSIGHT)

#REQ-UNISIG-SUB026-004054#REF# 3.18.2.3
National Values are transmitted with the area(s) (country or region) in which they are applicable. They shall become applicable at a defined
location, or shall be applicable immediately.
TEST APPROACH:
The following aspects have been identified:
1) NV applicable at a defined location
2) NV applicable immediately
#ANALYSE-VALUNISIG-7532#REF# FCT The requirement does not define unambiguously the expected OBU behavior if a message includes new NV and an override dependent trip condition.
#TEST-VAL-SUB026-5886#REF# FCT 1 New set of NV becoming applicable overwrite the one currently applicable NV
#TEST-VAL-SUB026-3366#REF# FCT 2 New set of NV becoming applicable overwrite the one currently applicable NV regardless of the country or region identifier
#TEST-VAL-SUB026-7083#REF# EET CFX00156924 Evaluation of new national values without definition
#TEST-VAL-SUB026-7026#REF# EET error expectation Evaluation of P3 with new D_NVOVTRP, trip order and P137 from one BG message
#TEST-VAL-SUB026-7027#REF# EET error expectation Evaluation of P3 with new T_NVOVTRP from BG not included in the List of Balises in SR Authority
#TEST-VAL-SUB026-7028#REF# EET error expectation Evaluation of P3 with new D_NVOVTRP/T_NVOVTRP from LT border BG

#REQ-UNISIG-SUB026-004055#REF# to.3.18.2.3 #ANA-UNISIG-NationalValues-0003#REF#
If the national value Q_NVLOCACC is changed and the value becomes valid, the new Q_NVLOCACC is used at first with the next read balise group.
UNISIG clarification: the new value isn't used for the current LRBG. This is also valid, when the national values are received in a balise
telegramm and these national values becomes immediatly valid.
#TEST-VAL-SUB026-5838#REF# FCT basic function Variable test Q_NVLOCACC

#REQ-DESIGN-CR-0167#REF# 3.18.2.4
Evaluating a balise group message, the balise identity information referring to the country or region shall be used to ensure that correct
National Values are used.
#TEST-VAL-SUB026-3210#REF# FCT basic function Supervised according to the National Values of the current infrastructure
#TEST-VAL-SUB026-7139#REF# EET error expectation Evaluation of NV if BG message neglected

#REQ-DESIGN-CR-0041:02#REF# 3.18.2.5
For each National Value, the corresponding Default Value shall be used as fall back value if:
  the National Value  is not available, or
  a mismatch has been detected between the country or region identifier read from a balise group and the corresponding identifier(s) of the
applicable set with which the National Value was received and stored.
#TEST-VAL-SUB026-3210#REF# EET CFX00037712 Supervised according to the National Values of the current infrastructure
#TEST-VAL-SyAnfSpezCR-0010#REF# EET CFX00037712 New national values from track
#TEST-VAL-SUB026-7083#REF# EET CFX00156924 Evaluation of new national values without definition
#TEST-VAL-SUB026-3292#REF# FCT basic function Löschen von National Values
#TEST-VAL-SUB026-2012#REF# EET error expectation Evaluation of P3 NID_C list
#TEST-VAL-SUB026-3457#REF# EET error expectation set/reset of NV (V_NVONSIGHT)
#TEST-VAL-SUB026-4316#REF# EET error expectation fall back of V_NVSTFF, D_NVSTFF

#REQ-DESIGN-CR-0044#REF# 3.18.2.7 #REQ-UNISIG-SUB026-010244#REF#
The National Values currently applicable when the on-board equipment is switched off (i.e. enters No Power mode) shall be retained and shall
remain applicable when powered on.
TEST APPROACH:
The following aspects have been identified:
1) basic software functionality 
1.1) Operated system version 1
1.2) Operated system version 2
2) software hardware integration
#TEST-VAL-SUB026-5622#REF# FCT 1.1 Storage on reading of remanent stored NV
#TEST-VAL-SUB026-5997#REF# FCT 1.2 Storage on reading of remanent stored NV
#TEST-SWHWINT-SWVAL-FKT-0001#REF# FCT 2 Nicht löschen der National Values (NP, IS, SF)

#REQ-UNISIG-SUB026-3487#REF# 3.18.2.8.1
When a new set of National Values becomes applicable its content shall always overwrite the corresponding National Values currently applicable
regardless of the country or region identifier(s).
TEST APPROACH:
The following aspects have been identified:
1) NV applicable at a defined location
2) NV applicable immediately
#TEST-VAL-SUB026-5886#REF# FCT 1 New set of NV becoming applicable overwrite the one currently applicable NV
#TEST-VAL-SUB026-3366#REF# FCT 2 New set of NV becoming applicable overwrite the one currently applicable NV regardless of the country or region identifier
#TEST-VAL-SUB026-3365#REF# EET CFX00038113 EB revocation in relation to Q_NVEMRRLS=0
#TEST-VAL-SUB026-4H26#REF# EET error expectation New M_NVCONTACT (Apply service brake) taken into account immediately
#TEST-VAL-SUB026-4H27#REF# EET error expectation New M_NVCONTACT (Train trip) taken into account immediately
#TEST-VAL-SUB026-4H30#REF# EET error expectation New T_NVCONTACT taken into account immediately

#REQ-DESIGN-CR-0042:01#REF# 3.18.2.9
A previously received set of National Values which is not yet applicable shall be deleted if:
  a new set of National Values is received, or
  the ERTMS/ETCS on-board equipment is switched off (i.e., enters No Power mode).
TEST APPROACH:
The requirement aspect deletion of not yet applicable NV due to switch off (NP is not a operation mode of the ASW) defines that no remanent
storage of not yet applicable NV is requested. The development process ensures that only requested function are implemented a separate
verification is not needed. 
The following aspects have been identified:
1) D_VALIDNV=0
2) D_VALIDNV>0
3) announced P203 information, deleted due to receiving P3
#TEST-VAL-SUB026-5642#REF# FCT 1 , CFX00078913 Announced not yet valid NV overwritten by new NV with D_VALIDNV=0
#TEST-VAL-SUB026-4H12#REF# FCT 2 New set of Nations Values deletes a previously set which is not yet valid
#TEST-VAL-SUB026-5656#REF# FCT 3 Validity of P203 information after receiving new NV without P203
#TEST-VAL-SUB026-5619#REF# EET CFX00078913 P203 - valid packet structure

#REQ-DESIGN-CR-0043:01#REF# 3.18.2.10
If a National Value becomes invalid, i.e., a mismatch has been detected between the country or region identifier read from a balise group and
the corresponding identifier(s) of the applicable set with which the National Value was received and stored, then it shall be deleted.
#TEST-VAL-SUB026-3292#REF# FCT basic function Löschen von National Values

#REQ-DESIGN-CR-0392#REF# 3.18.2.11
When a new set of National Values becomes applicable, any on-going supervision involving an overwritten National Value of type time or distance
shall continue, but using the corresponding value from the new set. However, the starting location or starting time shall remain unchanged.
TEST APPROACH:
The following aspects have been identified:
1) time
1.1) T_NVOVTRP
1.2) T_NVCONTACT
2) distance
2.1) D_NVROLL
2.2) D_NVOVTRP
2.3) D_NVPOTRP
2.4) D_NVSTFF
#TEST-VAL-SUB026-3450#REF# FCT 1.2 starting time unchanged, when the new NV is being considered - T_NVCONTACT
#TEST-VAL-SUB026-3449#REF# FCT 2.1 starting location unchanged, when the new NV is being considered - D_NVROLL
#TEST-VAL-SUB026-3937#REF# FCT 2.2, 1.1 Validity of received NV when they are under supervision -- Time/Distance
#TEST-VAL-SUB026-7832#REF# FCT 2.3 starting location unchanged, when the new NV is being considered - D_NVPOTRP
#TEST-VAL-SUB026-5887#REF# FCT 2.4 , CFX00034527 Reception of new D_NVSTFF in SR
#TEST-VAL-SyAnfSpezCR-0103#REF# EET CFX00034527 D_NVSTFF und D_NVOVTRP bei Override im SR-Mode

#REQ-UNISIG-SUB026-007293:01#REF# to.3.18.2.11 #ANA-UNISIG-NationalValues-0001:01#REF#
A change of M_NVCONTACT to a less restrictive value shall not to effect an ongoing T_NVCONTACT reaction.

Remark: The extension of T_NVCONTACT, including to T_NVCONTACT=infinite, during an ongoing T_NVCONTACT reaction has also no effect of this
reaction.
#TEST-VAL-SUB026-5688#REF# FCT M_NVCONTACT change Change of M_NVCONTACT during ongoing T_NVCONTACT reaction
#TEST-VAL-SUB026-7040#REF# FCT T_NVCONTACT change Change of T_NVCONTACT during ongoing T_NVCONTACT reaction

#REQ-UNISIG-SUB026-008061#REF# to.3.18.2.11 #ANA-UNISIG-NationalValues-0002#REF#
When a new set of National Values that is applicable at a defined location has been received,  the new set of National Values shall be used by
the speed and distance monitoring functionality for all targets behind the defined location.
Note: This implies, that the new set of National Values is already used in the area of the old set of National Values, e.g. for a deceleration
curve with a target location behind the defined location.
Justification: The aim of the deceleration curves is to protect the target location. Thus the safety margins for the target location are
relevant for the whole deceleration curve, even if the deceleration curve starts in the area with the old safety margins.
#TEST-VAL-SUB026-5659#REF# FCT basic function Evaluation of announced NV depending on the target location
#TEST-VAL-SUB026-5656#REF# EET error expectation Validity of P203 information after receiving new NV without P203

#REQ-UNISIG-SUB026-0122:02#REF# 3.18.3.2 #REQ-UNISIG-SUB026-0053#REF#
Before starting a mission, the following Train Data shall be acquired by the ERTMS/ETCS on-board equipment of a leading engine
a)	Train category(ies)
b)	Train length
c)	Traction / brake parameters
d)	Maximum train speed
e)	Loading gauge
f)	Axle load category
g)	Traction system(s) accepted by the engine
h)	Train fitted with airtight system
i)	List of National Systems available on-board
j)	Intentionally deleted
k)	Axle number
realised by: #REQ-DESIGN-CR-0415:01#REF#

#REQ-UNISIG-SUB026-004099#REF# 3.18.3.2.2
Exception: The driver shall never be involved in the entry/ modification/validation of the Train Data “Traction system(s) accepted by the
engine”, “List of National Systems available on-board” and “Axle number”.

--- FINALISED ---
The definition, which data the driver can input, is described in ERS SRS DMI, chapter "Train data window(s).

Requirements are defined for a parametrization of the other data.
#REQ-SAS_DMI-002640#REF#

#REQ-UNISIG-SUB026-0125:01#REF# 3.18.3.3
At standstill, it shall be possible for the driver to enter, modify and revalidate the Train Data that requires driver validation according to
the specific train implementation.
is realized with enabling conditions for button "train data" in ERA SRS DMI

#REQ-UNISIG-SUB026-004103#REF# 3.18.3.3.1
In normal operation after the start of mission, if a train movement is detected while the driver is modifying or revalidating the Train Data,
the ERTMS/ETCS on-board equipment shall trigger the brake command.
UNISIG clarification:
SB is to be commanded, analogous to procedure "Changing Train Data from sources different from the driver"
TEST APPROACH:
The following aspects were identified:
1) Train Data modified/re-validated
2) NTC Data modified/re-validated 
#TEST-VAL-SUB026-5885#REF# FCT 1 Train movement is detected while the driver is modifying or revalidating the Train Data
#TEST-VAL-SUB035-0423#REF# FCT 2 SUB035 V2.1.6 Kap. 13.1.1.2.7(train data entry/specific STM data cancelled by ETCS-Onboard)

#REQ-DESIGN-CR-0748:02#REF# 3.18.3.4 #REQ-UNISIG-SUB026-0635:01#REF#
#REQ-DESIGN-CR-0153#REF#
#REQ-DESIGN-CR-0154#REF#
#REQ-DESIGN-CR-0155#REF#
#ANA-UNISIG-TrainData-0002:01#REF#
Following any entry/modification of Train Data when a communication session is already established or following the successful establishment of
a communication session when valid Train Data are already available (e.g. when approaching a level 2/3 area or an accepting RBC area), the
ERTMS/ETCS on-board equipment of the leading engine shall send the following set of Train Data to the RBC:
a)	Train category(ies).
b)	Train length.
c)	Maximum train speed.
d)	Loading gauge.
e)	Axle load category.
f)	Traction system(s) accepted by the engine.
g)	Train fitted with airtight system.
h)	List of National Systems available on-board
i)	Axle number
UNISIG clarification: "List of National Systems available on-board means": all STMs, that are in CS, HS or DA (see analysis)
TEST APPROACH:
The following aspects have been identified:
1. Comm Session already established - driver changes train data
2. Comm Session already established - train data changed from external source
3. Comm Session already established - list of STM changes - leading engine
4. Comm Session already established - list of STM changes - non leading engine
5. No Comm Session, valid train data on board - Comm Session established - leading engine
6. No Comm Session, invalid train data on board - Comm Session established - leading engine

NOTE: aspect 2 will not be tested because feature "train data changed from external source" is postponed.
#TEST-VAL-SUB026-3184#REF# FCT 1 SoM - Train data is sent to RBC
#TEST-VAL-SUB026-3865#REF# FCT 3 OBU sends train data due to change of list of available STMs
#TEST-VAL-SUB026-3B99#REF# FCT 4 OBU does not send train data due to change of list of available STMs while in NL
#TEST-VAL-SUB026-3280#REF# FCT 5 Zugdaten zum RBC senden im L2 Ankündigungsbereich
#TEST-VAL-SUB026-3298#REF# FCT 6 No train data is sent to RBC after session establishment in modes SL and NL
#TEST-VAL-SUB026-3297#REF# EET error expectation Train Data sent to ACC RBC
#TEST-VAL-SUB026-3987#REF# EET error expectation Train data after loss of radio communication
#TEST-VAL-SUB026-4277#REF# EET error expectation Evaluation of train data in state TBR
#TEST-VAL-SUB026-5135#REF# EET error expectation Manual LT L1->L2, train data is sent to RBC after communication session is established
#TEST-VAL-SUB026-5213#REF# EET error expectation OBU sends train data due to change of list of available STMs (STM send FA State)

#REQ-UNISIG-SUB026-0712:01#REF# to.3.18.3.4.1 #ANA-UNISIG-ETCSLanguage-0007#REF#
The OBU shall reject Acknowledgement of Train Data messages (message 8) with a time stamp "Reference to received train data message"
lower than the initially send train data message.

Note: Repeating of Train data messages shall not affect this check.
UNISIG clarification: see analysis

an error reaction (error report) is not necessary
#TEST-VAL-SUB026-4H90#REF# FCT basic function Acceptance of M8 regarding timestamp in relation to the timestamp of sent M129
#TEST-VAL-SUB026-4H91#REF# EET error expectation Acceptance of M8 regarding timestamp in relation to the timestamp of sent M129 after change of train data

#REQ-UNISIG-SUB026-3641#REF# 3.18.3.4.2
In case the safe radio connection is lost before the acknowledgement is received, the Train Data shall be sent again once the safe radio
connection has been re-established within the on-going communication session.
#TEST-VAL-SUB026-3661#REF# FCT basic function valid train data sent again once the safe connection has been re-established

#REQ-UNISIG-SUB026-010141#REF# to.3.18.3.4.2 #REQ-DESIGN-CR-0093:01#REF#
In case a communication session is established and no acknowledgement of reception of train data is received from the RBC within a fixed waiting
time (see appendix to chapter 3, List of Fixed Value Data) after sending the train data message, the message shall be repeated with the fixed
waiting time after each repetition.
UNISIG clarification:
a rule is have to defined, when the RBC not answers.
#TEST-VAL-SUB026-3222#REF# FCT basic function Acknowledgment of train data

#REQ-UNISIG-SUB026-004124#REF# 3.18.3.7
In case the Train Data regarding train category, axle load category, loading gauge or traction system has been changed and the train is at
standstill:
a)	the location based information stored on-board shall be shortened to the current position of the train. Refer to appendix A.3.4 for the
exhaustive list of information, which shall be shortened.
b)	the stored MA, linking and track description, which have been received from the RBC after a level 2/3 transition or a RBC transition for
a further location has been ordered, shall be deleted.
part a is realized through A3.4 j)

UNISIG clarification:
the deletion is not relevant for a rbc transition order, because the RTO and therefore the RTO buffer has been deleted with part a).
realised by: #REQ-UNISIG-SUB026-3138:01#REF#
realised by: #REQ-DESIGN-CR-0700:01#REF#

#REQ-UNISIG-SUB026-3138:01#REF# 3.18.3.7.b #REQ-UNISIG-SUB026-004124#REF#
In case the Train Data regarding train category, axle load, loading gauge or power supply has been changed during a level announce to level 2/3
and the train is at standstill, stored MAs, linking and track description in the level transition buffer shall be deleted.

note: the following information are a part of track description (see 3.7.1.1 c):
- Static Speed Profile (SSP)
- gradient profile
- Axle load Speed Profile (ASP)
- Speed restriction to ensure a given permitted braking distance
- track conditions
- route suitability data
- areas where reversing is permitted
- changed adhesion factor
UNISIG clarification:
the conditions "data changed" and "standstill" have not get simultaneously.
If the train data are changed not at standstill, the deletion of information are executed not until standstill.

traction system can only be changed with external train data.
TEST APPROACH:
It has to be distinguished between deleted (D) and unchanged (U) buffered information.
1. National Values (U)
2. Linking (D)
3. Movement Authority + (optional) Mode Profile + (optional) List of Balises for SH area (D)
4. Gradient Profile (D)
5. International SSP (D)
6. Axle Load speed profile (D)
7. Temporary Speed Restriction (U)
8. Inhibition of revocable TSRs from balises in L2/3 (U)
9. Route Suitability Data (D)
10. Adhesion Factor (D)
11. Plain Text Information (U)
12. Fixed Text Information (U)
13. Geographical Position (U)
14. Track Conditions excluding big metal masses (D)
15. Unconditional Emergency Stop (U)
16. Conditional Emergency Stop (U)
17. Reversing Area Information (D)
18. Reversing Supervision Information (D)
19. Permitted Braking Distance Information (D)
20. Level Crossing information (U)

The selective deletion of information within one set of information has to be tested.
Further more the release of a set of information in case of deleting all information in a set of information has to be tested
The deletion of buffered information due to change of train category, axle load and loading gauge has to be evaluated. 
The available traction system can be changed by sources different from the driver only. This feature is not part of R8. The verification for the
aspect change of traction system is hence omitted.
The driver choice train data entry from driver is available in standstill only. Change of train data by sources different from the driver is not
supported in R8. Hence no separate verification concerning the condition standstill is needed. 
#TEST-VAL-SUB026-5896#REF# FCT D for 14; U for 15, 16 Handling of buffered Movement Authority + Mode Profile + List of Balises for SH area in case of train data change
#TEST-VAL-SUB026-5890#REF# FCT D for 2, loading gauge NTC->L2 Level transition buffer information evaluation due to loading gauge change
#TEST-VAL-SUB026-5895#REF# FCT D for 3 Handling of buffered Movement Authority + Mode Profile + List of Balises for SH area in case of train data change
#TEST-VAL-SUB026-3725#REF# FCT D for 3 (MA); train train category L0->L2 Level transition buffer information evaluation due to train category change
#TEST-VAL-SUB026-5894#REF# FCT D for 4, 5, 19 Handling of buffered P21, P27 and P52 in case of train data change
#TEST-VAL-SUB026-5889#REF# FCT D for 6, 17, 18; U for 1, 7, 11, 13 Handling of buffered P3, P51, P65, P72, P79 and P138/139 in case of train data change
#TEST-VAL-SUB026-3727#REF# FCT D for 9, 10; U for 12; axle load L1->L2 Level transition buffer information evaluation due to axle load change
#TEST-VAL-SUB026-5897#REF# FCT U for 8, 20 Handling of buffered P64 and P88 in case of train data change
#TEST-VAL-SUB026-3726#REF# EET error expectation L0->L1 Level transition buffer information not deleted due to train data change
#TEST-VAL-SUB026-3728#REF# EET error expectation L1->L2 Level transition buffer information not deleted due change of train length
#TEST-VAL-SUB026-5898#REF# EET error expectation Selective release of information and set of information in case of train data change

#REQ-UNISIG-SUB026-3734#REF# 3.18.3.8
In case the Train Data regarding train length has been increased, the currently used track description, if any, shall be considered as unknown
in rear of the former min safe rear end of the train.
UNISIG clarification:
"track description" is limit to SSP, ASP and GA
realised by: #REQ-UNISIG-SUB026-3139:01#REF#

#REQ-UNISIG-SUB026-3139:01#REF# 3.18.3.8 #REQ-UNISIG-SUB026-3734#REF#
#ANA-UNISIG-CR0500-0002:02#REF#
In case the Train Data regarding train length has been increased, the currently used track descriptions SSP, ASP and GAP, if available, shall be
considered as unknown in rear of the former min safe rear end of the train.
not relevant for track descriptions TC, RS, RV area and adhesion factor
#TEST-VAL-SUB026-3811#REF# FCT ASP ASP in case of the train data regarding train length has been increased
#TEST-VAL-SUB026-5888#REF# FCT SSP/GP Train data entry - SSP/GP considered as unknown under the added train length

#REQ-UNISIG-SUB026-3150#REF# to.3.18.3.8 #ANA-UNISIG-CR0500-0002:02#REF#
In case the Train Data regarding train length has been increased and the track description is set unknown under the added length, the
indications "ENTRY IN FULL SUPERVISION" (see #REQ-UNISIG-SUB026-0178#REF#) or "ENTRY IN ON SIGHT" (see
#REQ-UNISIG-SUB026-0201#REF#) to the driver shall be activated.
#TEST-VAL-SUB026-3728#REF# FCT FS L1->L2 Level transition buffer information not deleted due change of train length
#TEST-VAL-SUB026-3729#REF# FCT OS train length increased just before switch from SR/L1 to OS/L1

#REQ-DESIGN-CR-0149:01#REF# 3.18.4.1.2
If allowed by a National value, it shall be possible for the driver to change driver ID while the train is running.
is realized with enabling conditions for button "driver ID" in ERA SRS DMI

#REQ-UNISIG-SUB026-2020#REF# 3.18.4.1.3
It shall be possible to enter driver ID also in a non-leading engine.
is defined also in 4.7.2
realised by: #REQ-UNISIG-SUB026-3290:01#REF#

#REQ-UNISIG-SUB026-0127#REF# 3.18.4.2.1
The driver shall have the possibility to enter the ERTMS/ETCS level during a start of a mission.
realized by SoM, S2
realised by: #REQ-UNISIG-SUB026-1086:01#REF#

#REQ-DESIGN-CR-0065:01#REF# 3.18.4.2.4
For operational fallback situations: at standstill, the onboard equipment shall allow the driver to change the ERTMS/ETCS level.
is realized with enabling conditions for button "Level" in ERA SRS DMI

#REQ-DESIGN-CR-0066:01#REF# 3.18.4.2.5
If the table of supported levels given by trackside is available, the selection of level by the driver shall be limited to those contained in
this table. If the table of trackside supported levels is not available, the driver can select any level within a default list configured
on-board.
UNISIG clarification:
the levels have to be displayed independently of the current availability. (remark from Sven Adomeit)
TEST APPROACH:
The following aspects were identified:
1. ToP not available
1.1. Default level list parameterized
1.1.1. Levels included in the default level list are available for use
1.1.2. Default level list includes levels not available for use
1.2. Default level list not parameterized
2. ToP available
2.1. Default level list is parameterized
2.1.1. ToP includes level not available in the default level list
2.1.2. ToP includes level not available for use
2.1.3. Default level list includes level not included in ToP
2.1.4. Level available for use not included in ToP
2.2. Default level list not parameterized
2.2.1. ToP includes level not available for use
2.2.2. Level available for use not included in ToP
Note: aspect 1.2. is covered by verification of #REQ-UNISIG-SUB026-010482#REF# 
#TEST-VAL-SUB026-3408#REF# FCT 1.1.1, 2.1.3, 2.1.4 Default level list parameterized (same as supported levels list), ToP includes level not available in the default level list
#TEST-VAL-SUB026-3410#REF# FCT 1.1.2 driver level choice: no ToP, default level list includes levels not available for use
#TEST-VAL-SUB026-3411#REF# FCT 2.1.1, 2.1.2 ToP includes level not in default list and level not supported
#TEST-VAL-SUB026-3419#REF# FCT 2.2.1 level choice according to ToP, which includes levels not available for use
#TEST-VAL-SUB026-3415#REF# FCT 2.2.2 level_choice according to Table of priority defined by P41 (no level change)
#TEST-VAL-SUB026-5272#REF# EET CFX00047837 Update of table of priority, LTO for current level, border BG passed before announced LT position
#TEST-VAL-SUB026-5274#REF# EET CFX00047837 Update of table of priority, LTO for current level, ToP from border BG different to announcement ToP
#TEST-VAL-SUB026-5268#REF# EET error expectation Table of priority, level transition executed due to passing border BG with LTO now, ToP of announcement = ToP from border BG
#TEST-VAL-SUB026-5271#REF# EET error expectation Table of priority, level transition executed due to passing border BG, ToP of announcement differs from border BG ToP
#TEST-VAL-SUB026-5516#REF# EET error expectation ToP deleted because stored Level Transition order was deleted
#TEST-VAL-SUB026-5524#REF# EET error expectation ToP overwritten by new ToP
#TEST-VAL-SUB026-5554#REF# EET error expectation no ToP available, default level list does not contain configured and connected NTC, level choice for configured and connected NTC is not available
#TEST-VAL-SUB026-5555#REF# EET error expectation ToP doesn't include the configured and connected NTC, level choice for configured and connected NTC is not available
#TEST-VAL-SUB026-7938#REF# EET error expectation default level list comprises only ETCS levels L0, L1, L2, L3; configured and connected NTC
#TEST-VAL-SUB026-7939#REF# EET error expectation Default list contains only NTCs; ETCS levels are also supported

#REQ-UNISIG-SUB026-004155#REF# to.3.18.4.2.5
It shall be parameterizable maximum 31 different NTCs in the default list additional to the ETCS level.

remark: This maximum is derived from the maximum number of level in a table of priority. L0 should be always allowed.
the definition of a maximum number is necessary
#TEST-VAL-FZGKonfDat-0463#REF# FCT maximum 31 different NTCs Check STM List when totally filled

#REQ-UNISIG-SUB026-010482#REF# to.3.18.4.2.5
If no default list of selectable level is parametrized, the driver shall be offered all levels and STMs configured onboard (i.e. the onboard is
fitted for).
It should be possible to offer all levels and STMs the obu is fitted without a separate parametrization.
#TEST-VAL-SUB026-7934#REF# FCT basic function level_choice - no Table of Priority, default level list empty
#TEST-VAL-SUB026-7935#REF# EET error expectation level_choice - no Table of Priority, default level list empty, no supported NTCs
#TEST-VAL-SUB026-7936#REF# EET error expectation level_choice - no Table of Priority, default level list empty, supported level list changed

#REQ-DESIGN-CR-0734#REF# 3.18.4.3.2
If the driver enters level 2/3, at start of mission, the ERTMS/ETCS on-board equipment shall offer the driver different means to select the RBC
contact information (including RBC identity, RBC telephone number, and the identity of the radio network to be used), for details see chapter 5,
Start of Mission procedure.
realised by: #REQ-UNISIG-SUB026-1087:01#REF#

#REQ-DESIGN-CR-0743:01#REF# to.3.18.4.3 #ANA-UNISIG-RBCData-0003#REF#
If received and accepted a new Session Management Information to established a session and the RBC Identity in this information is not unknown,
the new RBC Identity and telephone number shall be memorized.
The state of the data is valid too with the storage
TEST APPROACH:
The following aspects have been identified:
1) basic function
2) termination order does not change the stored value
3) RBC data with Q_SLEEPSESSION=Ignore Session are stored on board
4) unsuccessful session establishment
#TEST-VAL-SUB026-3444#REF# FCT 1 RBC Contact Information received from track memorized
#TEST-VAL-SUB026-7681#REF# FCT 2 Termination order does not change the stored value
#TEST-VAL-SUB026-4H43#REF# FCT 3 Acceptance of P41 (Q_SLEEPSESSION=0) and P42 in SL
#TEST-VAL-SUB026-7682#REF# FCT 4 Unsuccessful session establishment does not change the stored value

#REQ-DESIGN-CR-0744:01#REF# to.3.18.4.3 #ANA-UNISIG-RBCData-0004#REF#
During a RBC-Handover the RBC-ID and RBC-Phonenumber of the accepting RBC shall be memorized, if the train reached the handover border with max
safe front end.
If received a immediately RBC Transition Order RBC-ID and RBC-Phonenumber of the accepting RBC shall be memorized at once.
The state of the data is valid too with the storage
TEST APPROACH:
The following aspects have been identified:
1) RBC transition order
1.1) train max safe front end passed the handover border
1.2) train max safe front end did not pass the handover border
2) Immediate RBC transition order
#TEST-VAL-SUB026-3445#REF# FCT 1.1 RBC-ID and RBC-Phonenumber of the accepting RBC memorized, if train max safe front end passed the handover border
#TEST-VAL-SUB026-3446#REF# FCT 1.2 RBC-ID and RBC-Phonenumber of the accepting RBC not memorized, if train max safe front end did not pass the handover border
#TEST-VAL-SUB026-4017#REF# FCT 2 Received immediately RBC Transition Order, RBC-ID and RBC-Phonenumber of the accepting RBC memorized at once
#TEST-VAL-SUB026-4158#REF# EET error expectation SL: two mobile RBC transition order with Q_SLEEPSESSION=0, without session

#REQ-UNISIG-SUB026-010367#REF# to.3.18.3.4 #ANA-UNISIG-RBCData-0007#REF#
Is it necessary to store the negotiated system version for a RBC initiated communication session establishment.
The system version shall be stored:
- after a successfull session establishment of the supervised RBC
OR
- if new RBC Data are stored during a RBC-Handover and the session to the Accepting RBC is either established or had been established.

remark: The system version is not stored remanent.
TEST APPROACH:
The following aspects have been identified:
1) successful session establishment with the supervising RBC
2) unsuccessful session establishment with the supervising RBC
3) when new RBC data is stored on board:
3.1) session to accepting RBC does not exist, but existed previously
3.2) session to accepting RBC does not exist, and never existed
3.3) session to accepting RBC exists
4) new RBC data not stored on board, session to accepting RBC exists
#TEST-VAL-SUB026-7684#REF# FCT 1 RBC system version stored when successful session establishment with the supervising RBC
#TEST-VAL-SUB026-7685#REF# FCT 2 RBC system version not stored if no successful session establishment with the supervising RBC
#TEST-VAL-SUB026-7686#REF# FCT 3.1 Handling of RBC negotiated system version: connection with accepting RBC droped before passing handover location
#TEST-VAL-SUB026-7687#REF# FCT 3.2 Handling of RBC negotiated system version: session with accepting RBC never existed
#TEST-VAL-SUB026-7688#REF# FCT 3.3 Handling of RBC negotiated system version: connection with accepting RBC exists
#TEST-VAL-SUB026-7689#REF# FCT 4 Handling of RBC negotiated system version

#REQ-UNISIG-SUB026-010445#REF# to.3.18.3.4 #ANA-UNISIG-RBCData-0007#REF#
The system version stored for a RBC initiated communication session establishment shall be set to "unknown":
- after startup
OR
-  new RBC Data are stored and a session to this RBC is neither established nor had been established lastly
OR
- the mode is changed to UN or SN (the same modes as RBC data are deleted).
TEST APPROACH:
The following aspects have been identified:
1) startup
2) new RBC data are stored and a session with this RBC was not yet established
3) new order to establish a communication session with unchanged RBC data does not override the stored system version
4) dependency on mode change
#TEST-VAL-SUB026-7690#REF# FCT 1 System version stored for a RBC initiated: startup
#TEST-VAL-SUB026-7691#REF# FCT 2 System version stored for a RBC initiated communication session establishment
#TEST-VAL-SUB026-7692#REF# FCT 3 New order to establish a communication session with unchanged RBC data does not override the stored system version
#TEST-VAL-SUB026-3B74#REF# FCT 4) FS, LS, OS, SH, NL, SB, SL RBC initiates communication session after mode transitions
#TEST-VAL-SUB026-7683#REF# FCT 4) PS RBC system version and data not deleted when switching to PS
#TEST-VAL-SUB026-3B82#REF# FCT 4) SN Previously negociated System version is deleted in SN
#TEST-VAL-SUB026-3B75#REF# FCT 4) SR, TR, PT, RV RBC initiates communication session after mode transitions (SR, TR, PT, RV)
#TEST-VAL-SUB026-3B81#REF# FCT 4) UN Previously negociated System version is deleted in UN
#TEST-VAL-SUB026-3B76#REF# EET error expectation RBC initiates communication session after situations A3.4 (a-d, f)
#TEST-VAL-SUB026-3B77#REF# EET error expectation RBC initiates communication session after situations A3.4 (e, h, j, n)
#TEST-VAL-SUB026-3B78#REF# EET error expectation RBC initiates communication session after situations A3.4 (g, i, l, m)
#TEST-VAL-SUB026-3B79#REF# EET error expectation RBC initiates communication session after situations A3.4 (k)

#REQ-UNISIG-SUB026-004162#REF# 3.18.4.3.3
In normal operation after the start of mission, the driver shall have no further possibility to modify the RBC contact information (all further
modifications of this data are executed automatically). Exception: after a manual level change to level 2/3 and if either no Mobile Terminal is
registered to a Radio Network or no valid RBC-ID/phone number is available, the ERTMS/ETCS on-board equipment shall request the driver to select
the RBC contact information by the same means as for Start of Mission.
is realized through 5.10.3.15.2
realised by: #REQ-DESIGN-CR-0735:02#REF#

#REQ-UNISIG-SUB026-004163#REF# 3.18.4.3.4
If the driver selects “Use of EIRENE short number” to contact the RBC and the communication session is successfully established, the ERTMS/ETCS
on-board equipment shall store as valid RBC identity and telephone number, the RBC identity reported by EURORADIO and the EIRENE short number,
respectively.
realised by: #REQ-UNISIG-SUB026-004164#REF#

#REQ-UNISIG-SUB026-004164#REF# to.3.18.4.3.4 #REQ-UNISIG-SUB026-004163#REF#
If the driver selects “Use of EIRENE short number” to contact the RBC and the communication session is successfully established, the ERTMS/ETCS
on-board equipment shall store as valid RBC identity, the RBC identity reported by EURORADIO, respectively.
The telephone number shall be remain UNKNOWN

clarification:
The EIRENE short number is only managed in subsystem KBS. KBS uses the EIRENE short number, whenever an unknown RBC telephon number is provided.
#TEST-VAL-SUB026-7933#REF# FCT basic function RBC ID / short number memorized after successfull establishment of a communication session with 'EIRENE short number' selected by driver
#TEST-VAL-SUB026-7847#REF# EET error expectation RBC ID / short number not memorized if communication session is not established after 'EIRENE short number' selected by driver

#REQ-UNISIG-SUB026-3664:01#REF# 3.18.4.5.1
During the Start of Mission, the ERTMS/ETCS on-board equipment of a leading engine shall acquire the train running number from driver input,
from the RBC or from other ERTMS/ETCS external sources.
clarification:
If the train running number windows is active, a new received train running number from RBC or external sources cannot taken over in the current
dialog.
TEST APPROACH:
The following aspects were identified:
1) Driver input
1.1) RBC or external source do not interfere with driver input
1.2) TRN window active, receive TRN from RBC
1.2.1) driver validates his input
1.2.2) driver cancels his input
1.3) TRN window active, receive TRN from other ERTMS/ETCS external source 
1.3.1) driver validates his input
1.3.2) driver cancels his input
2) RBC
3) other ERTMS/ETCS external source 
#TEST-VAL-SUB026-5404#REF# FCT 1.1 SOM - L2/SR
#TEST-VAL-SUB026-7993#REF# FCT 1.2.1 RBC sends TRN while driver input, driver validates his input
#TEST-VAL-SUB026-7995#REF# FCT 1.2.2 RBC sends TRN while driver input, driver cancels his input
#TEST-VAL-SUB026-7994#REF# FCT 1.3.1 ERTMS/ETCS external source sends TRN while driver input, driver validates his input
#TEST-VAL-SUB026-7996#REF# FCT 1.3.2 ERTMS/ETCS external source sends TRN while driver input, driver cancels his input
#TEST-VAL-SUB026-3B54#REF# FCT 2 Train Running Number from RBC during SOM
#TEST-VAL-SUB026-3B53#REF# FCT 3 Train Running Number from other ERTMS/ETCS external source during SOM

#REQ-UNISIG-SUB026-010554#REF# to.3.18.4.5.1
The train running number is received from RBC or an external sources shall be taken over independent of the current state of train running
number.
If the current state is unknown or invalid, the state shall be set valid after the taking over.
UNISIG clarification:
a definition is necessary, when the TRN is received before the driver inputs the TRN.
#TEST-VAL-SUB026-3B54#REF# FCT RBC Train Running Number from RBC during SOM
#TEST-VAL-SUB026-3B53#REF# FCT other ERTMS/ETCS external source Train Running Number from other ERTMS/ETCS external source during SOM

#REQ-UNISIG-SUB026-0123:01#REF# 3.18.4.5.2
It shall be possible to enter train running number also in a non-leading engine.
is defined also in 4.7.2
realised by: #REQ-UNISIG-SUB026-3286#REF#

#REQ-UNISIG-SUB026-2308#REF# 3.18.4.5.3
It shall be possible to change the train running number while running, from driver input, from the RBC or from other ERTMS/ETCS external
sources.
clarification:
If the train running number windows is active, a new received train running number from RBC or external sources cannot taken over in the current
dialog.
TEST APPROACH:
The following aspects were identified:
1) Driver input
1.1) RBC or external source do not interfere with driver input
1.2) TRN window active, receive TRN from RBC
1.2.1) driver validates his input
1.2.2) driver cancels his input
1.3) TRN window active, receive TRN from other ERTMS/ETCS external source 
1.3.1) driver validates his input
1.3.2) driver cancels his input
2) RBC
3) other ERTMS/ETCS external source 
#TEST-VAL-SUB026-3766#REF# FCT 1.1, 2, 3 Train Running Number from different sources
#TEST-VAL-SUB026-7993#REF# FCT 1.2.1 RBC sends TRN while driver input, driver validates his input
#TEST-VAL-SUB026-7995#REF# FCT 1.2.2 RBC sends TRN while driver input, driver cancels his input
#TEST-VAL-SUB026-7994#REF# FCT 1.3.1 ERTMS/ETCS external source sends TRN while driver input, driver validates his input
#TEST-VAL-SUB026-7996#REF# FCT 1.3.2 ERTMS/ETCS external source sends TRN while driver input, driver cancels his input

#REQ-UNISIG-SUB026-004184#REF# 3.18.4.5.4
Following any entry/modification of the train running number when a communication session is already established or following the successful
establishment of a communication session when valid train running number is already available, the ERTMS/ETCS on-board equipment shall send the
train running number to the RBC.
TEST APPROACH:
The following aspects have been identified:
1) Comm session available - Driver changes Train Running Number
2) Comm session available - Leading RBC sends new Train Running Number
3) Comm session available - Train Running Number changed via other ERTMS/ETCS external source
4) Comm session established - no Train Running Number on board
5) Comm session established - valid Train Running number on board
6) Comm session established - not valid Train Running number on board
#TEST-VAL-SUB026-3B59#REF# FCT 1, 2, 3 Change Train Running Number from different sources when comm session is available
#TEST-VAL-SUB026-3B56#REF# FCT 4 Deleted Train Running Number not sent to RBC on communication session establishment
#TEST-VAL-SUB026-3B55#REF# FCT 5 Change of Train Running Number via other ERTMS/ETCS external source sent to RBC on communication session establishment
#TEST-VAL-SUB026-3B58#REF# FCT 6 Invalidated Train Running Number not sent to RBC on communication session establishment

#REQ-UNISIG-SUB026-004186#REF# 3.18.4.5.4.1 #REQ-UNISIG-SUB026-007310#REF#
Exception: if the train running number has been received from the RBC, it shall not be sent back to the RBC by the ERTMS/ETCS on-board
equipment.
UNISIG clarification:
If a conncection to a second RBC is existed (for instance RBC-HO), the train running number is send to this second RBC.
#TEST-VAL-SUB026-3B59#REF# FCT basic function Change Train Running Number from different sources when comm session is available

#REQ-DESIGN-CR-0393:01#REF# 3.18.4.6.2.1
It shall be possible to update the adhesion factor from trackside and - if permitted by a National value - by the driver. If, following a change
of National Values, the update of the adhesion factor is no more permitted to the driver, the adhesion factor previously modified by the driver
to slippery rail shall immediately be reset to non slippery rail. Any trackside adhesion profile is not affected.
The change of adhesion factor from trackside or by driver does'nt have an impact of the other value
TEST APPROACH:
The following aspects have been identified:
1) driver
2) trackside
#TEST-VAL-SUB026-4594#REF# FCT 1 Driver choice change of ahesion factor unavailable if condition 'Q_NVDRIVER_ADHES=1' not fulfilled
#TEST-VAL-SUB026-3219#REF# FCT 2 Adhaesionsprofil
#TEST-VAL-SUB026-3893#REF# EET error expectation Effect on modified adhesionFactor if right to change revoked by NV pkt

#REQ-UNISIG-SUB026-2023:01#REF# 3.18.4.6.2.3 #REQ-UNISIG-SUB026-3321:01#REF#
The driver shall be informed whether the value of the adhesion factor is “slippery rail”.
#TEST-VAL-SUB026-4672#REF# FCT basic function adhesion factor changed by track and driver

#REQ-UNISIG-SUB026-3584:01#REF# to.3.18.4.6.2.3 #ANA-UNISIG-AdhesionFactor-0003:01#REF#
The indication "slippery rail" shall be displayed to the driver immediately whenever a section with reduced adhesion is in front of
the estimated train rear end.
Anzeige sofort und nicht erst mit Erreichen des Beginns des Bereiches.
TEST APPROACH:
The following aspects have been identified:
1) 'slippery rail' from driver
2) 'slippery rail' from track
3) revocation of 'slippery rail'
#TEST-VAL-SUB026-4671#REF# FCT 1 adhesion factor changed by driver and track
#TEST-VAL-SUB026-4672#REF# FCT 2 adhesion factor changed by track and driver
#TEST-VAL-SUB026-4674#REF# FCT 3 adhesion factor non slippery given from track side outside actual slippery area given from track side
#TEST-VAL-SUB026-4673#REF# EET error expectation Shortening of track side ordered slippery area by P71 none slippery

#REQ-UNISIG-SUB026-3690:01#REF# 3.18.4.6.3
The selection of the adhesion value from trackside or by driver entry shall be limited to the options slippery rail/ non slippery rail.
is realized through the values of M_ADHSION for trackside and the driver input via button "Non slippery rail"/"Slippery
rail"
--- FINALISED ---
The part of trackside is realized through definition of packet 71 and variable M_ADHESION.
For the driver entry ERA SRS DMI specification defines the possible input values.
#REQ-UNISIG-SUB026-1184#REF#
#ANALYSE-VALUNISIG-4789#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-0135#REF# 3.18.4.6.4
The default value for the adhesion factor shall be the highest value (i.e. not slippery rail).
#TEST-VAL-SUB026-3771#REF# FCT basic function slippery rail / non slippery rail equals

#REQ-UNISIG-SUB026-0137#REF# 3.18.5.1
Each ERTMS/ETCS on-board equipment shall be able to provide the date (day, month, year) and time (hour, minute, second) in Universal Time
Co-ordinated (UTC) and Local Time.
#TEST-VAL-SUB026-3220#REF# FCT basic function Availability of Time and Date

#REQ-UNISIG-SUB026-0138#REF# 3.18.5.2
The local time shall be presented to the driver, while the UTC shall be used for the juridical data.
#TEST-VAL-SUB026-3220#REF# FCT basic function Availability of Time and Date

#REQ-UNISIG-SUB026-004218#REF# 3.18.6.1
Outside the context of data entry, the ERTMS/ETCS on-board equipment shall offer the possibility to the driver to view the driver ID, the train
running number, the RBC contact information, the Virtual Balise Cover(s) and the Train Data either modifiable by the driver or modifiable by
other ERTMS/ETCS external sources.

--- FINALISED ---
Which data the driver can view and the conditions of view are defined in ERA SRS DMI.
#ANALYSE-VALUNISIG-5265#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-004220#REF# 3.18.6.2
Only valid data shall be presented to the driver.
is realized with ERA SRS DMI data view windows

Chapter 3.20

#REQ-UNISIG-SUB026-004230#REF# 3.20.1.2
The ERTMS/ETCS on-board equipment shall transmit to the on-board recording device the information that may be used for legal purpose after
hazardous situations.

--- FINALISED ---
The communication and the data to be transmitted to the on-board recording device are defined in /FFFIS_JRU/.
#ANALYSE-VALUNISIG-7668#REF# FCT No additional functional requirement refer column FINALISED.

Chapter A.3

#REQ-UNISIG-SUB026-004254:01#REF# A3.1



realised by: #REQ-UNISIG-SUB026-007957#REF#
realised by: #REQ-UNISIG-SUB026-007958#REF#
realised by: #REQ-DESIGN-CR-0093:01#REF#
realised by: #REQ-UNISIG-SUB026-007959#REF#
realised by: #REQ-UNISIG-SUB026-007960#REF#
realised by: #REQ-UNISIG-SUB026-007961#REF#
realised by: #REQ-UNISIG-SUB026-007962#REF#
realised by: #REQ-UNISIG-SUB026-007963#REF#
realised by: #REQ-UNISIG-SUB026-007964#REF#
realised by: #REQ-UNISIG-SUB026-007965#REF#
realised by: #REQ-UNISIG-SUB026-007966#REF#
realised by: #REQ-UNISIG-SUB026-007967#REF#
realised by: #REQ-UNISIG-SUB026-007968#REF#
realised by: #REQ-UNISIG-SUB026-007969#REF#
realised by: #REQ-UNISIG-SUB026-007970#REF#
realised by: #REQ-UNISIG-SUB026-007971#REF#
realised by: #REQ-UNISIG-SUB026-007972#REF#
realised by: #REQ-UNISIG-SUB026-007973#REF#
realised by: #REQ-UNISIG-SUB026-007974#REF#
realised by: #REQ-UNISIG-SUB026-007975#REF#
realised by: #REQ-UNISIG-SUB026-010109#REF#
realised by: #REQ-UNISIG-SUB026-007977#REF#
realised by: #REQ-UNISIG-SUB026-007978#REF#
realised by: #REQ-DESIGN-CR-0507#REF#
realised by: #REQ-UNISIG-SUB026-3067#REF#
realised by: #REQ-UNISIG-SUB026-010110#REF#
realised by: #REQ-UNISIG-SUB026-3407#REF#
realised by: #REQ-UNISIG-SUB026-3007#REF#
realised by: #REQ-UNISIG-SUB026-010111#REF#
realised by: #REQ-UNISIG-SUB026-010112#REF#

#REQ-UNISIG-SUB026-007957#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
The number of times to try to establish a safe radio connection
value: 3 times
realised by: #REQ-UNISIG-SUB026-0420:01#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007958#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Repetition of radio messages (i.e. excluding the first sending)
value: 3 times
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-DESIGN-CR-0093:01#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Waiting time before radio message repetition
value: 15 s
realised by: #REQ-UNISIG-SUB026-010278#REF#
realised by: #REQ-UNISIG-SUB026-0681:03#REF#
realised by: #REQ-UNISIG-SUB026-010141#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#
realised by: #REQ-UNISIG-SUB026-0262:02#REF#
realised by: #REQ-UNISIG-SUB026-3691:02#REF#
realised by: #REQ-UNISIG-SUB026-0844:01#REF#
realised by: #REQ-UNISIG-SUB026-0980:01#REF#

#REQ-UNISIG-SUB026-007959#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, minimum value
value: 7,5 km/h
name: dV_ebi_min
realised by: #REQ-UNISIG-SUB026-007273#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007960#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, maximum value
value: 15 km/h
name: dV_ebi_max
realised by: #REQ-UNISIG-SUB026-007273#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007961#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Value of MRSP where dV_ebi starts to increase to dV_ebi_max
value: 110 km/h
name: V_ebi_min
realised by: #REQ-UNISIG-SUB026-007273#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007962#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Value of MRSP where dV_ebi stops to increase to dV_ebi_max
value: 210 km/h
name: V_ebi_max
realised by: #REQ-UNISIG-SUB026-007273#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007963#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Speed difference between Permitted speed and Service Brake Intervention supervision limits, minimum value
value: 5,5 km/h
name: dV_sbi_min
realised by: #REQ-UNISIG-SUB026-007278#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007964#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Speed difference between Permitted speed and Service Brake Intervention supervision limits, maximum value
value: 10 km/h
name: dV_sbi_max
realised by: #REQ-UNISIG-SUB026-007278#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007965#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Value of MRSP where dV_sbi starts to increase to dV_sbi_max
value: 110 km/h
name: V_sbi_min
realised by: #REQ-UNISIG-SUB026-007278#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007966#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Value of MRSP where dV_sbi stops to increase to dV_sbi_max
value: 210 km/h
name: V_sbi_max
realised by: #REQ-UNISIG-SUB026-007278#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007967#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Speed difference between Permitted speed and Warning supervision limits, minimum value
value: 4 km/h
name: dV_warning_min
realised by: #REQ-UNISIG-SUB026-007279#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007968#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Speed difference between Permitted speed and Warning supervision limits, maximum value
value: 5 km/h
name: dV_warning_max
realised by: #REQ-UNISIG-SUB026-007279#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007969#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Value of MRSP where dV_warning starts to increase to dV_warning_max
value: 110 km/h
name: V_warning_min
realised by: #REQ-UNISIG-SUB026-007279#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007970#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Value of MRSP where dV_warning stops to increase to dV_warning_max
value: 140 km/h
name: V_warning_max
realised by: #REQ-UNISIG-SUB026-007279#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007971#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Time between Warning supervision limit and FLOI
value: 2 s
name: T_warning
realised by: #REQ-UNISIG-SUB026-007337#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007972#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Driver reaction time between Permitted speed supervision limit and FLOI
value: 4 s
name: T_driver
realised by: #REQ-UNISIG-SUB026-007341#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007973#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Time between the pre-indication location and the indication supervision limit valid for MRSP speed.
value: 7 s
name: T_preindication
realised by: #REQ-UNISIG-SUB026-007423#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007974#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Maximum possible rotating mass as a percentage of the total weight of the train
value: 15%
name: M_rotating_max
realised by: #REQ-UNISIG-SUB026-002706#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007975#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Minimum possible rotating mass as a percentage of the total weight of the train
value: 2%
name: M_rotating_min
realised by: #REQ-UNISIG-SUB026-002706#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-010109#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Compensation of the speed measurement inaccuracy  used for the calculation of speed restriction to ensure given permitted braking distance
value: 5 km/h
realised by: #REQ-UNISIG-SUB026-002059#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007977#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
MA request repetition cycle, default value
value: 60 s
name: TCYCRQSTD
realised by: #REQ-UNISIG-SUB026-0474#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-007978#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Mode transitions: Driver acknowledgement time
value: 5 s
name: TACK
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#
realised by: #REQ-UNISIG-SUB026-0785:01#REF#
realised by: #REQ-UNISIG-SUB026-0791:01#REF#
realised by: #REQ-UNISIG-SUB026-0276:01#REF#
realised by: #REQ-UNISIG-SUB026-3516#REF#
realised by: #REQ-UNISIG-SUB026-3526#REF#

#REQ-DESIGN-CR-0507#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Distance of metal immunity in Levels 0/NTC
value: 300 metres
name: D_METAL
realised by: #REQ-DESIGN-CR-0506#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-3067#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Maximum time to maintain a communication session in case of failed re-connection attempts
value: 5  minutes
realised by: #REQ-UNISIG-SUB026-3061:01#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-010110#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Driver reaction time before sounding the horn
value: 4 s
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#
realised by: #REQ-UNISIG-SUB026-006922#REF#

#REQ-UNISIG-SUB026-3407#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Time between minimum safe rear end of the train leaving a track condition area and on-board deleting the applicable indication
value: 5 s
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#
realised by: #REQ-UNISIG-SUB026-3425:01#REF#
realised by: #REQ-UNISIG-SUB026-3435:01#REF#
realised by: #REQ-UNISIG-SUB026-3451:01#REF#
realised by: #REQ-UNISIG-SUB026-010318#REF#

#REQ-UNISIG-SUB026-3007#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Distance to keep on-board information in rear of the min safe rear end of the train
value: 300 metres
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#
realised by: #REQ-UNISIG-SUB026-3260:02#REF#
realised by: #REQ-UNISIG-SUB026-3264#REF#
realised by: #REQ-UNISIG-SUB026-010486#REF#
realised by: #REQ-UNISIG-SUB026-3268#REF#
realised by: #REQ-UNISIG-SUB026-010549#REF#
realised by: #REQ-UNISIG-SUB026-3272:01#REF#
realised by: #REQ-UNISIG-SUB026-3276:01#REF#

#REQ-UNISIG-SUB026-010111#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
Additional delay time to disconnection on supervision of safe radio connection
value: 60 s
realised by: #REQ-UNISIG-SUB026-0675:01#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-UNISIG-SUB026-010112#REF# A3.1 #REQ-UNISIG-SUB026-004254:01#REF#
List of Fixed Value data:
“Connection status” timer for safe radio connection indication
value: 45 s
realised by: #REQ-UNISIG-SUB026-001011#REF#
realised by: #REQ-SWAnf-PARAM-008111:02#REF#
realised by: #REQ-SWAnf-FixedValues-008112:01#REF#

#REQ-SWAnf-PARAM-008111:02#REF# A.3 #REQ-PROJ-0110:01#REF#
#REQ-UNISIG-SUB026-007957#REF#
#REQ-UNISIG-SUB026-007958#REF#
#REQ-UNISIG-SUB026-007959#REF#
#REQ-UNISIG-SUB026-007960#REF#
#REQ-UNISIG-SUB026-007961#REF#
#REQ-UNISIG-SUB026-007962#REF#
#REQ-UNISIG-SUB026-007963#REF#
#REQ-UNISIG-SUB026-007964#REF#
#REQ-UNISIG-SUB026-007965#REF#
#REQ-UNISIG-SUB026-007966#REF#
#REQ-UNISIG-SUB026-007967#REF#
#REQ-UNISIG-SUB026-007968#REF#
#REQ-UNISIG-SUB026-007969#REF#
#REQ-UNISIG-SUB026-007970#REF#
#REQ-UNISIG-SUB026-007971#REF#
#REQ-UNISIG-SUB026-007972#REF#
#REQ-UNISIG-SUB026-007973#REF#
#REQ-UNISIG-SUB026-007974#REF#
#REQ-UNISIG-SUB026-007975#REF#
#REQ-UNISIG-SUB026-007977#REF#
#REQ-UNISIG-SUB026-007978#REF#
#REQ-DESIGN-CR-0507#REF#
#REQ-UNISIG-SUB026-3067#REF#
#REQ-UNISIG-SUB026-3007#REF#
#REQ-UNISIG-SUB026-3407#REF#
#REQ-DESIGN-CR-0093:01#REF#
#REQ-UNISIG-SUB026-010109#REF#
#REQ-UNISIG-SUB026-010110#REF#
#REQ-UNISIG-SUB026-010111#REF#
#REQ-UNISIG-SUB026-010112#REF#
The following fixed values shall be parameterizable:

-	The number of times to try to establish a safe radio connection
value: 3 times
-	Repetition of radio messages
value: 3 times
-	Cycle time for the repetition of radio messages in  case no reply is received
value: 15 s
-	Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, minimum value
value: 7.5 km/h
name: dV_ebi_min
-	Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, maximum value
value: 15 km/h
name: dV_ebi_max
-	Value of MRSP where dV_ebi starts to increase to dV_ebi_max
value: 110 km/h
name: V_ebi_min
-	Value of MRSP where dV_ebi stops to increase to dV_ebi_max
value: 210 km/h
name: V_ebi_max
-	Speed difference between Permitted speed and Service Brake Intervention supervision limits, minimum value
value: 5.5 km/h
name: dV_sbi_min
-	Speed difference between Permitted speed and Service Brake Intervention supervision limits, maximum value
value: 10 km/h
name: dV_sbi_max
-	Value of MRSP where dV_sbi starts to increase to dV_sbi_max
value: 110 km/h
name: V_sbi_min
-	Value of MRSP where dV_sbi stops to increase to dV_sbi_max
value: 210 km/h
name: V_sbi_min
-	Speed difference between Permitted speed and Warning supervision limits, minimum value
value: 4 km/h
name: dV_warning_min
-	Speed difference between Permitted speed and Warning supervision limits, maximum value
value: 5 km/h
name: dV_warning_max
-	Value of MRSP where dV_warning starts to increase to dV_warning_max
value: 110 km/h
name: V_warning_min
-	Value of MRSP where dV_warning stops to increase to dV_warning_max
value: 140 km/h
name: V_warning_max
-	Time between Warning supervision limit and FLOI
value: 2 s
name: T_warning
-	Driver reaction time between Permitted speed supervision limit and FLOI
value: 4 s
name: T_driver
-	Time between the pre-indication location and the indication supervision limit valid for MRSP speed
value: 7 s
name: T_preindication
-	Maximum possible rotating mass as a percentage of the total weight of the train
value: 15 %
name: M_roating_max
-	Minimum possible rotating mass as a percentage of the total weight of the train
value: 2 %
name: M_roating_min
-	Compensation of the speed measurement inaccuracy  used for the calculation of speed restriction to ensure given permitted braking
distance
value: 5 km/h
-	MA request repetition cycle, default value
value: 60 s
name: TCYCRQSTD
-	Mode transitions: Driver acknowledgement time
value: 5 s
name: TACK
-	Maximum time to maintain a communication session in case of failed re-connection attempts
value: 5 minutes
-	Distance of metal immunity in Levels 0/NTC
values: 300 metres
name: D_Metal
-	Driver reaction time before sounding the horn
value: 4 s
-	Time between minimum safe rear end of the train leaving a track condition area and on-board deleting the applicable indication
value: 5 s
-	Distance to keep on-board information in rear of the min safe rear end of the train
values: 300 metres
-	Additional delay time to disconnection on supervision of safe radio connection
value: 60 s
-	“Connection status” timer for safe radio connection indication
value: 45 s
Rel. 8.0 - Sub26 3.2 (Version :01)
changed
- "Cycle time for the repetition of radio messages in  case no reply is received" - 15s instead of 20s

new:
- Driver reaction time before sounding the horn
- Additional delay time to disconnection on supervision of safe radio connection
- “Connection status” timer for safe radio connection indication
- Display time for the “Connection Lost/Set-Up failed” indication status 

Sub26 3.3 (Version :02):
deleted
- Display time for the “Connection Lost/Set-Up failed” indication status 
- V_delta0rsob
TEST APPROACH:
The verification of this requirement focuses on the usage of the values as defined by UNISIG in the default configuration. 
The usage of modified values is covered by the verification of #REQ-SWAnf-FixedValues-008112:01#REF#.
The following aspects have been identified:
1) The number of times to try to establish a safe radio connection
2) Repetition of radio messages
3) Cycle time for the repetition of radio messages in case no reply is received
4) Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, minimum value
5) Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, maximum value
6) Value of MRSP where dV_ebi starts to increase to dV_ebi_max
7) Value of MRSP where dV_ebi stops to increase to dV_ebi_max
8) Speed difference between Permitted speed and Service Brake Intervention supervision limits, minimum value
9) Speed difference between Permitted speed and Service Brake Intervention supervision limits, maximum value
10) Value of MRSP where dV_sbi starts to increase to dV_sbi_max
11) Value of MRSP where dV_sbi stops to increase to dV_sbi_max
12) Speed difference between Permitted speed and Warning supervision limits, minimum value
13) Speed difference between Permitted speed and Warning supervision limits, maximum value
14) Value of MRSP where dV_warning starts to increase to dV_warning_max
15) Value of MRSP where dV_warning stops to increase to dV_warning_max
16) Time between Warning supervision limit and FLOI
17) Driver reaction time between Permitted speed supervision limit and FLOI
18) Time between the pre-indication location and the indication supervision limit valid for MRSP speed
19) Maximum possible rotating mass as a percentage of the total weight of the train
20) Minimum possible rotating mass as a percentage of the total weight of the train
21) Compensation of the speed measurement inaccuracy used for the calculation of speed restriction to ensure given permitted braking distance
22) MA request repetition cycle, default value
23) Mode transitions: Driver acknowledgement time
24) Maximum time to maintain a communication session in case of failed re-connection attempts
25) Distance of metal immunity in Levels 0/NTC
26) Driver reaction time before sounding the horn
27) Time between minimum safe rear end of the train leaving a track condition area and on-board deleting the applicable indication
28) Distance to keep on-board information in rear of the min safe rear end of the train
29) Additional delay time to disconnection on supervision of safe radio connection
30) 'Connection status' timer for safe radio connection indication
#TEST-VAL-SUB026-3262#REF# FCT 1 Connection to RBC can not be established during SoM
#TEST-VAL-SUB026-3618#REF# FCT 2, 3 no response from RBC for message 155 (Initiation of communication session)
#TEST-VAL-SUB026-4F78#REF# BVA 4 - 21 OBU fixed data used in BC: default UNISIG values
#TEST-VAL-SUB026-3078#REF# FCT 22 MA request repetition cycle, default fixed value T_CYCRQSTD
#TEST-VAL-SUB026-5038#REF# FCT 23 OS mode not acknowleged in time
#TEST-VAL-SUB026-3B15#REF# FCT 24 Establishing a communication session after previous session was considered terminated due to loss of safe radio connection
#TEST-VAL-SUB026-3975#REF# FCT 25 Fixed distance of metal immunity in L0
#TEST-VAL-SUB026-7724#REF# FCT 26 Indication of TC 'Sound horn', default configuration
#TEST-VAL-SUB026-5560#REF# FCT 27 Indication of TC 'Air tightness', default configuration
#TEST-VAL-SUB026-3800#REF# FCT 28 Storage of ASP Q_FRONT=0 and track side adhesion factor for backward movement
#TEST-VAL-SUB026-5731#REF# FCT 29 T_NVCONTACT supervision causes delayed release of safe connection
#TEST-VAL-SUB026-3B36#REF# FCT 30 Connection timer started when connection set-up begins due to manual level change to L2

#REQ-SWAnf-FixedValues-008112:01#REF# A.3 #REQ-UNISIG-SUB026-007957#REF#
#REQ-UNISIG-SUB026-007958#REF#
#REQ-UNISIG-SUB026-007959#REF#
#REQ-UNISIG-SUB026-007960#REF#
#REQ-UNISIG-SUB026-007961#REF#
#REQ-UNISIG-SUB026-007962#REF#
#REQ-UNISIG-SUB026-007963#REF#
#REQ-UNISIG-SUB026-007964#REF#
#REQ-UNISIG-SUB026-007965#REF#
#REQ-UNISIG-SUB026-007966#REF#
#REQ-UNISIG-SUB026-007967#REF#
#REQ-UNISIG-SUB026-007968#REF#
#REQ-UNISIG-SUB026-007969#REF#
#REQ-UNISIG-SUB026-007970#REF#
#REQ-UNISIG-SUB026-007971#REF#
#REQ-UNISIG-SUB026-007972#REF#
#REQ-UNISIG-SUB026-007973#REF#
#REQ-UNISIG-SUB026-007974#REF#
#REQ-UNISIG-SUB026-007975#REF#
#REQ-UNISIG-SUB026-007977#REF#
#REQ-UNISIG-SUB026-007978#REF#
#REQ-DESIGN-CR-0507#REF#
#REQ-UNISIG-SUB026-3067#REF#
#REQ-UNISIG-SUB026-3007#REF#
#REQ-UNISIG-SUB026-3407#REF#
#REQ-DESIGN-CR-0093:01#REF#
#REQ-UNISIG-SUB026-010109#REF#
#REQ-UNISIG-SUB026-010110#REF#
#REQ-UNISIG-SUB026-010111#REF#
#REQ-UNISIG-SUB026-010112#REF#
The ASW shall use the parameterized values for the fixed data.
TEST APPROACH:
The verification of this requirement focuses on the usage of modified values. 
The usage of the UNISIG defined values in the default configuration is covered by the verification of #REQ-SWAnf-PARAM-008111:02#REF#.
The following aspects have been identified:
1) The number of times to try to establish a safe radio connection
2) Repetition of radio messages
3) Cycle time for the repetition of radio messages in case no reply is received
4) Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, minimum value
5) Speed difference between Permitted speed and Emergency Brake Intervention supervision limits, maximum value
6) Value of MRSP where dV_ebi starts to increase to dV_ebi_max
7) Value of MRSP where dV_ebi stops to increase to dV_ebi_max
8) Speed difference between Permitted speed and Service Brake Intervention supervision limits, minimum value
9) Speed difference between Permitted speed and Service Brake Intervention supervision limits, maximum value
10) Value of MRSP where dV_sbi starts to increase to dV_sbi_max
11) Value of MRSP where dV_sbi stops to increase to dV_sbi_max
12) Speed difference between Permitted speed and Warning supervision limits, minimum value
13) Speed difference between Permitted speed and Warning supervision limits, maximum value
14) Value of MRSP where dV_warning starts to increase to dV_warning_max
15) Value of MRSP where dV_warning stops to increase to dV_warning_max
16) Time between Warning supervision limit and FLOI
17) Driver reaction time between Permitted speed supervision limit and FLOI
18) Time between the pre-indication location and the indication supervision limit valid for MRSP speed
19) Maximum possible rotating mass as a percentage of the total weight of the train
20) Minimum possible rotating mass as a percentage of the total weight of the train
21) Compensation of the speed measurement inaccuracy used for the calculation of speed restriction to ensure given permitted braking distance
22) MA request repetition cycle, default value
23) Mode transitions: Driver acknowledgement time
24) Maximum time to maintain a communication session in case of failed re-connection attempts
25) Distance of metal immunity in Levels 0/NTC
26) Driver reaction time before sounding the horn
27) Time between minimum safe rear end of the train leaving a track condition area and on-board deleting the applicable indication
28) Distance to keep on-board information in rear of the min safe rear end of the train
29) Additional delay time to disconnection on supervision of safe radio connection
30) 'Connection status' timer for safe radio connection indication
#TEST-VAL-FZGKonfDat-0006#REF# FCT 1 Data base entry mfixn_TryEstablishSafeConn taken into account
#TEST-VAL-SUB026-3617#REF# FCT 2, 3 level transition L2->L1 RBC does not order termination of connection
#TEST-VAL-SUB026-4F79#REF# FCT 4 - 15 Fixed values for CSM
#TEST-VAL-SUB026-4F69#REF# FCT 16 Dependecy on T_warning
#TEST-VAL-SUB026-4F70#REF# FCT 17 Dependecy on T_driver
#TEST-VAL-SUB026-4F71#REF# FCT 18 Dependecy on T_preindication
#TEST-VAL-SUB026-4F80#REF# FCT 19-21 Dependency of EBI on M_rotating_max/_min
#TEST-VAL-SUB026-5682#REF# FCT 22 MA request repetition cycle, non UNISIG value
#TEST-VAL-SUB026-5683#REF# FCT 23 Parameterized value time to acknowledge a mode transition taken into account
#TEST-VAL-SUB026-5681#REF# FCT 24 Parameterized value max time to maintain communication session
#TEST-VAL-FZGKonfDat-0205#REF# FCT 25 Fixed distance of metal immunity in L0 is used
#TEST-VAL-SUB026-7725#REF# FCT 26 Indication of TC 'Sound horn', non-UNISIG values
#TEST-VAL-SUB026-3B83#REF# FCT 27 Indication of TC 'Powerless section, lower pantograph', non-UNISIG values
#TEST-VAL-SUB026-5684#REF# FCT 28 Data base entry distance to keep on-board information taken into account
#TEST-VAL-SUB026-5737#REF# FCT 29 Parameterized values for the fixed data - disconnect delay time taken into account
#TEST-VAL-SUB026-3B35#REF# FCT 30 Safe Radio Connection Status Timer non-UNISIG value

#REQ-UNISIG-SUB026-010346#REF# A.3 #REQ-UNISIG-SUB040-3041:01#REF#
#REQ-UNISIG-SUB040-3043:01#REF#
#ANA-UNISIG-TrackCondition-0020#REF#
The following data shall be parameterizable also as fixed data, additional to the UNISIG fixed data defined in /SUBSET 26/ A.3.1:
-	necessaray time between announcement and start location of  track condition “Powerless Section with pantograph to be lowered”
value: 17 s
-	necessaray time between announcement and start location of  track condition “Change of Traction System”
value: 17 s
-	necessaray time between announcement and start location of  track condition “Powerless section - switch off the main power switch”
value: 11 s
-	necessaray time between announcement and start location of  track condition “air tightness”
value: 10 s
-	necessaray time between announcement and start location of  track condition “switch off regenerative/eddy current
(service/emergency)/magnetic shoe brake”
value: 10 s
TEST APPROACH:
The following aspects have been identified:
1) necessary time between announcement and start location of track condition ' Powerless Section with pantograph to be lowered' 
2) necessary time between announcement and start location of track condition ' Change of Traction System' 
3) necessary time between announcement and start location of track condition ' Powerless section - switch off the main power switch' 
4) necessary time between announcement and start location of track condition ' air tightness' 
5) necessary time between announcement and start location of track condition ' switch off regenerative brake' 
6) necessary time between announcement and start location of track condition ' switch off magnetic shoe brake' 
7) necessary time between announcement and start location of track condition ' switch off eddy current service brake"
8) necessary time between announcement and start location of track condition ' switch off eddy current emergency brake"
Each with the following sub-aspects:
1) UNISIG value
2) non-UNISIG value
#TEST-VAL-SUB026-5569#REF# FCT 1.1 Indication of TC 'Powerless section, lower pantograph' - default UNISIG values
#TEST-VAL-SUB026-3B83#REF# FCT 1.2 Indication of TC 'Powerless section, lower pantograph', non-UNISIG values
#TEST-VAL-SUB026-5566#REF# FCT 2.1 Indication of TC change of traction system, default configuration
#TEST-VAL-SUB026-3B87#REF# FCT 2.2 Indication of TC change of traction system, non-UNISIG values
#TEST-VAL-SUB026-5570#REF# FCT 3.1 Indication of TC 'Powerless section, switch off main power switch', default configuration
#TEST-VAL-SUB026-3B84#REF# FCT 3.2 Indication of TC 'Powerless section, switch off main power switch', non-UNISIG values
#TEST-VAL-SUB026-5560#REF# FCT 4.1 Indication of TC 'Air tightness', default configuration
#TEST-VAL-SUB026-3B85#REF# FCT 4.2 Indication of TC 'Air tightness', non-UNISIG values
#TEST-VAL-SUB026-5563#REF# FCT 5.1 Indication of TC inhibition of regenerative brake, default configuration
#TEST-VAL-SUB026-3B86#REF# FCT 5.2 Indication of TC inhibition of regenerative brake, non-UNISIG values
#TEST-VAL-SUB026-5565#REF# FCT 6.1 Indication of TC magnetic shoe brake, default configuration
#TEST-VAL-SUB026-3B91#REF# FCT 6.2 Indication of TC inhibition of magnetic shoe brake, non-UNISIG values
#TEST-VAL-SUB026-5564#REF# FCT 7.1 Indication of TC eddy current brake - SB, default configuration
#TEST-VAL-SUB026-3B90#REF# FCT 7.2 Indication of TC inhibition of eddy current brake SB, non-UNISIG values
#TEST-VAL-SUB026-3B89#REF# FCT 8.1 Indication of TC eddy current brake - EB, default configuration
#TEST-VAL-SUB026-3B92#REF# FCT 8.2 Indication of TC inhibition of eddy current brake EB, non-UNISIG values

#REQ-UNISIG-SUB026-004258#REF# A.3




*The default value of the correction factor Kr_int shall be valid for any train length, and likewise the default value of the correction factor
Kv_int shall be valid for any brake position, speed and maximum emergency brake deceleration. This means that the Kr_int model does not contain
any train length step, and that the Kv_int model is valid for all train types and does neither contain any speed step nor any pivot deceleration
limit.
realised by: #REQ-UNISIG-SUB026-007979#REF#
realised by: #REQ-UNISIG-SUB026-007980#REF#
realised by: #REQ-UNISIG-SUB026-007981#REF#
realised by: #REQ-UNISIG-SUB026-007982#REF#
realised by: #REQ-UNISIG-SUB026-3339#REF#
realised by: #REQ-UNISIG-SUB026-007983#REF#
realised by: #REQ-UNISIG-SUB026-007984#REF#
realised by: #REQ-UNISIG-SUB026-007985#REF#
realised by: #REQ-UNISIG-SUB026-007987#REF#
realised by: #REQ-UNISIG-SUB026-007988#REF#
realised by: #REQ-UNISIG-SUB026-007989#REF#
realised by: #REQ-UNISIG-SUB026-007990#REF#
realised by: #REQ-UNISIG-SUB026-007991#REF#
realised by: #REQ-UNISIG-SUB026-007992#REF#
realised by: #REQ-UNISIG-SUB026-007993#REF#
realised by: #REQ-UNISIG-SUB026-007994#REF#
realised by: #REQ-UNISIG-SUB026-007995#REF#
realised by: #REQ-UNISIG-SUB026-010209#REF#
realised by: #REQ-UNISIG-SUB026-007986#REF#
realised by: #REQ-UNISIG-SUB026-007996#REF#
realised by: #REQ-UNISIG-SUB026-007997#REF#
realised by: #REQ-UNISIG-SUB026-007998#REF#
realised by: #REQ-UNISIG-SUB026-008093#REF#
realised by: #REQ-UNISIG-SUB026-007999#REF#
realised by: #REQ-UNISIG-SUB026-008000#REF#
realised by: #REQ-UNISIG-SUB026-008001#REF#
realised by: #REQ-UNISIG-SUB026-008002#REF#
realised by: #REQ-UNISIG-SUB026-008004#REF#
realised by: #REQ-UNISIG-SUB026-008003#REF#
realised by: #REQ-UNISIG-SUB026-008006#REF#
realised by: #REQ-UNISIG-SUB026-008007#REF#
realised by: #REQ-UNISIG-SUB026-008008#REF#
realised by: #REQ-UNISIG-SUB026-008009#REF#
realised by: #REQ-UNISIG-SUB026-008010#REF#
realised by: #REQ-UNISIG-SUB026-008011#REF#

#REQ-UNISIG-SUB026-007979#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Modification of adhesion factor by driver
default value: not allowed
SRS name: Q_NVDRIVER_ADHES
#TEST-VAL-SUB026-3223#REF# FCT basic function Variablentest Q_NVDRIVER_ADHES

#REQ-UNISIG-SUB026-007980#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Shunting mode speed limit
default value: 30 km/h
SRS name: V_NVSHUNT
#TEST-VAL-SUB026-3224#REF# FCT basic function Variablentest V_NVSHUNT

#REQ-UNISIG-SUB026-007981#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Staff Responsible mode speed limit
default value: 40 km/h
SRS name: V_NVSTFF
#TEST-VAL-SUB026-3225#REF# FCT basic function Variablentest V_NVSTFF

#REQ-UNISIG-SUB026-007982#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
On Sight mode speed limit
default value: 30 km/h
SRS name: V_NVONSIGHT
#TEST-VAL-SUB026-3226#REF# FCT basic function Variablentest V_NVONSIGHT

#REQ-UNISIG-SUB026-3339#REF# zu.A.3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Limited Supervision mode speed limit
name: V_NVLIMSUPERV
default value: 100 km/h
#TEST-VAL-SUB026-5868#REF# FCT basic function Variable test V_NVLIMSUPERV

#REQ-UNISIG-SUB026-007983#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Unfitted mode speed limit
default value: 100 km/h
SRS name: V_NVUNFIT
#TEST-VAL-SUB026-3227#REF# FCT basic function Variablentest V_NVUNFIT

#REQ-UNISIG-SUB026-007984#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Release speed
default value: 40 km/h
SRS name: V_NVREL
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007985#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Distance to be used in Roll Away protection, Reverse movement protection and Standstill supervision
default value: 2 m
SRS name: D_NVROLL
#TEST-VAL-SUB026-3229#REF# FCT basic function Variablentest D_NVROLL

#REQ-UNISIG-SUB026-007987#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Speed limit for triggering the override function
default value: 0 km/h
SRS name: V_NVALLOWOVTRP
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007988#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Override speed limit to be supervised when the “override” function is active
default value: 30 km/h
SRS name: V_NVSUPOVTRP
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007989#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Distance for train trip suppression when override function is triggered
default value: 200 m
SRS name: D_NVOVTRP
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007990#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Max. time for train trip suppression when override function is triggered
default value: 60 s
SRS name: T_NVOVTRP
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007991#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Change of driver ID permitted while running
default value: yes
SRS name: M_NVDERUN
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007992#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
System reaction if radio channel monitoring time limit expires (T-Contact)
default value: no reaction
SRS name: M_NVCONTACT
TEST APPROACH:
The default value for T_NVCONTACT is infinitive. A change of T_NVCONTACT, via P3, includes the definition of M_NVCONTACT. 
The default value M_NVCONTACT has hence no functional relevance and can not be tested.
#TEST-VAL-SUB026-3237#REF# FCT basic function Variablentest M_NVCONTACT

#REQ-UNISIG-SUB026-007993#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Maximum time since creation in the RBC of last received telegram
default value: ∞
SRS name: T_NVCONTACT
#TEST-VAL-SUB026-5258#REF# FCT basic function Variable test T_NVCONTACT

#REQ-UNISIG-SUB026-007994#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Distance to be allowed for reversing in Post Trip mode
default value: 200 m
SRS name: D_NVPOTRP
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007995#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Max permitted distance to run in Staff Responsible mode
default value: ∞
SRS name: D_NVSTFF
#TEST-VAL-SUB026-5291#REF# FCT basic function D_NVSTFF default

#REQ-UNISIG-SUB026-010209#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Default location accuracy of a balise group
default value:12
SRS name: Q_NVLOCACC
#TEST-VAL-SUB026-5838#REF# FCT basic function Variable test Q_NVLOCACC

#REQ-UNISIG-SUB026-007986#REF# A3.2 #REQ-UNISIG-SUB026-007046#REF#
#REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Permission to release emergency brake
default value: Only at standstill
SRS name: Q_NVEMRRLS
#TEST-VAL-SUB026-3231#REF# FCT basic function Variable test Q_NVEMRRLS

#REQ-UNISIG-SUB026-007996#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Permission to use service brake in target speed monitoring
default value: yes
SRS name: Q_NVSBTSMPERM
#TEST-VAL-SUB026-5870#REF# FCT basic function default NV

#REQ-UNISIG-SUB026-007997#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Permission to use guidance curves
default value: no
SRS name: Q_NVGUIPERM
#TEST-VAL-SUB026-5628#REF# FCT basic function Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-007998#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Permission to use the service brake feedback
default value: no
SRS name: Q_NVSBFBPERM
#TEST-VAL-SUB026-5629#REF# FCT basic function Variable test Q_NVSBFBPERM

#REQ-UNISIG-SUB026-008093#REF# A3.2 #REQ-UNISIG-SUB026-008090#REF#
#REQ-UNISIG-SUB026-004258#REF#
LIst of National / Default Data:
Permission to inhibit the compensation of the speed measurement inaccuracy
default value: no
SRS name: Q_NVINHSMICPERM
#TEST-VAL-SUB026-5630#REF# FCT basic function Variable test Q_NVINHSMICPERM

#REQ-UNISIG-SUB026-007999#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Weighting factor for available wheel/rail adhesion
default value: 0
SRS name: M_NVAVADH
#TEST-VAL-SUB026-5634#REF# FCT basic function Variable test M_NVAVADH

#REQ-UNISIG-SUB026-008000#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Confidence level for emergency brake safe deceleration on dry rails
default value: 99.9999999 %
M_NVEBCL
#TEST-VAL-SUB026-5635#REF# FCT basic function Variable test M_NVEBCL

#REQ-UNISIG-SUB026-008001#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Train length step used for the integrated correction factor Kr_int
default value: N/A
SRS name: L_NVKRINT

--- FINALISED ---
The NVs with a defined default value N/A are not relevant for the application.
For these values the following rule is applied:
"The default value of the correction factor Kr_int shall be valid for any train length, and likewise the default value of the correction
factor Kv_int shall be valid for any brake position, speed and maximum emergency brake deceleration. This means that the Kr_int model does not
contain any train length step, and that the Kv_int model is valid for all train types and does neither contain any speed step nor any pivot
deceleration limit."
#ANALYSE-VALUNISIG-4800#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-008002#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Train length dependent integrated correction factor Kr_int
default value: 0.9
M_NVKRINT

clarification:
The default value of the correction factor Kr_int shall be valid for any train length, and likewise the default value of the correction factor
Kv_int shall be valid for any brake position, speed and maximum emergency brake deceleration. This means that the Kr_int model does not contain
any train length step, and that the Kv_int model is valid for all train types and does neither contain any speed step nor any pivot deceleration
limit.
#TEST-VAL-SUB026-5641#REF# FCT basic function Variable test M_NVKRINT

#REQ-UNISIG-SUB026-008004#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Speed dependent integrated correction factor Kv_int
default value: 0.7
M_NVKVINT

clarification:
The default value of the correction factor Kr_int shall be valid for any train length, and likewise the default value of the correction factor
Kv_int shall be valid for any brake position, speed and maximum emergency brake deceleration. This means that the Kr_int model does not contain
any train length step, and that the Kv_int model is valid for all train types and does neither contain any speed step nor any pivot deceleration
limit.
#TEST-VAL-SUB026-5639#REF# FCT basic function Variable test M_NVKVINT

#REQ-UNISIG-SUB026-008003#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Speed step used for the integrated correction factor Kv_int
default value: N/A
V_NVKVINT
Rel.7.1: neu durch BC-CR
--- FINALISED ---
The NVs with a defined default value N/A are not relevant for the application.
For these values the following rule is applied:
"The default value of the correction factor Kr_int shall be valid for any train length, and likewise the default value of the correction
factor Kv_int shall be valid for any brake position, speed and maximum emergency brake deceleration. This means that the Kr_int model does not
contain any train length step, and that the Kv_int model is valid for all train types and does neither contain any speed step nor any pivot
deceleration limit."
#ANALYSE-VALUNISIG-4801#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-008006#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Integrated correction factor for brake build up time
default value: 1.1
M_NVKTINT
Rel.7.1: neu durch BC-CR
#TEST-VAL-SUB026-5643#REF# FCT basic function Variable test M_NVKTINT

#REQ-UNISIG-SUB026-008007#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Maximum deceleration value under reduced adhesion conditions (1)
default value: 1,0 m/s2
A_NVMAXREDADH1
Rel.7.1: neu durch BC-CR
#TEST-VAL-SUB026-5631#REF# FCT basic function Variable test A_NVMAXREDADH1

#REQ-UNISIG-SUB026-008008#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Maximum deceleration value under reduced adhesion conditions (2)
default value: 0,7 m/s2
A_NVMAXREDADH2
Rel.7.1: neu durch BC-CR
#TEST-VAL-SUB026-5632#REF# FCT basic function Variable test A_NVMAXREDADH2

#REQ-UNISIG-SUB026-008009#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Maximum deceleration value under reduced adhesion conditions (3)
default value: 0.7 m/s2
A_NVMAXREDADH3
Rel.7.1: neu durch BC-CR
#TEST-VAL-SUB026-5633#REF# FCT basic function Variable test A_NVMAXREDADH3

#REQ-UNISIG-SUB026-008010#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Lower deceleration limit to determine the set of Kv_int to be used
default value: N/A
A_NVP12
Rel.7.1: neu durch BC-CR
--- FINALISED ---
The NVs with a defined default value N/A are not relevant for the application.
For these values the following rule is applied:
"The default value of the correction factor Kr_int shall be valid for any train length, and likewise the default value of the correction
factor Kv_int shall be valid for any brake position, speed and maximum emergency brake deceleration. This means that the Kr_int model does not
contain any train length step, and that the Kv_int model is valid for all train types and does neither contain any speed step nor any pivot
deceleration limit."
#ANALYSE-VALUNISIG-4802#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-008011#REF# A3.2 #REQ-UNISIG-SUB026-004258#REF#
List of National / Default Data:
Upper deceleration limit to determine the set of Kv_int to be used
default value: N/A
A_NVP23
Rel.7.1: neu durch BC-CR
--- FINALISED ---
The NVs with a defined default value N/A are not relevant for the application.
For these values the following rule is applied:
"The default value of the correction factor Kr_int shall be valid for any train length, and likewise the default value of the correction
factor Kv_int shall be valid for any brake position, speed and maximum emergency brake deceleration. This means that the Kr_int model does not
contain any train length step, and that the Kv_int model is valid for all train types and does neither contain any speed step nor any pivot
deceleration limit."
#ANALYSE-VALUNISIG-4803#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-004277#REF# A.3.4.1.2
A.3.4.1.2	The situations acting on the “status” of stored information are:
a)	the execution of a conditional emergency stop (3.10.2.2);
b)	the reception of a shortened MA (3.8.5.1.3, 3.8.5.1.4);
c)	the stored MA is shortened due to a section time-out (3.8.4.2.2);
d)	the SvL is shifted (to the DP if any or to the EOA) due to an overlap time-out (3.8.4.4.2) ;
e)	the stored MA is shortened due to an end section time-out (3.8.4.1.2);
f)	a cooperative MA revocation is granted by the onboard (3.8.6.2);
g)	inconsistency in a balise group marked as unlinked and the train is at standstill (3.16.2.5.2);
h)	a linking reaction led to a service brake and the train is at standstill (3.16.2.6.2) ;
i)	the reaction due to the supervision of the safe radio connection led to a service brake and the train is at standstill (3.16.3.4.5 b) ;
j)	the train category, axle load category, loading gauge or traction system is changed and the train is at standstill (3.18.3.7) ;
k)	driver closes the desk during SoM ;
l)	RAMS related supervision functions led to a service brake and the train is at standstill (3.16.2.7)
m)	inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill (3.16.2.4.4.2)
n)	the Limit of Authority becomes an End of Authority and the on-board considers an SvL (3.8.4.3.2)
TEST APPROACH:
The requirement summarizes and defines a letters for the conditions referred to later on in A.3.4.1.3 no additional functionality is defined
here.
The aim of the refinement verification is the exemplary verification of the condition recognition.
realised by: #REQ-UNISIG-SUB026-2201#REF#
realised by: #REQ-UNISIG-SUB026-2202#REF#
realised by: #REQ-UNISIG-SUB026-2203#REF#
realised by: #REQ-UNISIG-SUB026-2204#REF#
realised by: #REQ-UNISIG-SUB026-2205#REF#
realised by: #REQ-UNISIG-SUB026-2206#REF#
realised by: #REQ-UNISIG-SUB026-2207:01#REF#
realised by: #REQ-UNISIG-SUB026-2208#REF#
realised by: #REQ-UNISIG-SUB026-2209#REF#
realised by: #REQ-DESIGN-CR-0700:01#REF#
realised by: #REQ-DESIGN-CR-0629#REF#
realised by: #REQ-DESIGN-CR-0701#REF#
realised by: #REQ-UNISIG-SUB026-3024:01#REF#
realised by: #REQ-UNISIG-SUB026-010117#REF#

#REQ-UNISIG-SUB026-2201#REF# A3.4.1.2 #REQ-UNISIG-SUB026-001855#REF#
#REQ-UNISIG-SUB026-004277#REF#
a) the execution of a conditional emergency stop (3.10.2.2)
#TEST-VAL-SUB026-3478#REF# ECT basic function A.3.4.1a) location based plain/fixed text information

#REQ-UNISIG-SUB026-2202#REF# A3.4.1.2 #REQ-UNISIG-SUB026-001630#REF#
#REQ-UNISIG-SUB026-001632#REF#
#REQ-UNISIG-SUB026-004277#REF#
b) the reception of a shortened MA (3.8.5.1.3, 3.8.5.1.4)
#TEST-VAL-SUB026-3480#REF# ECT basic function A.3.4.1b) location based plain/fixed text information

#REQ-UNISIG-SUB026-2203#REF# A3.4.1.2 #REQ-UNISIG-SUB026-001558#REF#
#REQ-UNISIG-SUB026-004277#REF#
c) the stored MA is shortened due to a section time-out (3.8.4.2.2)
#TEST-VAL-SUB026-3482#REF# ECT basic function A.3.4.1c) location based plain/fixed text information

#REQ-UNISIG-SUB026-2204#REF# A3.4.1.2 #REQ-UNISIG-SUB026-001581#REF#
#REQ-UNISIG-SUB026-004277#REF#
d) the SvL is shifted (to the DP if any or to the EOA) due to an overlap time-out (3.8.4.4.2)
#TEST-VAL-SUB026-3399#REF# ECT DP A.3.4.1d) SvL is shifted to DP
#TEST-VAL-SUB026-3484#REF# ECT no DP A.3.4.1d) location based plain/fixed text information

#REQ-UNISIG-SUB026-2205#REF# A3.4.1.2 #REQ-UNISIG-SUB026-004277#REF#
#REQ-UNISIG-SUB026-010510#REF#
e) the stored MA is shortened due to an end section time-out (3.8.4.1.2)
#TEST-VAL-SUB026-3486#REF# ECT basic function A.3.4.1e) location based plain/fixed text information

#REQ-UNISIG-SUB026-2206#REF# A3.4.1.2 #REQ-UNISIG-SUB026-004277#REF#
f) a cooperative MA revocation is granted by the onboard (3.8.6.2)
Remark: This is applied also, when cooperative shorten new ma is longer as the current ma.
#TEST-VAL-SUB026-5899#REF# ECT MA extended by M9 Shortening of track description due accepting M9 defining a longer MA
#TEST-VAL-SUB026-3100#REF# ECT MA shorten by M9 Linkdaten werden nach cooperative shortenting of MA geloescht

#REQ-UNISIG-SUB026-2207:01#REF# A3.4.1.2 #REQ-DESIGN-CR-0197:02#REF#
#REQ-UNISIG-SUB026-004277#REF#
g) inconsistency in a balise group marked as unlinked (3.16.2.5.2) and the train is at standstill
#TEST-VAL-SUB026-3490#REF# ECT basic function A.3.4.1g) location based plain/fixed text information

#REQ-UNISIG-SUB026-2208#REF# A3.4.1.2 #REQ-UNISIG-SUB026-0665:01#REF#
#REQ-UNISIG-SUB026-004277#REF#
h) a linking reaction led to a service brake and the train is at standstill (3.16.2.6.2)
#TEST-VAL-SUB026-3492#REF# ECT basic function A.3.4.1h) location based plain/fixed text information

#REQ-UNISIG-SUB026-2209#REF# A3.4.1.2 #REQ-UNISIG-SUB026-004277#REF#
#REQ-UNISIG-SUB026-3209#REF#
i) the reaction due to the supervision of the safe radio connection led to a service brake and the train is at standstill (3.16.3.4.5 b)
#TEST-VAL-SUB026-3494#REF# ECT basic function A.3.4.1i) location based plain/fixed text information

#REQ-DESIGN-CR-0700:01#REF# A3.4.1.2 #REQ-UNISIG-SUB026-004124#REF#
#REQ-UNISIG-SUB026-004277#REF#
j) the train category, axle load category, loading gauge or traction system is changed and the train is at standstill(3.18.3.7)
test hint: traction system can only be changed with external train data. The driver cannot entered/changed the current traction system
TEST APPROACH:
The available traction system can be changed by sources different from the driver only. This feature is not part of R8. The verification for the
aspect change of traction system is hence omitted.
#TEST-VAL-SUB026-3A53#REF# ECT axle load GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-5203#REF# EET error expectation Change of train data other than defined in A.3.4.j does not lead to deletion of location based P72/76
#TEST-VAL-SUB026-3250#REF# ECT loading gauge MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3A50#REF# ECT train category Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 j (train category)

#REQ-DESIGN-CR-0629#REF# A3.4.1.2 #REQ-UNISIG-SUB026-004277#REF#
k ) driver closes the desk during SoM
#TEST-VAL-SUB026-3497#REF# ECT basic function A.3.4.1k) not location based plain/fixed text information

#REQ-DESIGN-CR-0701#REF# A3.4.1.2 #REQ-UNISIG-SUB026-003851#REF#
#REQ-UNISIG-SUB026-003859#REF#
#REQ-UNISIG-SUB026-004277#REF#
l) RAMS related supervision functions led to a service
brake and the train is at standstill (3.16.2.7)
TEST APPROACH:
The following aspects have been identified:
1) mitigation of balise reception degradation
2) mitigation of balise cross-talk while expecting repositioning information
#TEST-VAL-SUB026-3500#REF# ECT 1 A.3.4.1l) location based plain/fixed text information
#TEST-VAL-SUB026-5911#REF# ECT 2 A3.4.1.2 l Track condition big metal masses

#REQ-UNISIG-SUB026-3024:01#REF# A3.4.1.2 #REQ-DESIGN-CR-0195:02#REF#
#REQ-UNISIG-SUB026-004277#REF#
m) inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill(3.16.2.4.4.2)
#TEST-VAL-SUB026-3530#REF# EET CFX00038026 A.3.4.1m) effect on GP in SR
#TEST-VAL-SUB026-3503#REF# ECT basic function A.3.4.1m) effect on NV, GP and Axle load speed profile

#REQ-UNISIG-SUB026-010117#REF# A3.4.1.2 #REQ-UNISIG-SUB026-001575#REF#
#REQ-UNISIG-SUB026-004277#REF#
n) the Limit of Authority becomes an End of Authority and the on-board considers an SvL (3.8.4.3.2)
#TEST-VAL-SUB026-4E39#REF# ECT basic function GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3170:01#REF# A.3.4.1.3
A.3.4.1.3	Depending on the situation, the action can be:
a)	data is deleted,
b)	data is reset (set to initial states)
c)	data status is unchanged,
d)	data is to be revalidated




[1]: beyond the new SvL or in case of situation a, beyond the stop location of the accepted CES

[2]: The considered situations cannot occur when a list of balises to be used in SR is available onboard. Indeed, the onboard is in SR mode and
since no MA or track description are stored onboard, no new SvL may be defined.
[3]: In case of reception of a new non-infill MA (situation b or f), the stored MA is fully replaced with the new one. In case of reception of a
new infill MA (situation b), the stored MA is replaced beyond the infill location reference, i.e. the balise group at the next main signal
[4]: The considered situations a-d, f, h, i cannot occur when the default gradient for a TSR is used on-board.
[5]: The considered situation cannot occur because acceptance of this information has led to exit from SoM procedure.
[6]: The considered situations b-d, f cannot occur when a TAF request is stored on-board
[7]: If the start location of the Mode Profile is beyond the new SvL, the acknowledgement window of the Mode Profile shall be deleted as well
[8]: only if the location where to start to display the text is beyond the new SvL; otherwise all the text information (i.e. including end
location where to stop display, if any) shall remain unchanged
[9]: unchanged if the onboard is in SH mode
[10]: beyond the current max safe front end position of the train
[11]: the ERTMS/ETCS on-board equipment shall consider the current estimated front end and max safe front end positions of the train, as the EOA
and SvL respectively, with no release speed
[12]: If the start location of the Mode Profile is beyond the current max safe front end, the acknowledgement window of the Mode Profile shall
be deleted as well
[13]: only if the location where to start to display the text is beyond the current max safe front end; otherwise all the text information (i.e.
including end location where to stop display, if any) shall remain unchanged
[14]: In case of reception of a new non-infill MA with or without Mode Profile (situation b or f), the stored Mode Profile is deleted. In case
of reception of a new infill MA (situation b), the stored Mode Profile is deleted only beyond the infill location reference, i.e. the balise
group at the next main signal
realised by: #REQ-UNISIG-SUB026-3171:01#REF#
realised by: #REQ-UNISIG-SUB026-3172#REF#
realised by: #REQ-UNISIG-SUB026-010149#REF#
realised by: #REQ-UNISIG-SUB026-010150#REF#
realised by: #REQ-UNISIG-SUB026-2121:02#REF#
realised by: #REQ-DESIGN-CR-0702#REF#
realised by: #REQ-UNISIG-SUB026-2122:02#REF#
realised by: #REQ-DESIGN-CR-0703#REF#
realised by: #REQ-UNISIG-SUB026-2123:02#REF#
realised by: #REQ-DESIGN-CR-0704#REF#
realised by: #REQ-UNISIG-SUB026-2124:02#REF#
realised by: #REQ-DESIGN-CR-0705#REF#
realised by: #REQ-UNISIG-SUB026-2125:02#REF#
realised by: #REQ-DESIGN-CR-0706#REF#
realised by: #REQ-UNISIG-SUB026-3173:02#REF#
realised by: #REQ-UNISIG-SUB026-3174#REF#
realised by: #REQ-UNISIG-SUB026-3175:02#REF#
realised by: #REQ-UNISIG-SUB026-3176#REF#
realised by: #REQ-UNISIG-SUB026-3177:02#REF#
realised by: #REQ-DESIGN-CR-0708#REF#
realised by: #REQ-UNISIG-SUB026-010158#REF#
realised by: #REQ-UNISIG-SUB026-010159#REF#
realised by: #REQ-UNISIG-SUB026-2128:02#REF#
realised by: #REQ-DESIGN-CR-0709#REF#
realised by: #REQ-UNISIG-SUB026-3178:02#REF#
realised by: #REQ-UNISIG-SUB026-3179#REF#
realised by: #REQ-UNISIG-SUB026-3180:01#REF#
realised by: #REQ-UNISIG-SUB026-3181#REF#
realised by: #REQ-DESIGN-CR-0331:02#REF#
realised by: #REQ-DESIGN-CR-0710#REF#
realised by: #REQ-UNISIG-SUB026-3350:01#REF#
realised by: #REQ-DESIGN-CR-0711#REF#
realised by: #REQ-UNISIG-SUB026-010145#REF#
realised by: #REQ-UNISIG-SUB026-010146#REF#
realised by: #REQ-UNISIG-SUB026-010160#REF#
realised by: #REQ-UNISIG-SUB026-010161#REF#
realised by: #REQ-UNISIG-SUB026-2133:02#REF#
realised by: #REQ-DESIGN-CR-0712#REF#
realised by: #REQ-UNISIG-SUB026-2134:02#REF#
realised by: #REQ-DESIGN-CR-0713#REF#
realised by: #REQ-UNISIG-SUB026-3051:01#REF#
realised by: #REQ-UNISIG-SUB026-2135:02#REF#
realised by: #REQ-DESIGN-CR-0714#REF#
realised by: #REQ-UNISIG-SUB026-3052:01#REF#
realised by: #REQ-UNISIG-SUB026-2136:02#REF#
realised by: #REQ-DESIGN-CR-0715#REF#
realised by: #REQ-UNISIG-SUB026-3351:01#REF#
realised by: #REQ-UNISIG-SUB026-3352#REF#
realised by: #REQ-UNISIG-SUB026-2138:02#REF#
realised by: #REQ-DESIGN-CR-0716#REF#
realised by: #REQ-UNISIG-SUB026-2139:02#REF#
realised by: #REQ-DESIGN-CR-0717#REF#
realised by: #REQ-UNISIG-SUB026-3353:01#REF#
realised by: #REQ-UNISIG-SUB026-3182#REF#
realised by: #REQ-UNISIG-SUB026-2141:02#REF#
realised by: #REQ-UNISIG-SUB026-3183:01#REF#
realised by: #REQ-UNISIG-SUB026-2142:02#REF#
realised by: #REQ-DESIGN-CR-0719#REF#
realised by: #REQ-UNISIG-SUB026-2143:02#REF#
realised by: #REQ-DESIGN-CR-0720#REF#
realised by: #REQ-UNISIG-SUB026-3184:01#REF#
realised by: #REQ-UNISIG-SUB026-3185#REF#
realised by: #REQ-UNISIG-SUB026-3186:01#REF#
realised by: #REQ-UNISIG-SUB026-3187#REF#
realised by: #REQ-UNISIG-SUB026-3188:01#REF#
realised by: #REQ-DESIGN-CR-0722#REF#
realised by: #REQ-UNISIG-SUB026-3189:01#REF#
realised by: #REQ-DESIGN-CR-0723#REF#
realised by: #REQ-UNISIG-SUB026-3190:01#REF#
realised by: #REQ-UNISIG-SUB026-3191#REF#
realised by: #REQ-DESIGN-CR-0764:02#REF#
realised by: #REQ-DESIGN-CR-0765#REF#
realised by: #REQ-UNISIG-SUB026-3192:01#REF#
realised by: #REQ-DESIGN-CR-0724#REF#
realised by: #REQ-DESIGN-CR-0762:02#REF#
realised by: #REQ-DESIGN-CR-0763#REF#
realised by: #REQ-UNISIG-SUB026-3193:01#REF#
realised by: #REQ-UNISIG-SUB026-3194#REF#
realised by: #REQ-UNISIG-SUB026-3195:01#REF#
realised by: #REQ-DESIGN-CR-0725#REF#
realised by: #REQ-UNISIG-SUB026-2153:01#REF#
realised by: #REQ-DESIGN-CR-0726#REF#
realised by: #REQ-UNISIG-SUB026-3200:01#REF#
realised by: #REQ-DESIGN-CR-0727#REF#
realised by: #REQ-DESIGN-CR-0761:02#REF#
realised by: #REQ-DESIGN-CR-0728#REF#
realised by: #REQ-UNISIG-SUB026-010165#REF#
realised by: #REQ-UNISIG-SUB026-010166#REF#
realised by: #REQ-UNISIG-SUB026-010137#REF#
realised by: #REQ-UNISIG-SUB026-010138#REF#
realised by: #REQ-UNISIG-SUB026-010167#REF#
realised by: #REQ-UNISIG-SUB026-010168#REF#
realised by: #REQ-UNISIG-SUB026-010169#REF#
realised by: #REQ-UNISIG-SUB026-010170#REF#
realised by: #REQ-UNISIG-SUB026-010171#REF#
realised by: #REQ-UNISIG-SUB026-010172#REF#
realised by: #REQ-UNISIG-SUB026-010163#REF#
realised by: #REQ-UNISIG-SUB026-010164#REF#
realised by: #REQ-UNISIG-SUB026-2210#REF#
realised by: #REQ-UNISIG-SUB026-3205#REF#
realised by: #REQ-UNISIG-SUB026-010151#REF#
realised by: #REQ-UNISIG-SUB026-010153#REF#
realised by: #REQ-UNISIG-SUB026-3202#REF#
realised by: #REQ-UNISIG-SUB026-3203#REF#
realised by: #REQ-DESIGN-CR-0729#REF#
realised by: #REQ-UNISIG-SUB026-3053#REF#
realised by: #REQ-UNISIG-SUB026-3204#REF#
realised by: #REQ-UNISIG-SUB026-010154#REF#
realised by: #REQ-UNISIG-SUB026-010155#REF#
realised by: #REQ-UNISIG-SUB026-010152#REF#
realised by: #REQ-UNISIG-SUB026-010156#REF#
realised by: #REQ-UNISIG-SUB026-010157#REF#

#REQ-UNISIG-SUB026-3171:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
National Values shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A12#REF# FCT a NV, LTO, Route Suitability: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A16#REF# FCT b NV, LTO, Route Suitability: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A25#REF# FCT c NV, LTO, Route Suitability: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A29#REF# FCT d NV, LTO, Route Suitability: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A33#REF# FCT e NV, LTO, Route Suitability: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A21#REF# FCT f NV, LTO, Route Suitability: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A37#REF# FCT g NV, LTO, Route Suitability: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A41#REF# FCT h NV, LTO, Route Suitability: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A45#REF# FCT i NV, LTO, Route Suitability: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A51#REF# FCT j NV, LTO, Route Suitability: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A57#REF# FCT l NV, LTO, Route Suitability: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3503#REF# FCT m A.3.4.1m) effect on NV, GP and Axle load speed profile
#TEST-VAL-SUB026-4E37#REF# FCT n NV, LTO, Route Suitability: A.3.4.1.2 n (the Limit of Authority becomes an End of Authority and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3172#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
National Values shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3879#REF# FCT basic function Effect of closing desk during SoM on NationalValues and RBC transitionOrder (two mobiles)

#REQ-UNISIG-SUB026-010149#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
If current not yet applicable National Values are also not valid at the stop location, which is defined with [1] or [10], then these National
Values shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
UNISIG clarification:
announced NVs are deleted only, when they are not valid at the stop locaction
#TEST-VAL-SUB026-4E48#REF# FCT a A.3.4.1a) Not yet applicable National Values
#TEST-VAL-SUB026-4E49#REF# FCT b A.3.4.1b) Not yet applicable National Values
#TEST-VAL-SUB026-4E50#REF# FCT c A.3.4.1c) Not yet applicable National Values
#TEST-VAL-SUB026-4E51#REF# FCT d A.3.4.1d) Not yet applicable National Values
#TEST-VAL-SUB026-4E52#REF# FCT e A.3.4.1e) Not yet applicable National Values
#TEST-VAL-SUB026-4E53#REF# FCT f A.3.4.1f) Not yet applicable National Values
#TEST-VAL-SUB026-4E54#REF# FCT g A.3.4.1g) Not yet applicable National Values
#TEST-VAL-SUB026-4E55#REF# FCT h A.3.4.1h) Not yet applicable National Values
#TEST-VAL-SUB026-4E56#REF# FCT i A.3.4.1i) Not yet applicable National Values
#TEST-VAL-SUB026-4E57#REF# FCT j A.3.4.1j) Not yet applicable National Values
#TEST-VAL-SUB026-4E58#REF# FCT l A.3.4.1l) Not yet applicable National Values
#TEST-VAL-SUB026-4E59#REF# FCT m A.3.4.1m) Not yet applicable National Values
#TEST-VAL-SUB026-4E60#REF# FCT n A.3.4.1n) Not yet applicable National Values

#REQ-UNISIG-SUB026-010150#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Not yet applicable National Values shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-4E61#REF# FCT basic function A.3.4.1k) Not yet applicable National Values

#REQ-UNISIG-SUB026-2121:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Linking information shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
#TEST-VAL-SUB026-3A11#REF# FCT a Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3A15#REF# FCT b Linking, Reversing area/supervision, GeoPos A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A24#REF# FCT c Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A28#REF# FCT d Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A32#REF# FCT e Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A19#REF# FCT f Linking, Reversing area/supervision, GeoPos A.3.4.1.2 f (Request of Shorten MA)
#TEST-VAL-SUB026-3A36#REF# FCT g Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A40#REF# FCT h Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A44#REF# FCT i Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A50#REF# FCT j Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 j (train category)
#TEST-VAL-SUB026-3A56#REF# FCT l Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3529#REF# FCT m A.3.4.1m) effect on Linking information
#TEST-VAL-SUB026-4E36#REF# FCT n Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0702#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Linking information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3884#REF# FCT basic function Effect of closing desk during SoM on LinkingInformation and TC excluding BMM

#REQ-UNISIG-SUB026-2122:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Movement authority shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] and [11] shall be considered.
this requirement is not relevant for reason b and f, because the new ma replaced the current ma - see also condtion[3]
#TEST-VAL-SUB026-3A32#REF# EET CFX00040091 Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3241#REF# FCT a MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# FCT b MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3243#REF# FCT c MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 c (shortened of MA due to section time-out)
#TEST-VAL-SUB026-3244#REF# FCT d MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3245#REF# FCT e MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-7616#REF# EET error expectation MA when train stops with estimated front end between EoA and SvL
#TEST-VAL-SUB026-3246#REF# FCT f MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 f (the Request of Shorten MA)
#TEST-VAL-SUB026-3247#REF# FCT g MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3248#REF# FCT h MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3249#REF# FCT i MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3250#REF# FCT j MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3301#REF# FCT l MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E44#REF# FCT m MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 m (inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill)
#TEST-VAL-SUB026-4E43#REF# FCT n MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-007048:02#REF# table.A.3.4 #ANA-UNISIG-MAData-0008:01#REF#
If the reason of shorten stored information is the acceptance of a conditional emergency stop
AND
the stop location is located between EoA and SvL,
the following rules for OL, DP and SvL, if available, shall be applied:
∙	if an OL is available, the OL and the OL-Releasespeed shall be deleted and if no DP is available, the SvL shall be shortened to EoA
∙	if a DP is available and the new stop location is behind the DP location, the SvL shall be shortened to the DP location and
DP-Releasespeed shall be deleted
∙	if a DP is available and the new stop location is in front off the DP location, the DP location and SvL shall be shortened to the new
stop location and the DP-Releasespeed shall be deleted.
∙	if no OL and no DP is available the SvL shall be shortened to to the new stop location.

remark: This is not relevant for a MA with a LoA, because there is'nt supervised a SvL.
UNISIG clarification:
it's not clear, what the obu has to do, if the CES loacation between EoA and SvL - see analysis
TEST APPROACH:
The following aspects have been identified: 
1. OL and DP
1.1 CES location behind DP
1.2 CES location in front of DP
2. OL without DP
3. DP only
4. neither OL nor DP
#TEST-VAL-SUB026-4H41#REF# FCT 1.1 , CFX00039944 Conditional Emergency Stop stop location between EoA and SvL - MA with DP/OL on board, stop location behind DP
#TEST-VAL-SUB026-4H39#REF# FCT 1.2 , CFX00039944 Conditional Emergency Stop location between EoA and SvL - MA with DP and OL on board, stop location in front of DP
#TEST-VAL-SUB026-4H38#REF# FCT 2 , CFX00039944 Conditional Emergency Stop stop location between EoA and SvL - MA with OL without DP on board
#TEST-VAL-SUB026-4H40#REF# FCT 3 , CFX00039944 Conditional Emergency Stop stop location between EoA and SvL - MA with DP on board, stop location in front of DP
#TEST-VAL-SUB026-7846#REF# FCT 4 Conditional Emergency Stop stop location between EoA(estimated front end) and SvL(max safe front end) - MA with neither OL nor DP
#TEST-VAL-SUB026-4H42#REF# EET CFX00039944 Buffered Conditional Emergency Stop stop location between EoA and SvL - MA with DP/OL on board, stop location in front DP

#REQ-DESIGN-CR-0703#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Movement authority shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
condition[5] ist only a remark and is disregarded
#ANALYSE-VALUNISIG-4039#REF# FCT The considered situation cannot occur because acceptance of this information has led to exit from SoM procedure.

#REQ-UNISIG-SUB026-2123:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Gradient Profile shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.

At the end of the profile an EndOfProfile marker shall be placed.
UNISIG clarification:
An end of profile marker must be set at the new end of profile
#TEST-VAL-SUB026-3A14#REF# FCT a GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 a (execution of CES)
#TEST-VAL-SUB026-3A18#REF# FCT b GP, RBC ID/phone numbers: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A27#REF# FCT c GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A31#REF# FCT d GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A35#REF# FCT e GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A23#REF# FCT f GP, RBC ID/phone numbers: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A39#REF# FCT g GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A43#REF# FCT h GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A47#REF# FCT i GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A53#REF# FCT j GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A59#REF# FCT l GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E38#REF# FCT m GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 m (linked BG inconsisistency and no linking is used onboard)
#TEST-VAL-SUB026-4E39#REF# FCT n GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0704#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Gradient Profile shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3889#REF# FCT basic function Effect of closing desk during SoM on GP

#REQ-UNISIG-SUB026-2124:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
International SSP shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.

At the end of the profile an EndOfProfile marker shall be placed.
UNISIG clarification:
An end of profile marker must be set at the new end of profile
#TEST-VAL-SUB026-3241#REF# FCT a MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# FCT b MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3243#REF# FCT c MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 c (shortened of MA due to section time-out)
#TEST-VAL-SUB026-3244#REF# FCT d MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3245#REF# FCT e MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3246#REF# FCT f MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 f (the Request of Shorten MA)
#TEST-VAL-SUB026-3247#REF# FCT g MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3248#REF# FCT h MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3249#REF# FCT i MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3250#REF# FCT j MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3301#REF# FCT l MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E44#REF# FCT m MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 m (inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill)
#TEST-VAL-SUB026-4E43#REF# FCT n MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0705#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
International SSP shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3885#REF# FCT basic function Effect of closing desk during SoM SSP

#REQ-UNISIG-SUB026-2125:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Axle load speed profile shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
#TEST-VAL-SUB026-3241#REF# FCT a MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# FCT b MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3243#REF# FCT c MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 c (shortened of MA due to section time-out)
#TEST-VAL-SUB026-3244#REF# FCT d MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3245#REF# FCT e MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3246#REF# FCT f MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 f (the Request of Shorten MA)
#TEST-VAL-SUB026-3247#REF# FCT g MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3248#REF# FCT h MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3249#REF# FCT i MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3250#REF# FCT j MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3301#REF# FCT l MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E44#REF# FCT m MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 m (inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill)
#TEST-VAL-SUB026-4E43#REF# FCT n MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0706#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Axle load speed profile shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3883#REF# FCT basic function Effect of closing desk during SoM on ASP and TSR

#REQ-UNISIG-SUB026-3173:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
STM max speed shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4D57#REF# FCT a A.3.4.1.2a) STM max speed and STM system speed/distance when a conditional emergency stop is executed
#TEST-VAL-SUB026-4F10#REF# FCT b A.3.4.1.2b) STM max speed and STM system speed/distance when reception of a shortened MA
#TEST-VAL-SUB026-4512#REF# FCT c A.3.4.1.2c) STM max speed and STM system speed/distance when MA is shortened due to a section time-out
#TEST-VAL-SUB026-4513#REF# FCT d A.3.4.1.2d) STM max speed and STM system speed/distance when MA is shortened due to a overlap time-out
#TEST-VAL-SUB026-4514#REF# FCT e A.3.4.1.2e) STM max speed and STM system speed/distance when MA is shortened due to a end section time-out
#TEST-VAL-SUB026-3615#REF# EET error expectation A.3.4.1.2l) STM max speed and STM system speed/distance when MA is shortened due to balise cross-talk while expecting repositioning information
#TEST-VAL-SUB026-4515#REF# FCT f A.3.4.1.2f) STM max speed and STM system speed/distance when MA is shortened due cooperative MA revocation is granted by the onboard
#TEST-VAL-SUB026-4E04#REF# FCT g A.3.4.1.2g) STM max speed and STM system speed/distance when inconsistency in a balise group marked as unlinked
#TEST-VAL-SUB026-4E05#REF# FCT h A.3.4.1.2h) STM max speed and STM system speed/distance when linking reaction led to service brake and train is at standstill
#TEST-VAL-SUB026-4D58#REF# FCT i A.3.4.1.2i) STM max speed and STM system speed/distance when the Radio Link is Supervised
#TEST-VAL-SUB026-4519#REF# FCT j A.3.4.1.2j) STM max speed and STM system speed/distance when MA is shortened due change of axle load
#TEST-VAL-SUB026-4E07#REF# FCT l A.3.4.1.2l) STM max speed and STM system speed/distance when RAMS related supervision led to a service bake
#TEST-VAL-SUB026-4E06#REF# FCT m A.3.4.1.2m) STM max speed and STM system speed/distance when inconsistency in a balise group marked as linked and no linking is used on board
#TEST-VAL-SUB026-4E45#REF# FCT n A.3.4.1.2n) LoA becomes an EoA and the on-board considers an SvL

#REQ-UNISIG-SUB026-3174#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
STM max speed shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM).
#TEST-VAL-SUB026-4D59#REF# FCT basic function A.3.4.1.2k) STM max speed and STM system speed/distance when the driver closes desk during SoM

#REQ-UNISIG-SUB026-3175:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
STM system speed/distance shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4D57#REF# FCT a A.3.4.1.2a) STM max speed and STM system speed/distance when a conditional emergency stop is executed
#TEST-VAL-SUB026-4F10#REF# FCT b A.3.4.1.2b) STM max speed and STM system speed/distance when reception of a shortened MA
#TEST-VAL-SUB026-4512#REF# FCT c A.3.4.1.2c) STM max speed and STM system speed/distance when MA is shortened due to a section time-out
#TEST-VAL-SUB026-4513#REF# FCT d A.3.4.1.2d) STM max speed and STM system speed/distance when MA is shortened due to a overlap time-out
#TEST-VAL-SUB026-4514#REF# FCT e A.3.4.1.2e) STM max speed and STM system speed/distance when MA is shortened due to a end section time-out
#TEST-VAL-SUB026-3615#REF# EET error expectation A.3.4.1.2l) STM max speed and STM system speed/distance when MA is shortened due to balise cross-talk while expecting repositioning information
#TEST-VAL-SUB026-4515#REF# FCT f A.3.4.1.2f) STM max speed and STM system speed/distance when MA is shortened due cooperative MA revocation is granted by the onboard
#TEST-VAL-SUB026-4E04#REF# FCT g A.3.4.1.2g) STM max speed and STM system speed/distance when inconsistency in a balise group marked as unlinked
#TEST-VAL-SUB026-4E05#REF# FCT h A.3.4.1.2h) STM max speed and STM system speed/distance when linking reaction led to service brake and train is at standstill
#TEST-VAL-SUB026-4D58#REF# FCT i A.3.4.1.2i) STM max speed and STM system speed/distance when the Radio Link is Supervised
#TEST-VAL-SUB026-4519#REF# FCT j A.3.4.1.2j) STM max speed and STM system speed/distance when MA is shortened due change of axle load
#TEST-VAL-SUB026-4E07#REF# FCT l A.3.4.1.2l) STM max speed and STM system speed/distance when RAMS related supervision led to a service bake
#TEST-VAL-SUB026-4E06#REF# FCT m A.3.4.1.2m) STM max speed and STM system speed/distance when inconsistency in a balise group marked as linked and no linking is used on board
#TEST-VAL-SUB026-4E45#REF# FCT n A.3.4.1.2n) LoA becomes an EoA and the on-board considers an SvL

#REQ-UNISIG-SUB026-3176#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
STM system speed/distance shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM).
#TEST-VAL-SUB026-4D59#REF# FCT basic function A.3.4.1.2k) STM max speed and STM system speed/distance when the driver closes desk during SoM

#REQ-UNISIG-SUB026-3177:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Level Transition Order shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A12#REF# FCT a NV, LTO, Route Suitability: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A16#REF# FCT b NV, LTO, Route Suitability: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A25#REF# FCT c NV, LTO, Route Suitability: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A29#REF# FCT d NV, LTO, Route Suitability: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A33#REF# FCT e NV, LTO, Route Suitability: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3507#REF# EET error expectation A.3.4.1m) effect on Level Transition Order and level transition buffer
#TEST-VAL-SUB026-3A21#REF# FCT f NV, LTO, Route Suitability: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A37#REF# FCT g NV, LTO, Route Suitability: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A41#REF# FCT h NV, LTO, Route Suitability: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A45#REF# FCT i NV, LTO, Route Suitability: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A51#REF# FCT j NV, LTO, Route Suitability: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A57#REF# FCT l NV, LTO, Route Suitability: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3533#REF# FCT m A.3.4.1m) effect on plain/fixed text and level transition order in SR
#TEST-VAL-SUB026-4E37#REF# FCT n NV, LTO, Route Suitability: A.3.4.1.2 n (the Limit of Authority becomes an End of Authority and the on-board considers an SvL)

#REQ-DESIGN-CR-0708#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Level Transition Order shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3882#REF# FCT basic function Effect of closing desk during SoM on LvlTransitionOrder and AdhesionFactor
#TEST-VAL-SUB026-3876#REF# EET error expectation Effect of closing desk during SoM on in LT buffer stored unconditional EmergencyStop message

#REQ-UNISIG-SUB026-010158#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Stop Shunting on desk opening shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#ANALYSE-VALUNISIG-4788#REF# FCT The information Stop Shunting on desk opening is accepted in PS only. The information is deleted when leaving PS. The situation A3.4.1.2 a-i and l-n can not occur in PS as the appropriated functions are inactive. Train data change via DMI is not possible in PS while the change of train category, axle load category, loading gauge or traction system via external sources is not part of R8. The requirement has hence no functional relevance.

#REQ-UNISIG-SUB026-010159#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Stop Shunting on desk opening shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#ANALYSE-VALUNISIG-5335#REF# FCT The information Stop Shunting on desk opening is accepted in PS only. The information is deleted when leaving PS. The requirement has hence no functional relevance.

#REQ-UNISIG-SUB026-2128:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
#REQ-UNISIG-SUB026-3204#REF#
List of balises for SH area shall be deleted in situations A3.4.1.2 a-n (except for k).

If the onboard is in mode SHUNTING, List of balises for SH area shall be unchanged.
condition[9] can used for all situation, because the other situations can not entered in SH
TEST APPROACH:
Situation b, c, d, e, f and n can not occur in SH as no MA is available in SH.
Situation a, h, i and j can not occur in SH as the function manage emergency stop, check linking consistency, check safe radio connection and
train data entry are inactive in SH.
Situation l can not occur in SH as the function check linking consistency is inactive and Repositioning Information is rejected in SH.
Hence the verification of the aspect ETCS mode SH is limited to condition g and m.

The Situation e, g-j, l, m have no relevance for modes apart from SH as received MP starting beyond the max safe front is deleted while the mode
transition takes place when the start of the MP is reached with the max save front end. The mode transition has already taken place or will not
be executed at all. 
Situation b and f have no relevance as the reception of a new MA deletes a former received MP.
For any later mode transition following applies a previously received list of balise groups for SH area is deleted or replaced by a new list of
balise groups for SH area refer 3.12.4.4, 5.6.2.2 A050.
Hence the verification of the aspect ETCS mode unequal SH is limited to the situation a, c, d and n.
#TEST-VAL-SUB026-5921#REF# EET CFX00040838 A3.4.1.2 reception of shorten MA with new List of balises for SH Area
#TEST-VAL-SUB026-5916#REF# FCT a A3.4.1.2 a List of balises for SH area
#TEST-VAL-SUB026-5917#REF# FCT c A3.4.1.2 c List of balises for SH area
#TEST-VAL-SUB026-5918#REF# FCT d A3.4.1.2 d List of balises for SH area
#TEST-VAL-SUB026-5920#REF# EET error expectation A3.4.1.2 m List of balises for SH area - stop location in SH area
#TEST-VAL-SUB026-5923#REF# EET error expectation A3.4.1.2 g List of balises for SH area - stop location in SH area
#TEST-VAL-SUB026-3527#REF# FCT g) in SH A.3.4.1g) effect on List of balises for SH Area if onboard is in SH mode
#TEST-VAL-SUB026-3508#REF# FCT m) in SH A.3.4.1m) effect on List of balises for SH Area if onboard is in SH mode
#TEST-VAL-SUB026-5919#REF# FCT n A3.4.1.2 n List of balises for SH area

#REQ-DESIGN-CR-0709#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
List of balises for SH area shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
condition[5] is only a hint
#ANALYSE-VALUNISIG-4794#REF# FCT P49 is accepted along with M2 or P80 MP-SH, included in an MA. The accepting this information means to leave SoM. The condition can hence not occur.

#REQ-UNISIG-SUB026-3178:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
MA Request Parameters shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A52#REF# FCT j PR and MA req params, RBC transition order, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3506#REF# FCT m A.3.4.1m) effect on Route Suitability Data, MAR parameter
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3179#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
MA Request Parameters shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3877#REF# FCT basic function Effect of closing desk during SoM on MA requestParameters and Position reportParameters

#REQ-UNISIG-SUB026-3180:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Position Report parameters shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A52#REF# FCT j PR and MA req params, RBC transition order, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3504#REF# FCT m A.3.4.1m) effect on GeoPos, train location, PR parameter
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3181#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Position Report parameters shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3877#REF# FCT basic function Effect of closing desk during SoM on MA requestParameters and Position reportParameters

#REQ-DESIGN-CR-0331:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
List of Balises in SR Authority + SR mode speed limit and distance shall remain unchanged in situations A3.4.1.2 a-n (except for k).
condition[2] is only a hint
--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
TEST APPROACH:
The acceptance of the information M2, List of Balises in SR Authority + SR mode speed limit and distance, leads to the transition to SR.
Condition b, c, d, e, f and n can not occur in SR as no MA is available in SR.
Condition a, h and i can not occur in SR as the function manage conditional emergency stop, check linking consistency and check safe radio
connection are inactive in SR.
Condition l can not occur in SR as the function check linking consistency is inactive and Repositioning Information is rejected in SR.
Hence the verification of the aspect SH is limited to condition g, j and m. 
#TEST-VAL-SUB026-4E46#REF# FCT g A.3.4.1g) effect on List of Balises in SR Authority and SR mode speed limit and distance
#TEST-VAL-SUB026-4E47#REF# FCT j A.3.4.1j) effect on List of Balises in SR Authority and SR mode speed limit and distance
#TEST-VAL-SUB026-3510#REF# FCT m-List of Balises in SR Authority A.3.4.1m) effect on List of Balises in SR Authority
#TEST-VAL-SUB026-3511#REF# FCT m-SR speed and distance A.3.4.1m) effect on SR mode speed limit and distance

#REQ-DESIGN-CR-0710#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
List of Balises in SR Authority + SR mode speed limit and distance shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
condition[5] is only a hint
TEST APPROACH:
This requirement does not refer to the SR mode speed limit and SR distance as part of the National Values because the values remain unchanged in
situation k. (see #REQ-UNISIG-SUB026-3172#). It refers to the values which can be sent by trackside or changed by driver. SR mode speed limit
and SR distance can be changed by driver only if in SR(see #REQ-SAS_DMI-003520#). SR mode speed limit is not sent by trackside.
Hence, only the verification of the List of Balises in SR authority and the SR distance sent by trackside is needed.
#TEST-VAL-SUB026-3868#REF# FCT basic function Effect of closing desk during SoM on List of Balises in SR Authority and SR distance

#REQ-UNISIG-SUB026-3350:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Temporary Speed Restrictions shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3241#REF# FCT a MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# FCT b MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3243#REF# FCT c MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 c (shortened of MA due to section time-out)
#TEST-VAL-SUB026-3244#REF# FCT d MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3245#REF# FCT e MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3246#REF# FCT f MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 f (the Request of Shorten MA)
#TEST-VAL-SUB026-3247#REF# FCT g MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3248#REF# FCT h MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3249#REF# FCT i MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3250#REF# FCT j MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3301#REF# FCT l MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E44#REF# FCT m MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 m (inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill)
#TEST-VAL-SUB026-4E43#REF# FCT n MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0711#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Temporary Speed Restrictions shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3883#REF# FCT basic function Effect of closing desk during SoM on ASP and TSR

#REQ-UNISIG-SUB026-010145#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Inhibition of revocable TSRs from balises in L2/3 shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-5822#REF# FCT a, b, c, d, f A3.4.1.2 a, b, c, d, f - Inhibition of revocable TSRs from balises in L2/3
#TEST-VAL-SUB026-5823#REF# FCT e, h, j, n A3.4.1.2 e, h, j, n - Inhibition of revocable TSRs from balises in L2/3
#TEST-VAL-SUB026-5824#REF# FCT g, i, l, m A3.4.1.2 g, i, l, m - Inhibition of revocable TSRs from balises in L2/3

#REQ-UNISIG-SUB026-010146#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Inhibition of revocable TSRs from balises in L2/3 shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-5821#REF# FCT basic function A3.4.1.2 k - Inhibition of revocable TSRs from balises in L2/3

#REQ-UNISIG-SUB026-010160#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Default Gradient for TSR shall remain unchanged in situations A3.4.1.2 a-n (except for k).
condition[4] is only a hint
--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4E79#REF# FCT a, b, c, d, f A3.4.1.2 a, b, c, d, f - Default Gradient for TSR
#TEST-VAL-SUB026-4E80#REF# FCT e, h, j, n A3.4.1.2 e, h, j, n - Default Gradient for TSR
#TEST-VAL-SUB026-4E81#REF# FCT g, i, l, m A3.4.1.2 g, i, l, m - Default Gradient for TSR

#REQ-UNISIG-SUB026-010161#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Default Gradient for TSR shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-4E82#REF# FCT basic function A.3.4.1k) Default Gradient for TSR

#REQ-UNISIG-SUB026-2133:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Signalling related Speed Restriction shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
TEST APPROACH:
Clarification for situation f condition [1]:
A 'Request to Shorten MA' (M9) includes a 'Level 2/3 Movement Authority' (P15). A new MA replaces a previously received MA refer
#REQ-UNISIG-SUB026-0037#REF# . The 'Signalling related Speed Restriction' is hence not shorten but deleted completely.
Clarification for situation b condition [1]:
A new MA replaces a previously received MA refer #REQ-UNISIG-SUB026-0037#REF#. The 'Signalling related Speed Restriction' is hence not shorten
but deleted(P15) or replaced (P12) completely.
#TEST-VAL-SUB026-3A14#REF# FCT a GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 a (execution of CES)
#TEST-VAL-SUB026-3125#REF# FCT b, f New V_MAIN overrides old one
#TEST-VAL-SUB026-3A27#REF# FCT c GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A31#REF# FCT d GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A35#REF# FCT e GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A39#REF# FCT g GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A43#REF# FCT h GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A47#REF# FCT i GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A53#REF# FCT j GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A59#REF# FCT l GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E38#REF# FCT m GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 m (linked BG inconsisistency and no linking is used onboard)
#TEST-VAL-SUB026-4E39#REF# FCT n GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0712#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Signalling related Speed Restriction shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
condition[5] is only a hint
#ANALYSE-VALUNISIG-4037#REF# FCT The considered situation cannot occur because acceptance of this information has led to exit from SoM procedure.

#REQ-UNISIG-SUB026-2134:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Route Suitability Data shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
#TEST-VAL-SUB026-3A12#REF# FCT a NV, LTO, Route Suitability: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A16#REF# FCT b NV, LTO, Route Suitability: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A25#REF# FCT c NV, LTO, Route Suitability: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A29#REF# FCT d NV, LTO, Route Suitability: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A33#REF# FCT e NV, LTO, Route Suitability: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A21#REF# FCT f NV, LTO, Route Suitability: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A37#REF# FCT g NV, LTO, Route Suitability: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A41#REF# FCT h NV, LTO, Route Suitability: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A45#REF# FCT i NV, LTO, Route Suitability: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A51#REF# FCT j NV, LTO, Route Suitability: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A57#REF# FCT l NV, LTO, Route Suitability: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3506#REF# FCT m A.3.4.1m) effect on Route Suitability Data, MAR parameter
#TEST-VAL-SUB026-4E37#REF# FCT n NV, LTO, Route Suitability: A.3.4.1.2 n (the Limit of Authority becomes an End of Authority and the on-board considers an SvL)

#REQ-DESIGN-CR-0713#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Route Suitability Data shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3881#REF# FCT basic function Effect of closing desk during SoM on routeSuitability, plainTextMsg, and fixedTextMsg

#REQ-UNISIG-SUB026-3051:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Plain Text Information (not location based) shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3477#REF# FCT a A.3.4.1a) not location based plain/fixed text information
#TEST-VAL-SUB026-3479#REF# FCT b A.3.4.1b) not location based plain/fixed text information
#TEST-VAL-SUB026-3481#REF# FCT c A.3.4.1c) not location based plain/fixed text information
#TEST-VAL-SUB026-3483#REF# FCT d A.3.4.1d) not location based plain/fixed text information
#TEST-VAL-SUB026-3485#REF# FCT e A.3.4.1e) not location based plain/fixed text information
#TEST-VAL-SUB026-3533#REF# EET error expectation A.3.4.1m) effect on plain/fixed text and level transition order in SR
#TEST-VAL-SUB026-3487#REF# FCT f A.3.4.1f) not location based plain/fixed text information
#TEST-VAL-SUB026-3489#REF# FCT g A.3.4.1g) not location based plain/fixed text information
#TEST-VAL-SUB026-3491#REF# FCT h A.3.4.1h) not location based plain/fixed text information
#TEST-VAL-SUB026-3493#REF# FCT i A.3.4.1i) not location based plain/fixed text information
#TEST-VAL-SUB026-3495#REF# FCT j A.3.4.1j) not location based plain/fixed text information
#TEST-VAL-SUB026-3499#REF# FCT l A.3.4.1l) not location based plain/fixed text information
#TEST-VAL-SUB026-3501#REF# FCT m A.3.4.1m) not location based plain/fixed text information
#TEST-VAL-SUB026-4E41#REF# FCT n A.3.4.1n) not location based plain/fixed text information

#REQ-UNISIG-SUB026-2135:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Plain Text Information (location based) shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [8] shall be considered.
For the other situations condition [13] shall be considered.
#TEST-VAL-SUB026-3533#REF# EET CFX00038024 A.3.4.1m) effect on plain/fixed text and level transition order in SR
#TEST-VAL-SUB026-5205#REF# EET CFX00038097 A3.4.1.2m Deletion of location based text messages (without MA shortening)
#TEST-VAL-SUB026-5495#REF# EET CFX00039579 A3.4.1.2j Deletion of BMM and location based plain text (without MA shortening)
#TEST-VAL-SUB026-5497#REF# EET CFX00039579 A3.4.1.2g Deletion of BMM and location based plain text (without MA shortening)
#TEST-VAL-SUB026-3478#REF# FCT a A.3.4.1a) location based plain/fixed text information
#TEST-VAL-SUB026-3480#REF# FCT b A.3.4.1b) location based plain/fixed text information
#TEST-VAL-SUB026-3482#REF# FCT c A.3.4.1c) location based plain/fixed text information
#TEST-VAL-SUB026-3484#REF# FCT d A.3.4.1d) location based plain/fixed text information
#TEST-VAL-SUB026-3486#REF# FCT e A.3.4.1e) location based plain/fixed text information
#TEST-VAL-SUB026-3488#REF# FCT f A.3.4.1f) location based plain/fixed text information
#TEST-VAL-SUB026-3490#REF# FCT g A.3.4.1g) location based plain/fixed text information
#TEST-VAL-SUB026-3492#REF# FCT h A.3.4.1h) location based plain/fixed text information
#TEST-VAL-SUB026-3494#REF# FCT i A.3.4.1i) location based plain/fixed text information
#TEST-VAL-SUB026-3496#REF# FCT j A.3.4.1j) location based plain/fixed text information
#TEST-VAL-SUB026-3500#REF# FCT l A.3.4.1l) location based plain/fixed text information
#TEST-VAL-SUB026-3502#REF# FCT m A.3.4.1m) location based plain/fixed text information
#TEST-VAL-SUB026-4E40#REF# FCT n A.3.4.1n) location based plain/fixed text information

#REQ-DESIGN-CR-0714#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Plain Text Information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3498#REF# FCT location based A.3.4.1k) location based plain/fixed text information
#TEST-VAL-SUB026-3497#REF# FCT not location based A.3.4.1k) not location based plain/fixed text information

#REQ-UNISIG-SUB026-3052:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Fixed Text Information (not location based) shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3477#REF# FCT a A.3.4.1a) not location based plain/fixed text information
#TEST-VAL-SUB026-3479#REF# FCT b A.3.4.1b) not location based plain/fixed text information
#TEST-VAL-SUB026-3481#REF# FCT c A.3.4.1c) not location based plain/fixed text information
#TEST-VAL-SUB026-3483#REF# FCT d A.3.4.1d) not location based plain/fixed text information
#TEST-VAL-SUB026-3485#REF# FCT e A.3.4.1e) not location based plain/fixed text information
#TEST-VAL-SUB026-3533#REF# EET error expectation A.3.4.1m) effect on plain/fixed text and level transition order in SR
#TEST-VAL-SUB026-3487#REF# FCT f A.3.4.1f) not location based plain/fixed text information
#TEST-VAL-SUB026-3489#REF# FCT g A.3.4.1g) not location based plain/fixed text information
#TEST-VAL-SUB026-3491#REF# FCT h A.3.4.1h) not location based plain/fixed text information
#TEST-VAL-SUB026-3493#REF# FCT i A.3.4.1i) not location based plain/fixed text information
#TEST-VAL-SUB026-3495#REF# FCT j A.3.4.1j) not location based plain/fixed text information
#TEST-VAL-SUB026-3499#REF# FCT l A.3.4.1l) not location based plain/fixed text information
#TEST-VAL-SUB026-3501#REF# FCT m A.3.4.1m) not location based plain/fixed text information
#TEST-VAL-SUB026-4E41#REF# FCT n A.3.4.1n) not location based plain/fixed text information

#REQ-UNISIG-SUB026-2136:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Fixed Text Information (location based) shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [8] shall be considered.
For the other situations condition [13] shall be considered.
#TEST-VAL-SUB026-3533#REF# EET CFX00038024 A.3.4.1m) effect on plain/fixed text and level transition order in SR
#TEST-VAL-SUB026-5205#REF# EET CFX00038097 A3.4.1.2m Deletion of location based text messages (without MA shortening)
#TEST-VAL-SUB026-5496#REF# EET CFX00038097 A3.4.1.2j location based fixed text (without MA shortening)
#TEST-VAL-SUB026-5498#REF# EET CFX00038097 A3.4.1.2g Location based fixed text (without MA shortening)
#TEST-VAL-SUB026-3478#REF# FCT a A.3.4.1a) location based plain/fixed text information
#TEST-VAL-SUB026-3480#REF# FCT b A.3.4.1b) location based plain/fixed text information
#TEST-VAL-SUB026-3482#REF# FCT c A.3.4.1c) location based plain/fixed text information
#TEST-VAL-SUB026-3484#REF# FCT d A.3.4.1d) location based plain/fixed text information
#TEST-VAL-SUB026-3486#REF# FCT e A.3.4.1e) location based plain/fixed text information
#TEST-VAL-SUB026-3488#REF# FCT f A.3.4.1f) location based plain/fixed text information
#TEST-VAL-SUB026-3490#REF# FCT g A.3.4.1g) location based plain/fixed text information
#TEST-VAL-SUB026-3492#REF# FCT h A.3.4.1h) location based plain/fixed text information
#TEST-VAL-SUB026-3494#REF# FCT i A.3.4.1i) location based plain/fixed text information
#TEST-VAL-SUB026-3496#REF# FCT j A.3.4.1j) location based plain/fixed text information
#TEST-VAL-SUB026-3500#REF# FCT l A.3.4.1l) location based plain/fixed text information
#TEST-VAL-SUB026-3502#REF# FCT m A.3.4.1m) location based plain/fixed text information
#TEST-VAL-SUB026-4E40#REF# FCT n A.3.4.1n) location based plain/fixed text information

#REQ-DESIGN-CR-0715#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Fixed Text Information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3498#REF# FCT location based A.3.4.1k) location based plain/fixed text information
#TEST-VAL-SUB026-3497#REF# FCT not location based A.3.4.1k) not location based plain/fixed text information

#REQ-UNISIG-SUB026-3351:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Geographical Position shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A11#REF# FCT a Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3A15#REF# FCT b Linking, Reversing area/supervision, GeoPos A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A24#REF# FCT c Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A28#REF# FCT d Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A32#REF# FCT e Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A19#REF# FCT f Linking, Reversing area/supervision, GeoPos A.3.4.1.2 f (Request of Shorten MA)
#TEST-VAL-SUB026-3A36#REF# FCT g Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A40#REF# FCT h Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A44#REF# FCT i Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A50#REF# FCT j Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 j (train category)
#TEST-VAL-SUB026-3A56#REF# FCT l Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3504#REF# FCT m A.3.4.1m) effect on GeoPos, train location, PR parameter
#TEST-VAL-SUB026-4E36#REF# FCT n Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3352#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Geographical Position shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3878#REF# FCT basic function Effect of closing desk during SoM L1 on GeographicalPosition

#REQ-UNISIG-SUB026-2138:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
#REQ-DESIGN-CR-0729#REF#
#REQ-UNISIG-SUB026-010152#REF#
Mode Profile shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.

If the start location of the Mode Profile is beyond the new stop location, the acknowledgement window of the Mode Profile shall be deleted as
well.
condition[14] is not relevant for shortening the mode profile (see realization of condition [14])
#TEST-VAL-SUB026-3241#REF# FCT a MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# FCT b MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3243#REF# FCT c MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 c (shortened of MA due to section time-out)
#TEST-VAL-SUB026-3244#REF# FCT d MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3245#REF# FCT e MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-7829#REF# EET error expectation Level acknowledgement, mode acknowledgement then deletion of mode acknowledgement
#TEST-VAL-SUB026-3246#REF# FCT f MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 f (the Request of Shorten MA)
#TEST-VAL-SUB026-3247#REF# FCT g MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3248#REF# FCT h MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3249#REF# FCT i MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3250#REF# FCT j MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3301#REF# FCT l MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E44#REF# FCT m MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 m (inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill)
#TEST-VAL-SUB026-4E43#REF# FCT n MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0716#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Mode Profile shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
condition[5] is only a hint
#ANALYSE-VALUNISIG-4038#REF# FCT The considered situation cannot occur because acceptance of this information has led to exit from SoM procedure.

#REQ-UNISIG-SUB026-2139:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
#ANA-UNISIG-RBCHandover-0004:01#REF#
RBC Transition Order shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.

remark: the conditions means, that the RBC Transition Order is deleted only, when the RBC Transition border is beyond the defined stop location.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A48#REF# EET error expectation RBC transition order: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A49#REF# EET error expectation RBC transition order: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A54#REF# EET error expectation RBC transition order: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A55#REF# EET error expectation RBC transition order: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A60#REF# EET error expectation RBC transition order: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A52#REF# FCT j PR and MA req params, RBC transition order, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3513#REF# FCT m A.3.4.1m) effect on RBC transition order
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)
#TEST-VAL-SUB026-7185#REF# FCT remark - location check HO deleted, stored RBC ACC-RBC A.3.4 location check results in deletion of RBC/RBC Handover, max safe front end has passed RBC transition border
#TEST-VAL-SUB026-8231#REF# FCT remark - location check HO deleted, stored RBC HO-RBC A.3.4 location check results in deletion of RBC/RBC Handover, max safe front end has not passed RBC transition border
#TEST-VAL-SUB026-7186#REF# FCT remark - location check HO not deleted A.3.4 location check results in maintaining of RBC/RBC Handover

#REQ-DESIGN-CR-0717#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
RBC Transition Order shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3461#REF# EET CFX00036753 Effect of closing desk during SoM on RBC transitionOrder (one mobiles)
#TEST-VAL-SUB026-3879#REF# FCT basic function Effect of closing desk during SoM on NationalValues and RBC transitionOrder (two mobiles)

#REQ-UNISIG-SUB026-3353:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Radio infill area information shall be deleted n situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
RIU is'nt realized with Rel. 8.0

#REQ-UNISIG-SUB026-3182#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Radio infill area information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
UNISIG clarification:
this case cannot ocur - see realization
--- FINALISED ---
Radio infill area information is not accepted in mode SB (see table 4.8.4 - #REQ-UNISIG-SUB026-3556:01#REF#) and is deleted, when change to mode
SB (see table 4.10 - #REQ-UNISIG-SUB026-3145:02#REF#). Therefore the case "driver closes desk during SoM" is not relevant for this
information.

Bei Erhalt eines Unconditional Emergency Stops in SB wird sofort der Wechsel nach Train Trip ausgeführt => Der Fall UES vorhanden und Fahrer
riegelt in SB ab, kann nicht auftreten.
#ANALYSE-VALUNISIG-4075#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-UNISIG-SUB026-2141:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
EOLM information shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4E63#REF# FCT a, b, c, d, f A3.4.1.2 a, b, c, d, f - EOLM Information
#TEST-VAL-SUB026-4E64#REF# FCT e, h, j, n A3.4.1.2 e, h, j, n - EOLM Information
#TEST-VAL-SUB026-4E65#REF# FCT g, i, l, m A3.4.1.2 g, i, l, m - EOLM Information

#REQ-UNISIG-SUB026-3183:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
EOLM information shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4E66#REF# FCT basic function A3.4.1.2 k - EOLM Information

#REQ-UNISIG-SUB026-2142:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Track condition excluding big metal masses shall be reset in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
TEST APPROACH:
Track conditions are managed centrally by the module TC. The shortening is executed independent of the actual track condition. The test has to
include one example track condition only.
#TEST-VAL-SUB026-3241#REF# FCT a MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# FCT b MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3243#REF# FCT c MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 c (shortened of MA due to section time-out)
#TEST-VAL-SUB026-3244#REF# FCT d MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3245#REF# FCT e MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-8278#REF# EET error expectation Shortening of TC due to A.3.4.1.2m
#TEST-VAL-SUB026-3246#REF# FCT f MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 f (the Request of Shorten MA)
#TEST-VAL-SUB026-3247#REF# FCT g MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3248#REF# FCT h MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3249#REF# FCT i MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3250#REF# FCT j MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3301#REF# FCT l MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E44#REF# FCT m MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 m (inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill)
#TEST-VAL-SUB026-4E43#REF# FCT n MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3608#REF# table.A.3.4 #ANA-UNISIG-StoredInformation-0103:01#REF#
Für die track condition „Change of Traction System“ muss #REQ-UNISIG-SUB026-2142:02#REF# wie folgt umgesetzt werden:
1. R bedeutet Löschen der Information
2. Ein Löschen der track condition „Change of Traction System“ darf nur dann erfolgen, wenn der Wechselort noch nicht mit max safe front end
erreicht worden ist.
#TEST-VAL-SUB026-3845#REF# FCT 1 Track Condition Change of Traction System - A.3.4 Reset leads to deletion of change information
#TEST-VAL-SUB026-3846#REF# FCT 2 Track Condition Change of Traction System - A.3.4 Reset does not revert already executed change

#REQ-DESIGN-CR-0719#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Track Conditions excluding big metal masses shall be reset in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3884#REF# FCT basic function Effect of closing desk during SoM on LinkingInformation and TC excluding BMM

#REQ-UNISIG-SUB026-2143:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
#ANA-UNISIG-StoredInformation-0104#REF#
Track condition big metal masses shall be reset in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.

Exception: Track condition big metal masses shall not be reset in mode SHUNTING.
#TEST-VAL-SUB026-5900#REF# FCT a A3.4.1.2 a Track condition big metal masses
#TEST-VAL-SUB026-5901#REF# FCT b A3.4.1.2 b Track condition big metal masses
#TEST-VAL-SUB026-5902#REF# FCT c A3.4.1.2 c Track condition big metal masses
#TEST-VAL-SUB026-5903#REF# FCT d A3.4.1.2 d Track condition big metal masses
#TEST-VAL-SUB026-5904#REF# FCT e A3.4.1.2 e Track condition big metal masses
#TEST-VAL-SUB026-5914#REF# FCT exception for SH A3.4.1.2 g and m handling of Track condition big metal masses in SH
#TEST-VAL-SUB026-5905#REF# FCT f A3.4.1.2 f Track condition big metal masses
#TEST-VAL-SUB026-5906#REF# FCT g A3.4.1.2 g Track condition big metal masses
#TEST-VAL-SUB026-5907#REF# FCT h A3.4.1.2 h Track condition big metal masses
#TEST-VAL-SUB026-5908#REF# FCT i A3.4.1.2 i Track condition big metal masses
#TEST-VAL-SUB026-5909#REF# FCT j A3.4.1.2 j Track condition big metal masses
#TEST-VAL-SUB026-5911#REF# FCT l A3.4.1.2 l Track condition big metal masses
#TEST-VAL-SUB026-5912#REF# FCT m A3.4.1.2 m Track condition big metal masses
#TEST-VAL-SUB026-5913#REF# FCT n A3.4.1.2 n Track condition big metal masses

#REQ-DESIGN-CR-0720#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Track condition big metal masses shall be reset in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-5910#REF# FCT basic function A3.4.1.2 k Track condition big metal masses

#REQ-UNISIG-SUB026-3184:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Emergency Stops shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
TEST APPROACH:
The requirement has no relevance for condition A.3.4.1.2 b) and f) as a new authority is rejected if emergency stop(s) have been accepted and is
not yet revoked or deleted onboard. 

The requirement is not relevant for Unconditional Conditional Emergency Stop. 
The acceptance of Unconditional Conditional Emergency Stop leads to the transition to TR. 
UNISIG allows a transition from TR to SN/UN/NP/SF/IS were the UCES is deleted or not relevant and to PT. 
Condition a-f and n can not occur as no MA is on board. 
Condition g and m can not occur in PT.
Condition h, i and l can not occur as the appropriated function is neither active in TR nor PT. 
Condition j can not occur as the appropriated driver request is neither active in TR nor PT.
#TEST-VAL-SUB026-3A11#REF# FCT a Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3A24#REF# FCT c Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A28#REF# FCT d Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A32#REF# FCT e Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A36#REF# FCT g Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A40#REF# FCT h Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A44#REF# FCT i Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A50#REF# FCT j Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 j (train category)
#TEST-VAL-SUB026-3A56#REF# FCT l Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3517#REF# FCT m A.3.4.1m) effect on Conditional Emergency Stop
#TEST-VAL-SUB026-4E36#REF# FCT n Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3185#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Emergency Stops shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
UNISIG clarification:
this case cannot ocur - see realization
--- FINALISED ---
The Conditional Emergency Stop is not accepted in mode SB (see table 4.8.4 - #REQ-DESIGN-CR-0740:03#REF#) and is deleted, when change to mode SB
(see table 4.10 - #REQ-DESIGN-CR-0504:02#REF#).

When the train receives an Unconditional Emergency Stop in mode SB, train changes immediate to mode TRIP (see mode transition condition [20]).
Therefore the case "driver closes desk during SoM" is not relevant for this information.
#ANALYSE-VALUNISIG-4078#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-UNISIG-SUB026-3186:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Train Position shall remain unchangedin situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A52#REF# FCT j PR and MA req params, RBC transition order, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3504#REF# FCT m A.3.4.1m) effect on GeoPos, train location, PR parameter
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3187#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Train Position shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3900#REF# FCT basic function Validity of Memorised balise groups for special position report due to closing of desk during SoM

#REQ-UNISIG-SUB026-3188:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Train Data shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
TEST APPROACH:
Situation j has no relevance here because train category, axle load, loading gauge and traction system are part of train data.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3525#REF# FCT m A.3.4.1m) effect on Train Data, Driver ID, Radio Network ID, RBC ID/Phone Number, Train Running Number
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0722#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Train Data shall be revalidated in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3916#REF# FCT basic function Validity of Driver ID, Train Data and Train running number due to closing of desk during SoM

#REQ-UNISIG-SUB026-3189:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Adhesion factor shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A52#REF# FCT j PR and MA req params, RBC transition order, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3514#REF# FCT m A.3.4.1m) effect on ADHESIONFACTOR
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0723#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Adhesion factor shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3882#REF# FCT basic function Effect of closing desk during SoM on LvlTransitionOrder and AdhesionFactor

#REQ-UNISIG-SUB026-3190:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
ERTMS/ETCS level shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3241#REF# FCT a MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# FCT b MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3243#REF# FCT c MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 c (shortened of MA due to section time-out)
#TEST-VAL-SUB026-3244#REF# FCT d MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3245#REF# FCT e MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3246#REF# FCT f MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 f (the Request of Shorten MA)
#TEST-VAL-SUB026-3247#REF# FCT g MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3248#REF# FCT h MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3249#REF# FCT i MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3250#REF# FCT j MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 j (loading gauge)
#TEST-VAL-SUB026-3301#REF# FCT l MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E44#REF# FCT m MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 m (inconsistency in a balise group marked as linked and no linking is used onboard and the train is at standstill)
#TEST-VAL-SUB026-4E43#REF# FCT n MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3191#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
ERTMS/ETCS level shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3770#REF# FCT basic function ETCS level remains unchanged in situation A3.4.1.2 k

#REQ-DESIGN-CR-0764:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Table of priority of trackside supported levels shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3438#REF# FCT a, j table of priority - unchanged A.3.4.1.2 a) j)
#TEST-VAL-SUB026-3439#REF# FCT b, c, d, e table of priority - unchanged A.3.4.1.2 b-e)
#TEST-VAL-SUB026-3440#REF# FCT f, g table of priority - unchanged A.3.4.1.2 f, g
#TEST-VAL-SUB026-3441#REF# FCT h, l table of priority - unchanged A.3.4.1.2 h, l
#TEST-VAL-SUB026-3442#REF# FCT i table of priority - unchanged A.3.4.1.2 i
#TEST-VAL-SUB026-3526#REF# FCT m A.3.4.1m) effect on ERTMS/ETCS level and Table of priority of trackside supported levels
#TEST-VAL-SUB026-4E70#REF# FCT n table of priority - unchanged A.3.4.1.2 n

#REQ-DESIGN-CR-0765#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Table of priority of trackside supported levels shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3914#REF# FCT basic function Validity of Table of priority of trackside supported levels due to closing of desk during SoM

#REQ-UNISIG-SUB026-3192:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Driver ID shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A52#REF# FCT j PR and MA req params, RBC transition order, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3525#REF# FCT m A.3.4.1m) effect on Train Data, Driver ID, Radio Network ID, RBC ID/Phone Number, Train Running Number
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0724#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Driver ID shall be revalidated in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3916#REF# FCT basic function Validity of Driver ID, Train Data and Train running number due to closing of desk during SoM

#REQ-DESIGN-CR-0762:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Radio network ID shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3951#REF# FCT a, b Status of RadioNetworkId on occurance of ConditionalEmergencyStop and reception of Shortened MA
#TEST-VAL-SUB026-3979#REF# FCT c, d Status of RadioNetworkId on occurance of Section timeout and Overlap timeout
#TEST-VAL-SUB026-3980#REF# FCT e, f Status of RadioNetworkId on occurance of End section timeout and cooperative MA shortening
#TEST-VAL-SUB026-3981#REF# FCT g, h, l Handling of stored Radio Network id in various linking situations, e.G. second balise not in expectation window
#TEST-VAL-SUB026-3982#REF# FCT i, j Handling of stored Radio Network id in various situations (i,j,k)
#TEST-VAL-SUB026-3525#REF# FCT m A.3.4.1m) effect on Train Data, Driver ID, Radio Network ID, RBC ID/Phone Number, Train Running Number
#TEST-VAL-SUB026-4E62#REF# FCT n Status of RadioNetworkId on situation A3.4.1.3 (n)

#REQ-DESIGN-CR-0763#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Radio network ID shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3982#REF# FCT basic function Handling of stored Radio Network id in various situations (i,j,k)

#REQ-UNISIG-SUB026-3193:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
RBC ID/Phone Number shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A14#REF# FCT a GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 a (execution of CES)
#TEST-VAL-SUB026-3A18#REF# FCT b GP, RBC ID/phone numbers: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A27#REF# FCT c GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A31#REF# FCT d GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A35#REF# FCT e GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A23#REF# FCT f GP, RBC ID/phone numbers: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A39#REF# FCT g GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A43#REF# FCT h GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A47#REF# FCT i GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A53#REF# FCT j GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A59#REF# FCT l GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-4E38#REF# FCT m GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 m (linked BG inconsisistency and no linking is used onboard)
#TEST-VAL-SUB026-4E39#REF# FCT n GP, Signaling related speed restriction, RBC ID/phone numbers: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-UNISIG-SUB026-3194#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
RBC ID/Phone Number shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4213#REF# ECT basic function RBC contact information input possible during manual level transition to L2 - data memorized

#REQ-UNISIG-SUB026-3195:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Train Running Number shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A13#REF# FCT a PR and MA req params, RBC trans order, Train Data, DrvID, Train Pos, Adh Factor, Running No.: A.3.4.1.2 a (execution of a CES)
#TEST-VAL-SUB026-3A17#REF# FCT b PR and MA req params, RBC trans order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A26#REF# FCT c PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A30#REF# FCT d PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A34#REF# FCT e PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A22#REF# FCT f PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 f (Request to Shorten MA)
#TEST-VAL-SUB026-3A38#REF# FCT g PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A42#REF# FCT h PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A46#REF# FCT i PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A52#REF# FCT j PR and MA req params, RBC transition order, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 j (axle load changed)
#TEST-VAL-SUB026-3A58#REF# FCT l PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3525#REF# FCT m A.3.4.1m) effect on Train Data, Driver ID, Radio Network ID, RBC ID/Phone Number, Train Running Number
#TEST-VAL-SUB026-4E42#REF# FCT n PR and MA req params, RBC transition order, Train Data, DrvID, Train Loc, Adh Factor, Running No.: A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0725#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Train Running Number shall be revalidated in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3916#REF# FCT basic function Validity of Driver ID, Train Data and Train running number due to closing of desk during SoM

#REQ-UNISIG-SUB026-2153:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
#ANA-UNISIG-StoredInformation-0102#REF#
Reversing Area Information shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.

The new stop location shall be the new end of the reversing area.
unisig clarification:
It is necessary to ensure that the train front end is inside the shortened RV-Area - see analysis
#TEST-VAL-SUB026-3520#REF# EET CFX00038021 A.3.4.1m) effect on Reversing area information / Reversing supervision information - at new stop location
#TEST-VAL-SUB026-3A11#REF# FCT a Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3A15#REF# FCT b Linking, Reversing area/supervision, GeoPos A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A24#REF# FCT c Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A28#REF# FCT d Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A32#REF# FCT e Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A19#REF# FCT f Linking, Reversing area/supervision, GeoPos A.3.4.1.2 f (Request of Shorten MA)
#TEST-VAL-SUB026-3A36#REF# FCT g Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A40#REF# FCT h Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A44#REF# FCT i Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A50#REF# FCT j Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 j (train category)
#TEST-VAL-SUB026-3A56#REF# FCT l Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3519#REF# FCT m A.3.4.1m) effect on Reversing area information - beyond the new stop location
#TEST-VAL-SUB026-4E36#REF# FCT n Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0726#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Reversing Area Information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3880#REF# FCT basic function Effect of closing desk during SoM on reversingAreaInformation and reversingSupervisionInformation

#REQ-UNISIG-SUB026-3200:01#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Reversing Supervision Information shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-3A11#REF# FCT a Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3A15#REF# FCT b Linking, Reversing area/supervision, GeoPos A.3.4.1.2 b (reception of shortened MA)
#TEST-VAL-SUB026-3A24#REF# FCT c Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 c (MA shortened due to section time-out)
#TEST-VAL-SUB026-3A28#REF# FCT d Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 d (SvL is shifted due to an overlap time-out)
#TEST-VAL-SUB026-3A32#REF# FCT e Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 e (shortened of MA due to end section time-out)
#TEST-VAL-SUB026-3A19#REF# FCT f Linking, Reversing area/supervision, GeoPos A.3.4.1.2 f (Request of Shorten MA)
#TEST-VAL-SUB026-3A36#REF# FCT g Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 g (unlinked BG inconsisistency)
#TEST-VAL-SUB026-3A40#REF# FCT h Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 h (service brake due to linking reaction and standstill)
#TEST-VAL-SUB026-3A44#REF# FCT i Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 i (radio link supervision led to SB and stanstill)
#TEST-VAL-SUB026-3A50#REF# FCT j Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 j (train category)
#TEST-VAL-SUB026-3A56#REF# FCT l Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 l (service brake due to RAMS supervision and standstill)
#TEST-VAL-SUB026-3521#REF# FCT m A.3.4.1m) effect on Reversing supervision information - RV
#TEST-VAL-SUB026-4E36#REF# FCT n Cond Emergency Stop, Linking, Reversing area/supervision, GeoPos A.3.4.1.2 n (LoA becomes an EoA and the on-board considers an SvL)

#REQ-DESIGN-CR-0727#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Reversing Supervision Information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3880#REF# FCT basic function Effect of closing desk during SoM on reversingAreaInformation and reversingSupervisionInformation

#REQ-DESIGN-CR-0761:02#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Track Ahead Free Request shall remain unchanged iin situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4E67#REF# FCT a, b, c, d, f A3.4.1.2 a, b, c, d, f - TAF Request
#TEST-VAL-SUB026-4E68#REF# FCT e, h, j, n A3.4.1.2 e, h, j, n - TAF Request
#TEST-VAL-SUB026-4E69#REF# FCT g, i, l, m A3.4.1.2 g, i, l, m - TAF Request

#REQ-DESIGN-CR-0728#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Track Ahead Free Request shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM).
#TEST-VAL-SUB026-3988#REF# FCT basic function Handling of stored Track Ahead Free Request information in various situations

#REQ-UNISIG-SUB026-010165#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Level Crossing information shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-4E84#REF# FCT a, b, c, d, f A3.4.1.2 a, b, c, d, f - Level Crossing information
#TEST-VAL-SUB026-4E83#REF# FCT e, h, j, n A3.4.1.2 e, h, j, n - Level Crossing information
#TEST-VAL-SUB026-4E85#REF# FCT g, i, l, m A3.4.1.2 g, i, l, m - Level Crossing information

#REQ-UNISIG-SUB026-010166#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Level Crossing information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM).
#TEST-VAL-SUB026-7647#REF# FCT basic function Level crossing information deleted when mode changes to SB and when desk is closed during SoM

#REQ-UNISIG-SUB026-010137#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Permitted Braking Distance Information shall be deleted in situations A3.4.1.2 a-n (except for k).

For situations a-d, f and n condition [1] shall be considered.
For the other situations condition [10] shall be considered.
clarification:
if the new stop location fells together with a start point of a PBD, this  PBD is to delete.
#TEST-VAL-SUB026-3A79#REF# FCT a) PBD Information when executing a CES
#TEST-VAL-SUB026-3A80#REF# FCT b) PBD Information when receiveng a shotened MA
#TEST-VAL-SUB026-3A81#REF# FCT c) PBD Information when MA is shortened due to a section time-out
#TEST-VAL-SUB026-3A82#REF# FCT d) PBD Information when the SvL is shifted due to an overlap timeout
#TEST-VAL-SUB026-3A83#REF# FCT e) PBD Information when the stored MA is shortened due to an end section time-out
#TEST-VAL-SUB026-3A89#REF# EET error expectation PBD Information when train category is changed
#TEST-VAL-SUB026-3A90#REF# EET error expectation PBD Information when loading gauge is changed
#TEST-VAL-SUB026-3A91#REF# EET error expectation PBD Information when traction system is changed
#TEST-VAL-SUB026-3A84#REF# FCT f) PBD Information when a cooperative MA revocation is granted by the onboard
#TEST-VAL-SUB026-3A85#REF# FCT g) PBD Information when passing an unlinked BG and inconsistency is detected
#TEST-VAL-SUB026-3A86#REF# FCT h) PBD Information when a linking reaction leads to a SB
#TEST-VAL-SUB026-3A87#REF# FCT i) PBD Information when supervision of safe radio connection led to a SB
#TEST-VAL-SUB026-3A88#REF# FCT j) PBD Information when axle load is changed
#TEST-VAL-SUB026-3A92#REF# FCT l) PBD Information when RAMS related supervision functions led to a SB
#TEST-VAL-SUB026-3A93#REF# FCT m) PBD Information when passing a BG marked as linked and inconsistency is detected
#TEST-VAL-SUB026-3A94#REF# FCT n) PBD Information when LoA becomes EoA and On-board considers an SvL

#REQ-UNISIG-SUB026-010138#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Permitted Braking Distance Information shall be deleted in situation A3.4.1.2 k (driver closes desk during SoM)
#TEST-VAL-SUB026-3A95#REF# FCT basic function PBD Information when driver closes desk during SoM

#REQ-UNISIG-SUB026-010167#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
RBC/RIU System Version shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
TEST APPROACH:
RIU is not part of R8 the appropriated test aspect is hence omitted
#TEST-VAL-SUB026-4E71#REF# FCT RBC - a, b, c, d, f A3.4.1.2 a, b, c, d, f - RBC system version
#TEST-VAL-SUB026-4E72#REF# FCT RBC - e, h, j, n A3.4.1.2 e, h, j, n - RBC system version
#TEST-VAL-SUB026-4E73#REF# FCT RBC - g, i, l, m A3.4.1.2 g, i, l, m - RBC system version

#REQ-UNISIG-SUB026-010168#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
RBC/RIU System Version shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
TEST APPROACH:
RIU is not part of R8 the appropriated test aspect is hence omitted
#TEST-VAL-SUB026-4E74#REF# FCT basic function A.3.4.1k) RBC system version

#REQ-UNISIG-SUB026-010169#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Operated System Version shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-7124#REF# FCT a, b, c, d, f A3.4.1.2 a, b, c, d, f - Operated System Version
#TEST-VAL-SUB026-7125#REF# FCT e, h, j, n A3.4.1.2 e, h, j, n - Operated System Version
#TEST-VAL-SUB026-7126#REF# FCT g, i, l, m A3.4.1.2 g, i, l, m - Operated System Version

#REQ-UNISIG-SUB026-010170#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Operated System Version shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-7127#REF# FCT basic function A3.4.1.2 k - Operated System Version

#REQ-UNISIG-SUB026-010171#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Language used to display information to the driver shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#ANALYSE-VALUNISIG-4790#REF# FCT The language setting is realised by the DMI refer #REQ-SAS_DMI-000561#REF#, #REQ-SAS_DMI-000563#REF# and #REQ-SAS_DMI-000565#REF#. The application software is hence not affected by this requirement. The verification has to take place on the system level.

#REQ-UNISIG-SUB026-010172#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Language used to display information to the driver shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#ANALYSE-VALUNISIG-4791#REF# FCT The language setting is realised by the DMI refer #REQ-SAS_DMI-000561#REF#, #REQ-SAS_DMI-000563#REF# and #REQ-SAS_DMI-000565#REF#. The application software is hence not affected by this requirement. The verification has to take place on the system level.

#REQ-UNISIG-SUB026-010163#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Virtual Balise Covers shall remain unchanged in situations A3.4.1.2 a-n (except for k).

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-7850#REF# FCT a, b, c, d, f A3.4.1.2 a, b, c, d, f - VBC Information
#TEST-VAL-SUB026-7851#REF# FCT e, h, j, n A3.4.1.2 e, h, j, n - VBC information
#TEST-VAL-SUB026-7852#REF# FCT g, i, l, m A3.4.1.2 g, i, k, l, m - VBC Information

#REQ-UNISIG-SUB026-010164#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
Virtual Balise Covers Levels shall remain unchanged in situation A3.4.1.2 k (driver closes desk during SoM)

--- FINALISED ---
Alle Spalteneinträge in A3.4 mit Einstufung "unchanged" bedingen keine Funktionalität in der ASW und werden deshalb bereits auf dieser
Ebene auf REAL gesetzt.
#TEST-VAL-SUB026-7852#REF# FCT basic function A3.4.1.2 g, i, k, l, m - VBC Information

#REQ-UNISIG-SUB026-2210#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [1]:
beyond the new SvL or in case of situation a, beyond the stop location of the accepted CES
#TEST-VAL-SUB026-3241#REF# ECT beyond CES location MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 a (the execution of a CES)
#TEST-VAL-SUB026-3242#REF# ECT beyond new SvL MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 b (reception of shortened MA)

#REQ-UNISIG-SUB026-3205#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [2]:
The considered situations cannot occur when a list of balises to be used in SR is available onboard. Indeed, the onboard is in SR mode and since
no MA or track description are stored onboard, no new SvL may be defined.
keine Anforderung => kann bei der Auswertung der Tabelle ignoriert werden
--- FINALISED ---
Die conditions [2], [4], [5] und [6] stellen lediglich Erläuterungen dar. Sie führen zu keiner neuen/geänderten Funktionalität.
#ANALYSE-VALUNISIG-4081#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-UNISIG-SUB026-010151#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [3]:
In case of reception of a new non-infill MA (situation b or f), the stored MA is fully replaced with the new one. In case of reception of a new
infill MA (situation b), the stored MA is replaced beyond the infill location reference, i.e. the balise group at the next main signal
is conformed with 3.8.5.1
realised by: #REQ-UNISIG-SUB026-0037#REF#

#REQ-UNISIG-SUB026-010153#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [4]: The considered situations a-d, f, h, i cannot occur when the default gradient for a TSR is used on-board.

--- FINALISED ---
Die conditions [2], [4], [5] und [6] stellen lediglich Erläuterungen dar. Sie führen zu keiner neuen/geänderten Funktionalität.
#ANALYSE-VALUNISIG-4792#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-UNISIG-SUB026-3202#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [5]:
The considered situation cannot occur because acceptance of this information has led to exit from SoM procedure.

--- FINALISED ---
Die conditions [2], [4], [5] und [6] stellen lediglich Erläuterungen dar. Sie führen zu keiner neuen/geänderten Funktionalität.
#ANALYSE-VALUNISIG-4083#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-UNISIG-SUB026-3203#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [6]:
The considered situations b-f cannot occur when a TAF request is stored on-board

--- FINALISED ---
Die conditions [2], [4], [5] und [6] stellen lediglich Erläuterungen dar. Sie führen zu keiner neuen/geänderten Funktionalität.
#ANALYSE-VALUNISIG-4084#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-DESIGN-CR-0729#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [7]:
If the start location of the Mode Profile is beyond the new SvL, the acknowledgement window of the Mode Profile shall be deleted as well.
realised by: #REQ-UNISIG-SUB026-2138:02#REF#

#REQ-UNISIG-SUB026-3053#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [8]:
only if the location where to start to display the text is beyond the new stop location; otherwise all the text information (i.e. including end
location where to stop display, if any) shall remain unchanged.
#TEST-VAL-SUB026-3478#REF# ECT basic function A.3.4.1a) location based plain/fixed text information

#REQ-UNISIG-SUB026-3204#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [9]:
unchanged if the onboard is in SH mode
realised by: #REQ-UNISIG-SUB026-2128:02#REF#

#REQ-UNISIG-SUB026-010154#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [10]:
beyond the current max safe front end position of the train
#TEST-VAL-SUB026-3247#REF# ECT basic function MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)

#REQ-UNISIG-SUB026-010155#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [11]:
the ERTMS/ETCS on-board equipment shall consider the current estimated front end and max safe front end positions of the train, as the EOA and
SvL respectively, with no release speed
#TEST-VAL-SUB026-3247#REF# ECT basic function MA, SSP, ASP, TSR, MP, TC excluding BMM: A.3.4.1.2 g (unlinked BG inconsisistency)

#REQ-UNISIG-SUB026-010152#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [12]:
If the start location of the Mode Profile is beyond the current max safe front end, the acknowledgement window of the Mode Profile shall be
deleted as well
realised by: #REQ-UNISIG-SUB026-2138:02#REF#

#REQ-UNISIG-SUB026-010156#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [13]:
only if the location where to start to display the text is beyond the current max safe front end; otherwise all the text information (i.e.
including end location where to stop display, if any) shall remain unchanged
#TEST-VAL-SUB026-3490#REF# ECT basic function A.3.4.1g) location based plain/fixed text information

#REQ-UNISIG-SUB026-010157#REF# table.A.3.4 #REQ-UNISIG-SUB026-3170:01#REF#
condition [14]:
In case of reception of a new non-infill MA with or without Mode Profile (situation b or f), the stored Mode Profile is deleted. In case of
reception of a new infill MA (situation b), the stored Mode Profile is deleted only beyond the infill location reference, i.e. the balise group
at the next main signal
is conformed with 3.12.4.3 and 3.12.4.3.1
realised by: #REQ-UNISIG-SUB026-0580#REF#
realised by: #REQ-UNISIG-SUB026-3563#REF#

#REQ-UNISIG-SUB026-3004:01#REF# A.3.5.1
A.3.5.1 Regards actions executed in reference to location information received from trackside, the on-board equipment shall ensure that the
action related to a location is neither reverted, nor executed twice. Situations to be considered shall include reverse movement (initiated by
driver or due to roll-away) and the sub-sequent forward movement, or adjustment of train position on passing a new LRBG. This rule shall apply
to the following actions:
  Change of National Values (see 3.18.2)
  Request to acknowledge new level, level transition (see SRS chapter 5.10)
  Start and stop displaying plain or fixed text messages (see 3.12.3)
  Request to acknowledge a mode profile, mode transition due to mode profile (see 3.12.4)
  Start and stop accepting radio infill information (see 3.9.3)
  Actions related to RBC/RBC handover (see 3.15.1)
  Actions related to track condition information (see 3.12.1) with the exception of big metal masses
  Permission to initiate Reversing mode, i.e., limits of Reversing Area (see 3.15.4)
  Start and stop Track Ahead free request to driver (see 3.15.5)”
  Start and stop calculation of geographical position (see 3.6.6)

--- FINALISED ---
In A.3.6.2 wird benannt, welche Informationen beim Rücksetzen zu berücksichtigen sind. Mit dieser Festlegung werden alle nicht genannten
Informationen ausgeschlossen. Somit kann diese Anforderung mit Umsetzung A.3.6.2 auf dieser Ebene als realisiert eingestuft werden.
#ANALYSE-VALUNISIG-4793#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-UNISIG-SUB026-010370#REF# A.3.5.2
A.3.5.2
Once the ERTMS/ETCS on-board equipment has received a balise group message (i.e. once it has received the last balise telegram of the balise
group), the action(s) resulting from its content shall take into account the train position measured at the time of reception of this last
telegram and shall take precedence on any other action related to a further location that is reached before the message has been fully
processed.
TEST APPROACH:
For the verification of this requirement, the two scenarios described in SUB026 will be implemented:
1) Example 1 - A.3.5.2.1
2) Example 2 - A.3.5.2.2
#TEST-VAL-SUB026-7678#REF# FCT 1 Evaluation of train location at the time of balise telegram reception - Example 1
#TEST-VAL-SUB026-7674#REF# FCT 2 Evaluation of train location at the time of balise telegram reception - Example 2

#REQ-UNISIG-SUB026-3747#REF# A.3.6.1.1
A.3.6.1.1	When the train moves in the direction of its train orientation, storage capacity occupied by trackside information no longer
used, i.e., the related on-board functionality has been completed, shall be made available immediately.
realised by: #REQ-UNISIG-SUB026-3005:02#REF#

#REQ-UNISIG-SUB026-3005:02#REF# A3.6.1.1 #REQ-UNISIG-SUB026-3747#REF#
#ANA-UNISIG-CR0798-0007:01#REF#
When the train moves in the direction of its train orientation, storage capacity occupied by trackside information no longer used, i.e., the
related on-board functionality has been completed, shall be made available immediately.

Exception: For informations SSP, GAP, ASP, TSR, LX, PBD, adhesion factor from trackside and track condition big metal masses shall be applied
the A3.6.2.
TEST APPROACH:
The aim of the requirement is to allow the trackside to predict the storage capacity available on-board in order to comply with the dimensioning
rules regarding information stored on-board given in Subset 040 based on the train location. 
It has to be assured that new information are accepted/processed accordingly. 
SUBSET-40 4.3.2 
a) Number of MA sections (excluding the End Section)
b) Number of balise IDs in balise list for SR authority or for shunting mode
c) Number of mode profile sections
d) Number of locations with changes of SSP
e) Number of TSR 
f) Number of changes of gradient
g) Number of locations for position reports
h) Number of text messages
i) Number of linked balise groups
j) Number of Track Conditions Change of traction system
k) Number of Track Conditions Big Metal masses
l) Number of Track Conditions
m) Number of Route suitability data
n) -
o) Number of Axle load speed profile segments
p) Number of Axle load speed restriction values per ASP segment
q) Number of adhesion profiles
r) Number of reversing area
s) Number of Permitted Braking Distance Speed Restrictions
t) Number of Track Conditions Station Platforms
u) Number of Track Conditions Allowed Current Consumption
v) Number of Level Crossings
w) Number of Virtual Balise Covers set by trackside
x) Size of packet 44 with NID_XUSER = 102

The information a, c, g, i, j, m, r and s are not relevant as the stored information is overridden by new information. 
The information b, p, w and x are not relevant as they are not location based.
The information t and u are not relevant as they are not stored on-board.
The information d, e, f, k, o, q, s and v are covered by the exception.
For the information h and l it has to be verified that new information exceeding the dimension rules (together with the former stored
information but passed information) are processed properly.

Furthermore it has to be ensured that actions executed in reference to location information received from trackside are neither reverted, nor
executed twice (#REQ-UNISIG-SUB026-3004:01#REF#).
SUBSET-26 A.3.4
I) National Values 
II) Not yet applicable National Values 
III) Linking
IV) Movement Authority 
V) Gradient Profile 
VI) International SSP 
VII) Axle load speed profile 
VIII) STM max speed 
IX) STM system speed/distance 
X) Level Transition Order 
XI) Stop Shunting on desk opening 
XII) List of balises for SH area 
XIII) MA Request Parameters
XIV) Position Report parameters 
XV) List of Balises in SR Authority + SR mode speed limit and distance 
XVI) Temporary Speed Restrictions 
XVII) Inhibition of revocable TSRs from balises in L2/3 
XVIII) Default Gradient for TSR 
XIX) Signalling related Speed Restriction 
XX) Route Suitability Data 
XXI) Plain Text Information (location based) 
XXII) Plain Text Information (not location based) 
XXIII) Fixed Text Information (location based) 
XXIV) Fixed Text Information (not location based) 
XXV) Geographical Position 
XXVI) Mode Profile 
XXVII) RBC Transition Order 
XXVIII) Radio Infill Area information 
XXIX) EOLM information 
XXX) Track Conditions excluding big metal masses
XXX.I) TC change of traction system
XXX.II) TC change of allowed power consumption
XXX.III) TC (packet 68)
XXX.IV) TC station platforms
XXXI) Track condition big metal masses 
XXXII) Unconditional Emergency Stop
XXXIII) Conditional Emergency Stop
XXXIV) Train Position
XXXV) Train Data
XXXVI) Adhesion factor 
XXXVII) ERTMS/ETCS level
XXXVIII) Table of priority of trackside supported levels 
XXXIX) Driver ID
XL) Radio Network ID
XLI) RBC ID/Phone Number 
XLII) Train Running Number
XLIII) Reversing Area Information 
XLIV) Reversing Supervision Information
XLV) Track Ahead Free Request 
XLVI) Level Crossing information 
XLVII) Permitted Braking Distance Information
XLVIII) RBC/RIU System Version
XLIX) Operated System Version
L) Language used to display information to the driver
LI) Virtual Balise Covers

The information XI, XII, XIII, XV, XVII, XVIII, XIX, XXII, XXIV, XXIX, XXXII, XL, XLI, XLII, XLVIII and LI are not relevant as they are not
location based.
The information IV, XX, XXXIII and XLIV are not relevant as the location can' t be passed.
The information XXVIII and XXX.IV are not relevant as the function is not part of R8.
The information V, VI, VII, XVI, XXXI, XXXVI, XLVI, XLVII are covered by the exception.
The information VIII, IX, XXXIV, XXXV, XXXVII, XXXIX, XLIX, L are not relevant as they are not trackside information.
The information XXXVIII is part of the level transition order and not separate information.
The information II is part of the national values and not separate information.
The verification has to take place for information I, III, X, XIV, XXI, XXIII, XXV, XXVI, XXVII, XXX.I, XXX.II, XXX.III, XLIII and XLV.

Hence, the following aspects remain to be tested:
1) acceptance of new information
1.1) location based text messages
1.2) track condition (packet 68)
2) information neither reverted, nor executed twice
2.1) National values
2.2) Linking
2.3) Level transition order
2.4) Position report parameters
2.5) Plain text information (location based)
2.6) Fixed text information (location based)
2.7) Geographical position
2.8) Mode profile
2.9) RBC transition order
2.10) TC change of traction system 
2.11) TC change of allowed current consumption
2.12) TC (packet 68) 
2.13) Reversing area information
2.14) Track ahead free request
#TEST-VAL-SUB026-7848#REF# FCT 1.1 Storage capacity handling when new text messages are received
#TEST-VAL-SUB040-0039#REF# FCT 1.2 A system failure occurs when the max number of Track Conditions (pkt 68) stored on board is exceeded
#TEST-VAL-SUB026-4B09#REF# FCT 2.1, 2.3 Level Transition Order not executed twice, NV not switched back
#TEST-VAL-SUB026-7849#REF# FCT 2.2 Information neither reverted, nor executed twice - Linking
#TEST-VAL-SUB026-5282#REF# FCT 2.4 Position report parameters with specific locations, part of the indicated locations already passed
#TEST-VAL-SUB026-3A00#REF# FCT 2.5, 2.6 Start and stop displaying fixed text messages is neither reverted, nor executed twice.
#TEST-VAL-SUB026-3A02#REF# FCT 2.7 Actions related to Start and stop calculation of geographical position is neither reverted, nor executed twice
#TEST-VAL-SUB026-4B12#REF# FCT 2.8 Mode Profile not executed twice
#TEST-VAL-SUB026-4B10#REF# FCT 2.9 RBC HO not executed twice
#TEST-VAL-SUB026-3A10#REF# FCT 2.10 Actions related to Track Condition Change of Traction system is neither reverted, nor executed twice
#TEST-VAL-SUB026-7731#REF# FCT 2.11 Acceptance of TC 'Allowed power consumption' - RBC/L2
#TEST-VAL-SUB026-3A01#REF# FCT 2.12 Actions related to track condition information (except big metal masses) is neither reverted, nor executed twice
#TEST-VAL-SUB026-4B14#REF# FCT 2.13 Reversing area not considered twice
#TEST-VAL-SUB026-4B15#REF# FCT 2.14 TAF request not considered twice
#TEST-VAL-SUB026-4B13#REF# EET error expectation Level Transition Order not reverted

#REQ-UNISIG-SUB026-3006:01#REF# A.3.6.2.1
A.3.6.2.1	Following information shall remain stored on-board for a distance defined by a fixed value in rear of the min safe rear end
position of the train:
  location dependent static speed restrictions , i.e., SSP, ASP, TSR, LX SR, PBD SR (see 3.11.2.2)
  gradient information,
  reduced adhesion information received from trackside,
  Track condition “Big metal masses”.
realised by: #REQ-UNISIG-SUB026-3260:02#REF#
realised by: #REQ-UNISIG-SUB026-3264#REF#
realised by: #REQ-UNISIG-SUB026-010486#REF#
realised by: #REQ-UNISIG-SUB026-3268#REF#
realised by: #REQ-UNISIG-SUB026-010549#REF#
realised by: #REQ-UNISIG-SUB026-3272:01#REF#
realised by: #REQ-UNISIG-SUB026-3274#REF#
realised by: #REQ-UNISIG-SUB026-3275#REF#
realised by: #REQ-UNISIG-SUB026-3276:01#REF#

#REQ-UNISIG-SUB026-3260:02#REF# A3.6.2.1 #REQ-UNISIG-SUB026-3006:01#REF#
#REQ-UNISIG-SUB026-3007#REF#
#ANA-UNISIG-CR0798-0001:03#REF#
SPP and GP shall remain stored on-board for a distance defined by a fixed value in rear of the min safe rear end position of the train.
#TEST-VAL-SUB026-7087#REF# FCT GP Deletion of accepted and stored information when used GP
#TEST-VAL-SUB026-7086#REF# FCT SSP Deletion of accepted and stored information when used SSP

#REQ-UNISIG-SUB026-3261#REF# A3.6.2.1 #ANA-UNISIG-CR0798-0006#REF#
Die Einschränkung gemäß #REQ-UNISIG-SUB026-3260:02#REF# gilt nicht, wenn das gesamte SSP- bzw. GA-Profil zu löschen ist, z.B. bei einem
Modewechsel.
#TEST-VAL-SUB026-7088#REF# FCT basic function Deletion of information stored on-board backward movemetn SP/GP

#REQ-UNISIG-SUB026-3264#REF# A3.6.2.1 #REQ-UNISIG-SUB026-3006:01#REF#
#REQ-UNISIG-SUB026-3007#REF#
#ANA-UNISIG-CR0798-0002:01#REF#
Ein in Fahrtrichtung „Vorwärts“ verlassenes ASP-Profilelement ist erst mit Erreichen mit min safe rear end einer durch einen fixed Value
vorgegebenen Distanz des Profilelementendes zu löschen.
#TEST-VAL-SUB026-3800#REF# FCT basic function Storage of ASP Q_FRONT=0 and track side adhesion factor for backward movement
#TEST-VAL-SUB026-3801#REF# EET error expectation Storage of ASP Q_FRONT=0 and track side adhesion factor for backward movement (V_AXLELOAD1>V_AXLELOAD2)

#REQ-UNISIG-SUB026-3265#REF# A3.6.2.1 #ANA-UNISIG-CR0798-0006#REF#
Die Einschränkung gemäß #REQ-UNISIG-SUB026-3264#REF# gilt nicht, wenn das gesamte ASP-Profil zu löschen ist, z.B. bei einem Modewechsel.
#TEST-VAL-SUB026-3804#REF# FCT basic function Deletion of stored (fixed distance to keep information on-board) TSR/ASP

#REQ-UNISIG-SUB026-010486#REF# A3.6.2.1 #REQ-UNISIG-SUB026-3006:01#REF#
#REQ-UNISIG-SUB026-3007#REF#
#ANA-UNISIG-CR0798-0008#REF#
Ein in Fahrtrichtung „Vorwärts“ verlassenes PBD-Profilelement ist erst mit Erreichen mit min safe rear end einer durch einen fixed Value
vorgegebenen Distanz des Profilelementendes zu löschen.
#TEST-VAL-SUB026-7701#REF# FCT basic function Fixed distance to keep PBD Information stored onboard

#REQ-UNISIG-SUB026-010487#REF# A3.6.2.1 #ANA-UNISIG-CR0798-0006#REF#
Die Einschränkung gemäß #REQ-UNISIG-SUB026-010486#REF# gilt nicht, wenn das gesamte PBD-Profil zu löschen ist, z.B. bei einem Modewechsel.
#TEST-VAL-SUB026-3A75#REF# FCT basic function PBD Information deleted when changing mode to SB and SN

#REQ-UNISIG-SUB026-3268#REF# A3.6.2.1 #REQ-UNISIG-SUB026-3006:01#REF#
#REQ-UNISIG-SUB026-3007#REF#
#ANA-UNISIG-CR0798-0003:01#REF#
Eine in Fahrtrichtung „Vorwärts“ verlassene Temporary Speed Restriction ist erst mit Erreichen mit min safe rear end einer durch einen fixed
Value vorgegebenen Distanz zum Ende der TSR zu löschen.
TEST APPROACH:
The following aspects have been identified:
1) Q_FRONT = 0 (train length delay)
2) Q_FRONT = 1 (no train length delay)
#TEST-VAL-SUB026-3802#REF# FCT 1 Storage of TSR for backward movement Q_FRONT=1
#TEST-VAL-SUB026-3786#REF# FCT 2 , CFX00039206 Storage of TSR for backward movement Q_FRONT=0

#REQ-UNISIG-SUB026-3269#REF# A3.6.2.1 #ANA-UNISIG-CR0798-0003:01#REF#
#ANA-UNISIG-CR0798-0006#REF#
Die Einschränkung gemäß #REQ-UNISIG-SUB026-3268#REF# gilt nicht, wenn
- die TSR mit einem Revocation zurückgenommen wurde
- die TSR generell wegen eines Modewechsels etc. zu löschen ist.
TEST APPROACH:
The following aspects have been identified:
1) TSR revocation
2) mode change
#TEST-VAL-SUB026-3804#REF# FCT 1 Deletion of stored (fixed distance to keep information on-board) TSR/ASP
#TEST-VAL-SUB026-3803#REF# FCT 2 Stored (fixed distance to keep information on-board) slippery area and TSR deleted due to mode change

#REQ-UNISIG-SUB026-010549#REF# A3.6.2.1 #REQ-UNISIG-SUB026-3006:01#REF#
#REQ-UNISIG-SUB026-3007#REF#
#ANA-UNISIG-CR0798-0009#REF#
Eine in Fahrtrichtung „Vorwärts“ verlassene "non protected" LX Information ist erst mit Erreichen mit min safe rear end einer durch
einen fixed Value vorgegebenen Distanz zum Ende der LX Information zu löschen.
#TEST-VAL-SUB026-7658#REF# FCT basic function Storage of LX not protected information in rear of the train, receive LX protected information

#REQ-UNISIG-SUB026-010501#REF# to.A3.6.2.1 #ANA-UNISIG-LevelCrossing-0003#REF#
If the start location of a LX is no longer supervised and the train moves back over the start location, only the LX speed shall be supervised
furthermore.

The start location of the new LX information shall not be supervised again.
UNISIG clarification:
a recurrence of supervision the start location, especailly with EoA/SvL isn't desired.
TEST APPROACH:
The following aspects were identified:
1) LX not protected with stop required
2) LX not protected without stop required
#TEST-VAL-SUB026-7663#REF# FCT 1, 2 Supervision of LX information in rear of the train

#REQ-UNISIG-SUB026-010550#REF# A3.6.2.1 #ANA-UNISIG-CR0798-0009#REF#
#ANA-UNISIG-CR0798-0006#REF#
Die Einschränkung gemäß #REQ-UNISIG-SUB026-010549#REF# gilt nicht, wenn
- die "non protected" LX Information mit Empfang einer "protected" LX Information zurückgenommen wurde
- die "non protected" LX Information generell wegen eines Modewechsels etc. zu löschen ist.
TEST APPROACH:
The following aspects were identified:
1) receive protected LX information
2) enter a mode where LX information is deleted
#TEST-VAL-SUB026-7658#REF# FCT 1 Storage of LX not protected information in rear of the train, receive LX protected information
#TEST-VAL-SUB026-7659#REF# FCT 2 Storage of LX not protected information in rear of the train, transition to mode where LX information is deleted

#REQ-UNISIG-SUB026-3272:01#REF# A3.6.2.1 #REQ-UNISIG-SUB026-3006:01#REF#
#REQ-UNISIG-SUB026-3007#REF#
#ANA-UNISIG-CR0798-0004:02#REF#
Bei Erhalt eines neuen streckenseitigen Adhesionsfaktors sind alle aktuell vorhandenen Bereiche, die hinter der durch den fixed Value
vorgegebenen Distanz nach dem sicheren Zugende definierten Ort liegen, zu löschen.
#TEST-VAL-SUB026-3809#REF# EET error expectation Storage of Adhesion factor for fixed distance
#TEST-VAL-SUB026-3800#REF# FCT limit not passed Storage of ASP Q_FRONT=0 and track side adhesion factor for backward movement
#TEST-VAL-SUB026-3801#REF# FCT limit passed Storage of ASP Q_FRONT=0 and track side adhesion factor for backward movement (V_AXLELOAD1>V_AXLELOAD2)

#REQ-UNISIG-SUB026-3273#REF# A3.6.2.1 #ANA-UNISIG-CR0798-0006#REF#
Die Einschränkung gemäß #REQ-UNISIG-SUB026-3272:01#REF# gilt nicht, wenn der streckenseitige Adhesionsfaktor als solches zu löschen ist, z.B.
bei einem Modewechsel.
#TEST-VAL-SUB026-3803#REF# FCT basic function Stored (fixed distance to keep information on-board) slippery area and TSR deleted due to mode change

#REQ-UNISIG-SUB026-3274#REF# A3.6.2.1 #REQ-DESIGN-CR-0505#REF#
#REQ-UNISIG-SUB026-3006:01#REF#
#ANA-UNISIG-CR0798-0005:01#REF#
Eine Track Condition BMM muss berücksichtigt werden, wenn
- die untere Bereichsgrenze mit max safe antenna position
- die obere Bereichsgrenze mit min safe antenna position
befahren wird.
- die untere Bereichs-grenze ist die kleinere Position der beiden Bereichsenden
- die obere Bereichsgrenze ist die größere Position der beiden Bereichsenden
TEST APPROACH:
The following aspects have been identified:
1) handling with ELBE5A
2) handling with ELBE5K
#TEST-VAL-SUB026-3787#REF# FCT 1 Storage of BMM information for fixed distance
#TEST-VAL-SUB026-8140#REF# FCT 2, lower area border BMM supervision (with ELBE5K) - end point
#TEST-VAL-SUB026-8141#REF# FCT 2, upper area border BMM supervision (with ELBE5K) - start point
#TEST-VAL-SUB026-3358#REF# EET error expectation BMM area supervision in SR Modus Level 1 (P67 from BG with Q_LINK=0)
#TEST-VAL-SUB026-3810#REF# EET error expectation Storage of BMM information for fixed distance - in SH

#REQ-UNISIG-SUB026-3275#REF# A3.6.2.1 #REQ-DESIGN-CR-0505#REF#
#REQ-UNISIG-SUB026-3006:01#REF#
#ANA-UNISIG-CR0798-0005:01#REF#
Eine Track Condition BMM ist nicht mehr zu berücksichtigen, wenn
- die untere Bereichsgrenze mit max safe antenna position
- die obere Bereichsgrenze mit min safe antenna position
verlassen wird.
- die untere Bereichs-grenze ist die kleinere Position der beiden Bereichsenden
- die obere Bereichsgrenze ist die größere Position der beiden Bereichsenden
TEST APPROACH:
The following aspects have been identified:
1) handling with ELBE5A
2) handling with ELBE5K
#TEST-VAL-SUB026-3787#REF# FCT 1 Storage of BMM information for fixed distance
#TEST-VAL-SUB026-8141#REF# FCT 2, lower area border BMM supervision (with ELBE5K) - start point
#TEST-VAL-SUB026-8140#REF# FCT 2, upper area border BMM supervision (with ELBE5K) - end point
#TEST-VAL-SUB026-3358#REF# EET error expectation BMM area supervision in SR Modus Level 1 (P67 from BG with Q_LINK=0)
#TEST-VAL-SUB026-3810#REF# EET error expectation Storage of BMM information for fixed distance - in SH

#REQ-UNISIG-SUB026-3276:01#REF# A3.6.2.1 #REQ-UNISIG-SUB026-3006:01#REF#
#REQ-UNISIG-SUB026-3007#REF#
#ANA-UNISIG-CR0798-0005:01#REF#
Eine Track Condition BMM darf nach Verlassen des vorgegebenen Gültigkeitsbereiches nicht sofort gelöscht werden, sondern erst bei Erreichen der
in der Tabelle #DSC-TBL-BackwardMovement-0004:01#REF# genannten Bedingungen.
#TEST-VAL-SUB026-3358#REF# FCT error expectation BMM area supervision in SR Modus Level 1 (P67 from BG with Q_LINK=0)
#TEST-VAL-SUB026-3810#REF# FCT lower border Storage of BMM information for fixed distance - in SH
#TEST-VAL-SUB026-3787#REF# FCT upper border Storage of BMM information for fixed distance

#REQ-UNISIG-SUB026-3277:01#REF# A3.6.2.1 #ANA-UNISIG-CR0798-0006#REF#
Die Einschränkung gemäß #REQ-UNISIG-SUB026-3276:01#REF# gilt nicht, wenn die Track Condition BMM als solches zu löschen ist, z.B. bei einem
Modewechsel.
#TEST-VAL-SUB026-3788#REF# FCT basic function Storaged BMM information for fixed distance deleted by mode change

#REQ-UNISIG-SUB026-007520#REF# A.3.7.1
A.3.7.1 The brake percentage (λ) shall be converted into two different input parameters:
λo = λ for calculation of emergency brake deceleration (A_brake_emergency(V))
λo = MIN (λ, 135) for calculation of service brake deceleration (A_brake_service(V))
where λ is the brake percentage defined as part of Train Data.
TEST APPROACH:
The correct determination of lambda _0 for the calculation of the brake deceleration is verified via module test BC. The scope of the specific
test outlined here is to verify the correct provisioning of the input from driver and configuration for determination of lambda _0.
#ANALYSE-VALUNISIG-4514#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F82#REF# FCT basic function Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values

#REQ-UNISIG-SUB026-007525#REF# A.3.7.3
A.3.7.3 The speed limit for the first step shall be calculated as V_lim = x * λoy.
V_lim is the speed limit for the first step in km/h
x = 16.85
y = 0.428
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for x, y
2) non-UNISIG values defined for x, y
#ANALYSE-VALUNISIG-4515#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F82#REF# FCT 1 Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values
#TEST-VAL-SUB026-4F73#REF# FCT 2 Configuration change of fixed values taken into account in calculation of the basic deceleration

#REQ-UNISIG-SUB026-007527#REF# A.3.7.4
A.3.7.4 The first step of the basic deceleration shall be calculated as AD_0 = A * λo + B
AD_0 is the basic deceleration in m/s2 for 0 ≤ speed ≤ V_lim.
A = 0.0075
B = 0.076
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for A, B
2) non-UNISIG values defined for A, B
#ANALYSE-VALUNISIG-4516#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F82#REF# FCT 1 Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values
#TEST-VAL-SUB026-4F73#REF# FCT 2 Configuration change of fixed values taken into account in calculation of the basic deceleration

#REQ-UNISIG-SUB026-007530#REF# A.3.7.5
The following steps of the basic deceleration shall be calculated by means of a set of polynomials of the third order with the following format:
AD_n = a3_n * λo3 + a2_n * λo2 + a1_n * λo + a0_n and with the following values for n (all speed limits in km/h):
n = 1	valid for V_lim < speed ≤ 100   if V_lim ≤ 100
to be ignored			  if V_lim > 100
n = 2	valid for V_lim < speed ≤ 120   if 100 < V_lim ≤ 120	valid for 100 < speed ≤ 120	    if V_lim ≤ 100
to be ignored			  if V_lim > 120
n = 3	valid for V_lim < speed ≤ 150   if 120 < V_lim ≤ 150
valid for 120 < speed ≤ 150	    if V_lim ≤ 120
to be ignored			  if V_lim > 150
n = 4	valid for V_lim < speed ≤ 180   if 150 < V_lim ≤ 180
valid for 150 < speed ≤ 180	    if V_lim ≤ 150
to be ignored			  if V_lim > 180
n = 5	valid for V_lim < speed	       if V_lim > 180
valid for 180 < speed		  if V_lim ≤ 180
realised by: #REQ-UNISIG-SUB026-007529:01#REF#

#REQ-UNISIG-SUB026-007529:01#REF# A.3.7.5 #REQ-UNISIG-SUB026-007530#REF#
A.3.7.5 The following steps of the basic deceleration shall be calculated by means of a set of polynomials of the third order with the following
format:
AD_n = a3_n * λo3 + a2_n * λo2 + a1_n * λo + a0_n
and with the following values for n (all speed limits in km/h):
n = 1			valid for V_lim < speed ≤ 100		if V_lim ≤ 100
to be ignored						if V_lim > 100
n = 2			valid for V_lim < speed ≤ 120		if 100 < V_lim ≤ 120
valid for 100 < speed ≤ 120		if V_lim ≤ 100
to be ignored						if V_lim > 120
n = 3			valid for V_lim < speed ≤ 150		if 120 < V_lim ≤ 150
valid for 120 < speed ≤ 150		if V_lim ≤ 120
to be ignored						if V_lim > 150
n = 4			valid for V_lim < speed ≤ 180		if 150 < V_lim ≤ 180
valid for 150 < speed ≤ 180		if V_lim ≤ 150
to be ignored						if V_lim > 180
n = 5			valid for V_lim < speed		if V_lim > 180
valid for 180 < speed		if V_lim ≤ 180
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
#ANALYSE-VALUNISIG-4517#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F82#REF# FCT basic function Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values

#REQ-UNISIG-SUB026-007531#REF# A.3.7.6
A.3.7.6 The coefficients for the polynomials shall be defined as follows:

TEST APPROACH:
The following aspects have been identified:
1) UNISIG values defined for am_N coefficients
2) non-UNISIG values defined for am_N coefficients
#TEST-VAL-SUB026-4F82#REF# FCT 1 Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values
#TEST-VAL-SUB026-4F73#REF# FCT 2 Configuration change of fixed values taken into account in calculation of the basic deceleration

#REQ-UNISIG-SUB026-007533:01#REF# A.3.8.1
A.3.8.1 The basic brake build up time for the emergency brake with the brake position in passenger trains in P shall be calculated as:
T_brake_basic_eb = a + b * (L/100) + c * (L/100)2
where
L = MAX (400m; train length in m)
a = 2.30
b = 0.00
c = 0.17
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for a, b, c and L
2) non-UNISIG values defined for a, b, c and L
#ANALYSE-VALUNISIG-4518#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F82#REF# FCT 1 Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values
#TEST-VAL-SUB026-4F72#REF# FCT 2 Configuration change of values for calculation of EB/SB equivalent time for passenger trains

#REQ-UNISIG-SUB026-010333#REF# A.3.8.2
A.3.8.2 The basic brake build up time for the emergency brake with the brake position in freight trains in P shall be calculated as:
T_brake_basic_eb = a + b * (L/100) + c * (L/100)2
where
L = MAX (400m; train length in m)
If train length ≤ 900m:
a = 2.30
b = 0.00
c = 0.17
If 900m < train length ≤ 1500m:
a = -0.40
b = 1.60
c = 0.03
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for a, b, c and L
2) non-UNISIG values defined for a, b, c and L
#ANALYSE-VALUNISIG-7669#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3B67#REF# FCT 1 Parameters defined in A.3.8, A.3.9 for Freight train in P: UNISIG values
#TEST-VAL-SUB026-3B93#REF# FCT 2 Configuration change of values for calculation of EB/SB equivalent time for freight trains in P

#REQ-UNISIG-SUB026-007535:01#REF# A.3.8.3
A.3.8.3 The basic brake build up time for the emergency brake with the brake position in freight trains in G shall be calculated as:
T_brake_basic_eb = a + b * (L/100) + c * (L/100)2
where
L = train length in m
If train length ≤ 900m:
a = 12.00
b = 0.00
c = 0.05
If 900m < train length ≤ 1500m:
a = -0.40
b = 1.60
c = 0.03
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for a, b, c and L
2) non-UNISIG values defined for a, b, c and L
#ANALYSE-VALUNISIG-4519#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3B68#REF# FCT 1 Parameters defined in A.3.8, A.3.9 for Freight train in G: UNISIG values
#TEST-VAL-SUB026-4F74#REF# FCT 2 Configuration change of values for calculation of EB/SB equivalent time for freight trains in P

#REQ-UNISIG-SUB026-007537#REF# A.3.8.4
A.3.8.4 The equivalent brake build up time for the emergency brake shall be computed as follows:
T_brake_emergency_cm0 = T_brake_basic_eb when V_target = 0
T_brake_emergency_cmt = kto * T_brake_basic_eb when V_target > 0
where
V_target is the target speed
#ANALYSE-VALUNISIG-4520#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007539#REF# A.3.8.5
A.3.8.5 The correction factor kto shall depend on the brake position as follows:
kto = 1 + Ct
where
Ct = 0.16		for freight trains in G
Ct = 0.20		for freight trains in P
Ct = 0.20		for passenger trains
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for Ct
2) non-UNISIG values defined for Ct
Each aspect is tested for Passenger trains in P (PP), Freight trains in G (FG) and Freight trains in P (FP)
#ANALYSE-VALUNISIG-4521#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3B68#REF# FCT 1 (FG) Parameters defined in A.3.8, A.3.9 for Freight train in G: UNISIG values
#TEST-VAL-SUB026-3B67#REF# FCT 1 (FP) Parameters defined in A.3.8, A.3.9 for Freight train in P: UNISIG values
#TEST-VAL-SUB026-4F72#REF# FCT 1 (PP) Configuration change of values for calculation of EB/SB equivalent time for passenger trains
#TEST-VAL-SUB026-4F82#REF# FCT 1 (PP) Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values
#TEST-VAL-SUB026-4F74#REF# FCT 2 (FG) Configuration change of values for calculation of EB/SB equivalent time for freight trains in P
#TEST-VAL-SUB026-3B93#REF# FCT 2 (FP) Configuration change of values for calculation of EB/SB equivalent time for freight trains in P

#REQ-UNISIG-SUB026-007542#REF# A.3.9.1
A.3.9.1 The basic brake build up time for full service brake for passenger trains in P shall be calculated as:
T_brake_basic_sb = a + b * (L/100) + c * (L/100)2
where
L	= train length in m
a	= 3.00
b	= 1.50
c	= 0.10
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for a, b, c and L
2) non-UNISIG values defined for a, b, c and L
#ANALYSE-VALUNISIG-4522#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-4F82#REF# FCT 1 Parameters defined in A.3.7, A.3.8, A.3.9 for Passenger train in P: UNISIG values
#TEST-VAL-SUB026-4F72#REF# FCT 2 Configuration change of values for calculation of EB/SB equivalent time for passenger trains

#REQ-UNISIG-SUB026-007546:01#REF# A.3.9.2
A.3.9.2 The basic brake build up time for full service brake for freight trains in P shall be calculated as:
T_brake_basic_sb = a + b * (L/100) + c * (L/100)2
where
L = train length in m
If train length ≤ 900m:
a = 3.00
b = 2.77
c = 0.00
If 900m < train length ≤ 1500m:
a = 10.50
b = 0.32
c = 0.18
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for a, b, c and L
2) non-UNISIG values defined for a, b, c and L
#ANALYSE-VALUNISIG-4523#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3B67#REF# FCT 1 Parameters defined in A.3.8, A.3.9 for Freight train in P: UNISIG values
#TEST-VAL-SUB026-3B93#REF# FCT 2 Configuration change of values for calculation of EB/SB equivalent time for freight trains in P

#REQ-UNISIG-SUB026-007550:01#REF# A.3.9.3
A.3.9.3 The basic brake build up time for full service brake for freight trains in G shall be calculated as:
T_brake_basic_sb = a + b * (L/100) + c * (L/100)2
where
L = MAX (400m; train length in m)
If train length ≤ 900m:
a = 3.00
b = 2.77
c = 0.00
If 900m < train length ≤ 1500m:
a = 10.50
b = 0.32
c = 0.18
TEST APPROACH:
The correct calculation is verified via module test BC.
The scope of the specific test outlined here is to verify the correct provisioning of the input from configuration for the calculation.
The following aspects have been identified:
1) UNISIG values defined for a, b, c and L
2) non-UNISIG values defined for a, b, c and L
#ANALYSE-VALUNISIG-4524#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.
#TEST-VAL-SUB026-3B68#REF# FCT 1 Parameters defined in A.3.8, A.3.9 for Freight train in G: UNISIG values
#TEST-VAL-SUB026-4F74#REF# FCT 2 Configuration change of values for calculation of EB/SB equivalent time for freight trains in P

#REQ-UNISIG-SUB026-007554#REF# A.3.9.4
A.3.9.4 The equivalent brake build up time for the service brake shall be computed as follows:
T_brake_service_cm0 = T_brake_basic_sb when V_target = 0
T_brake_service_cmt = kto * T_brake_basic_sb when V_target > 0
#ANALYSE-VALUNISIG-4525#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-004483#REF# A.3.9.5
A.3.9.5 The correction factor kto shall be defined as in A.3.8.5
#ANALYSE-VALUNISIG-7599#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-008094#REF# A.3.9.6
A.3.9.6 The values of a, b, c and kto used in A.3.9.1, A.3.9.2, A.3.9.3 and A.3.9.4 define reference values for the equivalent brake build up
time for the service brake, which shall be considered as maximum ones. If justified by the specific brake system of the train other values of
these coefficients, which lead to shorter values of the equivalent brake build up time for the service brake, may be used.
realised by: #REQ-UNISIG-SUB026-008126#REF#

#REQ-UNISIG-SUB026-007560#REF# A.3.10.2 #REQ-UNISIG-SUB026-007050#REF#
A.3.10.2	The on-board shall consider the service brake feedback as available for use if:
a)	The service brake feedback is implemented, AND
b)	The national value does not inhibit its use.
TEST APPROACH:
The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#. 
#TEST-VAL-SUB026-4B83#REF# FCT SB feedback: implemented, dependency on Q_NVSBFBPERM inhibition of SB feedback by National Values

#REQ-UNISIG-SUB026-007563#REF# A.3.10.3
A.3.10.3	Two different types of feedback from the service brake are specified, main brake pipe pressure and brake cylinder pressure. The
algorithms below are made for main brake pipe pressure. When brake cylinder pressure is used instead this shall be converted into a fictive main
brake pressure value in the following way:
p = fictive main brake pipe pressure (kPa)
p_cylinder = brake cylinder pressure (kPa)
k1 = vehicle dependent constant (set by engineering of ETCS on-board; k1 is normally between 2.0 and 2.7)
p =  500  - p_cylinder / k1
TEST APPROACH:
The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#. 
#TEST-VAL-SUB026-4B79#REF# FCT basic function conversion of brake cylinder pressure

#REQ-UNISIG-SUB026-004503#REF# A.3.10.4
A.3.10.4	The value of T_bs1 and T_bs2 shall be calculated according to the following algorithm to take the service brake feedback into
account:
p = current main brake pipe pressure (or fictive main brake pipe pressure calculated in A.3.10.3)
p0 = reference pressure when not braking
p1 = pressure at which the train starts to brake = p0 - 30
p2 = pressure limit, under which T_bs1 and T_bs2 are locked = p0 - 60
p3 = pressure at full service brake = p0 - 150
Q_feedback_started = a Boolean stating whether the feedback function has started to reduce T_bs1 and T_bs2.
Q_Tbslocked = a boolean stating whether T_bs1 and T_bs2 have been locked to the following values due to enough main brake pipe pressure
reduction:
T_bs1_locked =	0 s.
T_bs2_locked =	2 s.
If (Q_Tbslocked) or (Q_feedback_started) or (V_est > V_target and the indication supervision limit has been exceeded) then
If Q_Tbslocked then
T_bs1 = T_bs1_locked
T_bs2 = T_bs2_locked
Else
If p > p2 then
If Q_feedback_started or p ≤ p1 then
Q_feedback_started = true
T_bs_feedback = T_bs * (p - p3) / (p0 - p3)
T_bs1 = T_bs2 = T_bs_feedback
If T_bs_feedback > T_bs then
T_bs1 = T_bs2 = T_bs
Else if T_bs_feedback < T_bs2_locked then
T_bs2 = T_bs2_locked
End If
Else
T_bs1 = T_bs
T_bs2 = T_bs
End If
Else
T_bs1 = T_bs1_locked
T_bs2 = T_bs2_locked
Q_Tbslocked = true
End If
End If
Else
T_bs1 = T_bs
T_bs2 = T_bs
End if
If (the target speed monitoring is left) or (the target location is passed) then
Q_Tbslocked = false
Q_feedback_started = false
End If


The reference pressure p0 (nominal value 500 kPa) shall be set on starting the ETCS:
a)	To the first stable p value between 400-550 kPa achieved.
b)	Stable in this instance means that the pressure has not varied more than ± 20 kPa over 3 seconds.
The reference pressure p0 shall thereafter be adapted to the current pressure according to the following table (which applies if the calculation
is performed once per second):


Where:
-	p is limited to max 550 kPa.
-	Values given in kPa.
realised by: #REQ-UNISIG-SUB026-007566#REF#
realised by: #REQ-UNISIG-SUB026-007567:01#REF#
realised by: #REQ-UNISIG-SUB026-007569#REF#

#REQ-UNISIG-SUB026-007566#REF# A.3.10.4 #REQ-UNISIG-SUB026-004503#REF#
The value of T_bs1 and T_bs2 shall be calculated according to the following algorithm to take the service brake feedback into account:
p = current main brake pipe pressure (or fictive main brake pipe pressure calculated in A.3.10.3)
p0 = reference pressure when not braking
p1 = pressure at which the train starts to brake = p0 - 30
p2 = pressure limit, under which T_bs1 and T_bs2 are locked = p0 - 60
p3 = pressure at full service brake = p0 - 150
Q_feedback_started = a Boolean stating whether the feedback function has started to reduce T_bs1 and T_bs2.
Q_Tbslocked = a boolean stating whether T_bs1 and T_bs2 have been locked to the following values due to enough main brake pipe pressure
reduction:
T_bs1_locked =	0 s.
T_bs2_locked =	2 s.
#ANALYSE-VALUNISIG-7651#REF# FCT The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#.

#REQ-UNISIG-SUB026-007567:01#REF# A.3.10.4 #REQ-UNISIG-SUB026-004503#REF#
The value of T_bs1 and T_bs2 shall be calculated according to the following algorithm to take the service brake feedback into account:
If (Q_Tbslocked) or (Q_feedback_started) or (V_est > V_target and the indication supervision limit has been exceeded) then
If Q_Tbslocked then
T_bs1 = T_bs1_locked
T_bs2 = T_bs2_locked
Else
If p > p2 then
If Q_feedback_started or p ≤ p1 then
Q_feedback_started = true
T_bs_feedback = T_bs * (p - p3) / (p0 - p3)
T_bs1 = T_bs2 = T_bs_feedback
If T_bs_feedback > T_bs then
T_bs1 = T_bs2 = T_bs
Else if T_bs_feedback < T_bs2_locked then
T_bs2 = T_bs2_locked
End If
Else
T_bs1 = T_bs
T_bs2 = T_bs
End If
Else
T_bs1 = T_bs1_locked
T_bs2 = T_bs2_locked
Q_Tbslocked = true
End If
End If
Else
T_bs1 = T_bs
T_bs2 = T_bs
End if
If (the target speed monitoring is left) or (MRDT is changed) then
Q_Tbslocked = false
Q_feedback_started = false
End If
UNISIG clarification:
As end condition "MRDT is changed" shall be used instead of "the target location is passed".
TEST APPROACH:
The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#. 
#ANALYSE-VALUNISIG-7652#REF# FCT The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#.
#TEST-VAL-SUB026-4B78#REF# FCT Lock: T_bs1, T_bs2 once T_bs is locked, it remains so, even if pressure on main brake pipe increases
#TEST-VAL-SUB026-4B86#REF# FCT Unlock: MRDT change due to leaving TSM SB feedback stops, if TSM is left
#TEST-VAL-SUB026-4B85#REF# FCT Unlock: MRDT change due to new track description SB feedback stops, if MRDT changes (new track description received)
#TEST-VAL-SUB026-4B84#REF# FCT Unlock: MRDT change due to passing former MRDT SB feedback stops if MRDT changes

#REQ-UNISIG-SUB026-007569#REF# A.3.10.4 #REQ-UNISIG-SUB026-004503#REF#
The value of T_bs1 and T_bs2 shall be calculated according to the following algorithm to take the service brake feedback into account:
The reference pressure p0 (nominal value 500 kPa) shall be set on starting the ETCS:
a)	To the first stable p value between 400-550 kPa achieved.
b)	Stable in this instance means that the pressure has not varied more than ± 20 kPa over 3 seconds.
The reference pressure p0 shall thereafter be adapted to the current pressure according to the following table (which applies if the calculation
is performed once per second):



Where:
-	p is limited to max 550 kPa.
-	Values given in kPa.
#ANALYSE-VALUNISIG-7653#REF# FCT The feature Service brake feedback is not part of R8.0 refer #REQ-SRS-004417#REF#/#REQ-SWAnf-NotRealizedFeatures-008115#REF#.

Chapter 4

TEST APPROACH:
Note: The track description is verified via a mode independent test interface if not stated otherwise.
		

Chapter 4.4

#REQ-UNISIG-SUB026-004676#REF# 4.4.3.1.1
In Isolation mode, the ERTMS/ETCS on-board equipment shall be physically isolated from the brakes and can be isolated from other on-board
equipments/systems depending on the specific on-board implementation.

--- FINALISED ---
Isolation is realized by hardware.
The EVC In is powered off in isolation. Leaving Isolation is for EVC a normal transition from NP to SB.

see /SyArchSpez/, #REQ-SAD-Isolation-0001#REF#
#ANALYSE-VALUNISIG-5267#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-0149#REF# 4.4.3.1.2
There shall be a clear indication to the driver that the ERTMS/ETCS on-board equipment is isolated.
is realized via Hardware
--- FINALISED ---
Die Anzeige des Isloationsstatus muss anwenderspezifisch im Gesamtkontext des Fahrzeuges festgelegt werden, da bei Isolation des ECTS-Systems
keine ETCS-Anzeigen mehr erfolgen.
Regel #REQ-SWAnf-Regel-0004#REF# wurde erstellt.

#REQ-UNISIG-SUB026-3405#REF# 4.4.3.1.3
To leave Isolation mode, a special operating procedure is needed (no transition from Isolation is specified). This procedure shall ensure that
the on-board equipment is only put back into service when it has been proven that this is safe for operation.
is realized via Hardware
--- FINALISED ---
Isolation is realized by hardware.
The EVC In is powered off in isolation. Leaving Isolation is for EVC a normal transition from NP to SB.

see /SyArchSpez/, #REQ-SAD-Isolation-0001#REF#
#ANALYSE-VALUNISIG-4167#REF# FCT The requirment has to be covered by [ESBO_SyValBer].

#REQ-UNISIG-SUB026-004698#REF# 4.4.4.1.1
When the ERTMS/ETCS on-board equipment is not powered, the equipment shall be in the No Power mode.

--- FINALISED ---
Der Modewechsel nach NP erfolgt mit dem Ausschalten (Stromlosschalten) des ETCS-Fahrzeuggerätes und wird per Hardware realisiert.
Damit muss der Mode No Power nicht separat in der ASW realisiert werden.
Die entsprechenden Bezüge zum Mode No Power in den Tabellen von Kapitel 4 können demzufolge entfallen.
#ANALYSE-VALUNISIG-5268#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-3672#REF# 4.4.4.1.2 #REQ-UNISIG-SUB026-1053#REF#
The ERTMS/ETCS on-board equipment shall permanently command the emergency brake.

--- FINALISED ---
Die Sicherstellung dieser Anforderung ist bereits in der Systemebene dadurch gewährleistet, dass der SRAUS-Ausgang der EB defaultmäßig das
Bremskommando ausgibt (siehe #REQ-DigIO-000651#REF#). Somit liegt das Bremskommando auch im ausgeschalteten Zustand an.
#ANALYSE-VALUNISIG-4086#REF# FCT The requirement has to be covered by [ESBO_SyValBer].

#REQ-UNISIG-SUB026-6793#REF# 4.4.4.3.3
If it is required to move a loco in NP mode as a wagon, ETCS brake command must be overridden by external means.

--- FINALISED ---
is realized in hardware through #REQ-FCT-BAD-0003:01#REF# (see /ESBO_SyAnfSpez/)
#ANALYSE-VALUNISIG-4301#REF# FCT The requirement has to be covered by [ESBO_SyValBer].

#REQ-UNISIG-SUB026-0721#REF# 4.4.5.1.2 #REQ-UNISIG-SUB026-1053#REF#
The ERTMS/ETCS on-board equipment shall permanently command the Emergency Brakes.
#TEST-VAL-SUB026-4126#REF# ECT basic function Mode change SB->SF (BAM reports 'not ready')
#TEST-VAL-SUB026-4127#REF# EET error expectation Mode change SB->SF (Signal input 'Sleeping' set to an implausible value)

#REQ-UNISIG-SUB026-0723#REF# 4.4.6.1.2
The desk(s) of a sleeping engine must be closed (since there is no driver, no information shall be shown).
is realized through mode transitions (see 4.6.2/4.6.3)
realised by: #REQ-UNISIG-SUB026-2213#REF#
realised by: #REQ-UNISIG-SUB026-2221#REF#

#REQ-UNISIG-SUB026-3726#REF# 4.4.6.1.4
The ERTMS/ETCS on-board equipment shall perform the Train Position function; in particular, the front/rear end of the engine (i.e., not the
train) shall be used to refer to train front/rear end.
realised by: #REQ-UNISIG-SUB026-1016:02#REF#
realised by: #REQ-UNISIG-SUB026-3728:01#REF#

#REQ-UNISIG-SUB026-0156#REF# 4.4.6.1.5
Sleeping mode shall be automatically detected on-board via the train interface.
is realized through mode transition condition[14]
realised by: #REQ-UNISIG-SUB026-2221#REF#

#REQ-UNISIG-SUB026-1152#REF# 4.4.6.1.6
If possible, the train must not be stopped due to a safety critical fault in a sleeping engine. The ERTMS/ETCS on-board equipment shall
therefore try to memorise the occurrence of such fault(s), which shall be handled when the engine leaves the Sleeping mode. The ERTMS/ETCS
on-board equipment shall also try to send an error information to the RBC.
#TEST-VAL-SUB026-4006#REF# FCT basic function Safety critical fault in a sleeping engine

#REQ-UNISIG-SUB026-0158#REF# 4.4.6.1.10 #REQ-UNISIG-SUB026-0862#REF#
#ANA-UNISIG-CR0560-0002:01#REF#
The ERTMS/ETCS on-board equipment shall open a communication session with the RBC when at least one of the following events occurs:
a)	in all levels, on receipt of the order to contact the RBC.
b)	In level 2/3, when entering or exiting Sleeping mode (to report the change of mode to the RBC).
c)	In level 2/3, when a safety critical fault of the ERTMS/ETCS on-board equipment occurs (to report the fault to the RBC).
mode sleeping

UNISIG clarification:
Point b is not possible, if Sleeping is exited and the SoM procedure is started before the the Session is opend completly.
In this case the session establishemtn should be  canceled (see condition S0 in SoM and REQ-UNISIG-SUB026-010553)
#TEST-VAL-SUB026-8271#REF# FCT CFX00189721 Establshment of communication session in SL due to safety critical fault of the ERTMS/ETCS on-board equipment
#TEST-VAL-SUB026-4007#REF# FCT a) Acceptance of P42 in SL
#TEST-VAL-SUB026-7141#REF# FCT b) enter SL, exit SL (desk opened) Mode transition SL/L2 to SB/L2 due to cab opening
#TEST-VAL-SUB026-4660#REF# FCT b) exit SL (SL signal removed) RBC ID/Phone Number unchanged when entering RV/SL/SB
#TEST-VAL-SUB026-4001#REF# FCT c) SL - OBU establishes connection in order to send error report

#REQ-UNISIG-SUB026-3083#REF# 4.4.6.1.12
In case of balise group message consistency error (refer to 3.16.2.4.4 and 3.16.2.5.1), the ERTMS/ETCS onboard equipment shall not command the
service brake.
mode sleeping
TEST APPROACH:
The following aspects have been identified:
1) unlinked balise group message consistency  
2) linked balise group message consistency  (no linking is used onboard)
#TEST-VAL-SUB026-4707#REF# FCT 1 Table 4.5.2 --> Unlinked Balise Group Message Consistency (SL,SN)
#TEST-VAL-SUB026-4706#REF# FCT 2 Table 4.5.2 --> Balise Group Message Consistency if no linking consistency is checked (OS,SB,SL,SH)

#REQ-UNISIG-SUB026-004770#REF# 4.4.6.1.13
When in levels 2 or 3, if no compatible version has been established between the on-board equipment in Sleeping mode and the RBC, the ERTMS/ETCS
onboard equipment shall react as specified in 3.5.3.8 b) but no driver’s indication shall be given.
realised by: #REQ-UNISIG-SUB026-0160:01#REF#

#REQ-UNISIG-SUB026-0160:01#REF# to.4.4.6.1.13 #REQ-UNISIG-SUB026-004770#REF#
Exception to 3.5.3.8.b)
No driver’s indication shall be given, if no compatible version has been established between the on-board equipment in Sleeping mode and the
RBC.
UNISIG clarification: the limitation to L2/3 is not correct. A session establishment in SL is also possible  outside L2/3.
#TEST-VAL-SUB026-4009#REF# FCT basic function No compatible version established between the OBU in Sleeping mode and the RBC

#REQ-UNISIG-SUB026-004793#REF# 4.4.7.1.4
In Stand-By mode, the desk of the engine can be open or closed. No interaction with the driver shall be possible as long as the desk is closed,
except isolation of the ERTMS/ETCS on-board equipment.
The Exception for isolation cannot realized, because the EVC ist powered off in IS.

Only if a DMi is active, the obu can accepted messages from this DMI (see REQ-DP_DMI-001173)
--- FINALISED ---
Isolation is realized by hardware.
The EVC In is powered off in isolation. Leaving Isolation is for EVC a normal transition from NP to SB.

see /SyArchSpez/, #REQ-SAD-Isolation-0001#REF#
realised by: #REQ-UNISIG-SUB026-010488#REF#

#REQ-UNISIG-SUB026-010488#REF# to.4.4.7.1.4 #REQ-UNISIG-SUB026-004793#REF#
#REQ-UNISIG-SUB026-010360#REF#
A DMI shall be set active only, if one desk is opened.
Clarification: When the cab is closed, all the procedures shall be reseted.
#TEST-VAL-SUB026-7722#REF# FCT basic function DMI is active only if one desk is opened

#REQ-UNISIG-SUB026-3665#REF# 4.4.7.1.5
The ERTMS/ETCS on-board equipment shall perform the Standstill Supervision.
realised by: #REQ-UNISIG-SUB026-1050#REF#

#REQ-UNISIG-SUB026-004813#REF# 4.4.8.1.1
The purpose of the Shunting mode is to enable shunting movements. In Shunting mode, The ERTMS/ETCS on-board equipment supervises the train
movements against:
a)	a ceiling speed: the shunting mode speed limit
b)	a list of expected balise groups (if such list was sent by the trackside equipment). The train shall be tripped if a balise group, not
contained in the list, is passed (When an empty list is sent, no balise group can be passed. When no list is sent, all balise groups can be
passed)
c)	“stop if in shunting mode” information. The train is tripped if such information is received from balise groups
d)	Intentionally deleted
realised by: #REQ-UNISIG-SUB026-3090#REF#
realised by: #REQ-UNISIG-SUB026-3091#REF#
realised by: #REQ-UNISIG-SUB026-3092#REF#

#REQ-UNISIG-SUB026-3090#REF# 4.4.8.1.1.a #REQ-UNISIG-SUB026-004813#REF#
#REQ-UNISIG-SUB026-1039:01#REF#
#REQ-UNISIG-SUB026-1046:01#REF#
The purpose of the Shunting mode is to enable shunting movements. In Shunting mode, The ERTMS/ETCS on-board equipment supervises the train
movements against:
a ceiling speed: the shunting mode speed limit
#TEST-VAL-SUB026-4241#REF# FCT V_MAMODE transition FS/L2 - SN/STM - SH/L2
#TEST-VAL-SUB026-4435#REF# FCT V_NVSHUNT NV when entering SL, SB, SR, SH

#REQ-BA-Ueberw-0001:02#REF# to.4.4.8.1.1.a
In mode SH the parameterized upper limit for the maximum permitted speed must be supervised as ceiling speed.
Because the speed limit in SH is given by trackside, it is possible in theory, that this speed limit is higher than the max. permitted train
speed, e.g. in case of trains for trackwork "Bau-/Räumfahrzeuge".
#TEST-VAL-SUB026-5695#REF# FCT basic function SH the parameterized upper limit for the maximum permitted speed supervised as ceiling speed

#REQ-UNISIG-SUB026-3091#REF# 4.4.8.1.1.b #REQ-UNISIG-SUB026-004813#REF#
The purpose of the Shunting mode is to enable shunting movements. In Shunting mode, The ERTMS/ETCS on-board equipment supervises the train
movements against:
a list of expected balise groups (if such list was sent by the trackside equipment). The train shall be tripped if a balise group, not contained
in the list, is passed (When an empty list is sent, no balise group can be passed. When no list is sent, all balise groups can be passed).
TEST APPROACH:
Following aspects have been identified:
1) BG list received, included BG passed
2) BG list received, not included BG passed
3) emty list received
4) no list recieved
#TEST-VAL-SUB026-5702#REF# FCT 1, 2 Acceptance of MA from BG in L1
#TEST-VAL-SUB026-4105#REF# FCT 3, 4 Listen von BGs im SH-Bereich

#REQ-UNISIG-SUB026-3092#REF# 4.4.8.1.1.c #REQ-UNISIG-SUB026-004813#REF#
#ANA-UNISIG-ETCSLanguage-0004#REF#
The purpose of the Shunting mode is to enable shunting movements. In Shunting mode, The ERTMS/ETCS on-board equipment supervises the train
movements against:
“stop if in shunting mode” information. The train is tripped if such information is received from balise groups.
#TEST-VAL-SUB026-4013#REF# FCT basic function Baliseninformation 'Stop if in Shunting'

#REQ-UNISIG-SUB026-0167#REF# 4.4.8.1.3
The ERTMS/ETCS on-board equipment shall perform the Train Position function.
realised by: #REQ-UNISIG-SUB026-1016:02#REF#

#REQ-UNISIG-SUB026-0169:01#REF# 4.4.8.1.5 #REQ-UNISIG-SUB026-010092#REF#
When in Shunting mode, the ERTMS/ETCS on-board shall not manage level transitions. However, an immediate level transition order or a conditional
level transition order shall be stored and evaluated only when another mode than Shunting or Passive Shunting has been entered (i.e. when the
Shunting movement is terminated).
realised by: #REQ-UNISIG-SUB026-010115#REF#

#REQ-UNISIG-SUB026-010115#REF# 4.4.8.1.5 #REQ-UNISIG-SUB026-0169:01#REF#
#REQ-UNISIG-SUB026-005262#REF#
When in Shunting or Passive Shunting mode, the ERTMS/ETCS on-board shall not manage level transitions. However, an immediate level transition
order or a conditional level transition order shall be stored and evaluated only when another mode than Shunting or Passive Shunting has been
entered (i.e. when the Shunting movement is terminated).
TEST APPROACH:
The following aspects have been identified:
1) LTO/CTO stored and evaluated when entering other mode than SH or PS
1.1) SH
1.2) PS
2) level announcement not taken into account
2.1) SH
2.2) PS
#TEST-VAL-SUB026-5777#REF# FCT 1.1 Evaluation of immediate level transition order in SH
#TEST-VAL-SUB026-5778#REF# FCT 2.1 Evaluation of multiple level transition order in SH

#REQ-UNISIG-SUB026-004827#REF# 4.4.8.1.5.1 #REQ-DESIGN-CR-0353:01#REF#
When receiving a communication session establishment order, the ERTMS/ETCS on-board in Shunting mode shall not establish the communication
session, but shall store the RBC ID/phone number.
#TEST-VAL-SUB026-5784#REF# FCT basic function Evaluation of communication session establishment order in SH

#REQ-UNISIG-SUB026-004829#REF# 4.4.8.1.5.2
When in Shunting mode, the ERTMS/ETCS on-board shall not manage RBC-RBC hand-over, except for storing the RBC ID/phone number given at the
RBC/RBC border.
#TEST-VAL-SUB026-5785#REF# FCT basic function Evaluation of RBC transition order in SH

#REQ-UNISIG-SUB026-0173:01#REF# 4.4.8.1.10
The ERTMS/ETCS on-board equipment shall display the train speed and, only on driver request, the permitted speed. The display of the permitted
speed shall also be stopped on driver request.
the special indication only on driver request is defined also in ERA SRS DMI (see duplicate link)
realised by: #REQ-UNISIG-SUB026-3308:02#REF#
realised by: #REQ-UNISIG-SUB026-3309#REF#

#REQ-UNISIG-SUB026-0734#REF# 4.4.9.1.3
To be in Full Supervision mode, SSP and gradient are not required for the whole length of the train, but shall be at least available from the
FRONT END of the train.
realised by: #REQ-DESIGN-CR-0499#REF#
realised by: #REQ-DESIGN-CR-0114#REF#

#REQ-UNISIG-SUB026-0178#REF# 4.4.9.1.4 #REQ-UNISIG-SUB026-3330#REF#
Once in Full Supervision mode, if SSP and gradient are not known for the whole length of the train, an indication “ENTRY IN FULL SUPERVISION”
shall be clearly displayed to the driver until SSP and gradient are known for the whole length of the train.
#TEST-VAL-SUB026-4019#REF# FCT L1 L1/FS indication 'Entry In Full Supervision' active till whole length of the train covered by SSP/GP
#TEST-VAL-SUB026-4020#REF# FCT L2/L3 L2/FS indication 'Entry In Full Supervision' active till whole length of the train covered by SSP/GP
#TEST-VAL-SUB026-3728#REF# EET error expectation L1->L2 Level transition buffer information not deleted due change of train length

#REQ-UNISIG-SUB026-004877#REF# 4.4.9.1.5
The ERTMS/ETCS on-board equipment shall supervise train movements against a dynamic speed profile.
realised by: #REQ-UNISIG-SUB026-1042:02#REF#

#REQ-UNISIG-SUB026-004879#REF# 4.4.9.1.6
The ERTMS/ETCS on-board equipment shall display the train speed, the permitted speed, the target distance and the target speed to the driver
(this list is not exhaustive - refer to chapter 4.7 “DMI depending on modes”).
realised by: #REQ-UNISIG-SUB026-3308:02#REF#
realised by: #REQ-UNISIG-SUB026-3309#REF#
realised by: #REQ-UNISIG-SUB026-3310:01#REF#
realised by: #REQ-UNISIG-SUB026-3311:01#REF#

#REQ-UNISIG-SUB026-3094#REF# 4.4.10.1.2 #REQ-UNISIG-SUB026-1039:01#REF#
The ERTMS/ETCS on-board equipment shall supervise train movements against a ceiling speed: the lowest of the maximum train speed and the
Unfitted mode speed limit for unfitted area (national value).
#TEST-VAL-SUB026-4002#REF# FCT basic function Supervision of V_NVUNFIT and max train speed in UN
#TEST-VAL-SUB026-4A23#REF# EET error expectation Determine Most Restrictive Speed Profile, based on Mode related speed restriction UN

#REQ-DESIGN-CR-0487#REF# 4.4.10.1.4
The ERTMS/ETCS on-board equipment shall display the train speed to the driver.
realised by: #REQ-UNISIG-SUB026-3308:02#REF#

#REQ-UNISIG-SUB026-004935#REF# 4.4.11.1.3
The ERTMS/ETCS on-board equipment shall supervise train movements against:
a)	a ceiling speed: the staff responsible mode speed limit
b)	a given distance (regarding its origin location see 4.4.11.1.3.1). The ERTMS/ETCS on-board equipment shall supervise braking curves with
a target speed of zero to the end of this distance. If the train overpasses this distance (see next note) the ERTMS/ETCS on-board equipment
shall trip the train
c)	a list of expected balise groups, if this list has been sent by the RBC. The train shall be tripped if over-passing a balise group that
is not in the list. (When an empty list is sent, no balise group can be passed. When no list is sent, all balise groups can be passed)
d)	balise groups giving the order ‘stop if in SR’. This order shall immediately trip the train, unless the over-passed balise group is
included in a list of expected balises as defined in item c)
e)	running in the direction opposite to the train orientation (reverse movement protection)
realised by: #REQ-UNISIG-SUB026-3086#REF#
realised by: #REQ-DESIGN-CR-0386#REF#
realised by: #REQ-UNISIG-SUB026-3087#REF#
realised by: #REQ-UNISIG-SUB026-3088:01#REF#
realised by: #REQ-UNISIG-SUB026-3089#REF#

#REQ-UNISIG-SUB026-3086#REF# 4.4.11.1.3.a) #REQ-UNISIG-SUB026-004935#REF#
#REQ-UNISIG-SUB026-1039:01#REF#
In Staff Responsible the ERTMS/ETCS on-board equipment shall supervise train movements against a ceiling speed: the staff responsible mode speed
limit
#TEST-VAL-SUB026-4A21#REF# FCT basic function , CFX00038113 Determine Most Restrictive Speed Profile, based on Mode SR

#REQ-DESIGN-CR-0386#REF# 4.4.11.1.3.b) #REQ-UNISIG-SUB026-004935#REF#
In Staff Responsible the ERTMS/ETCS on-board equipment shall supervise train movements against a given distance (regarding its origin location
see 4.4.11.1.3.1).
The ERTMS/ETCS on-board equipment shall supervise braking curves with a target speed of zero to the end of this distance. If the train
overpasses this distance (see next note) the ERTMS/ETCS on-board equipment shall trip the train
TEST APPROACH:
The following aspects have been identified, based on possible origins of distance to run in SR defined in 4.4.11.1.3.1:
1) D_NVSTFF
2) D_SR from driver
3) D_SR from RBC
4) D_SR from loop
The P13 is rejected in R8 refer #REQ-SWAnf-008826#REF# aspect 4 is hence omitted.
#TEST-VAL-SUB026-5881#REF# FCT 1 SR distance supervision based on D_NVSTFF
#TEST-VAL-SUB026-4991#REF# FCT 2 Supervising train movements against a given distance in SR/L1
#TEST-VAL-SUB026-5664#REF# FCT 3 Supervision of D_SR and V_NVSTFF
#TEST-VAL-SUB026-5492#REF# EET CFX00041450 D_SR supervision when D_SR updated during active override

#REQ-UNISIG-SUB026-3087#REF# 4.4.11.1.3.c) #REQ-UNISIG-SUB026-004935#REF#
In Staff Responsible the ERTMS/ETCS on-board equipment shall supervise train movements against a list of expected balise groups, if this list
has been sent by the RBC.
The train shall be tripped if over-passing a balise group that is not in the list. (When an empty list is sent, no balise group can be passed.
When no list is sent, all balise groups can be passed)
TEST APPROACH:
Following aspects have been identified:
1) BG list received, included BG passed
2) BG list received, not included BG passed
3) emty list received
4) no list recieved
#TEST-VAL-SUB026-4330#REF# FCT 1, 2 List of Balises in SR Authority overwritten by new List of Balises in SR Authority
#TEST-VAL-SUB026-4023#REF# FCT 3 leere BG-Liste fuer SR
#TEST-VAL-SUB026-4331#REF# FCT 4 List of Balises in SR Authority deleted by new SR Authorisation
#TEST-VAL-SUB026-5620#REF# EET error expectation List of Balise in SR Authority + SR distance when entering L1

#REQ-UNISIG-SUB026-3088:01#REF# 4.4.11.1.3.d) #REQ-UNISIG-SUB026-004935#REF#
#ANA-UNISIG-ETCSLanguage-0004#REF#
In Staff Responsible the ERTMS/ETCS on-board equipment shall supervise train movements against balise groups giving the order ‘stop if in SR’.
This order shall immediately trip the train, unless the over-passed balise group is included in a list of expected balises as defined in item c)
#TEST-VAL-SUB026-5930#REF# FCT basic function Evaluation of 'stop if in Staff Responsible' depending on P137
#TEST-VAL-SUB026-4898#REF# EET error expectation Transition table 4.6.3 - Conditions 36, 54

#REQ-UNISIG-SUB026-3089#REF# 4.4.11.1.3.e) #REQ-UNISIG-SUB026-004935#REF#
In Staff Responsible the ERTMS/ETCS on-board equipment shall supervise train movements against running in the direction opposite to the train
orientation (reverse movement protection)
realized with line "Reverse Movement Protection" in table 4.5.2
realised by: #REQ-UNISIG-SUB026-1049:01#REF#

#REQ-UNISIG-SUB026-008623#REF# 4.4.11.1.3.1
The ERTMS/ETCS on-board shall determine the start location of the SR distance as follows:
a)	If the National/Default value determines the max permitted distance to run in SR mode, the starting point of this distance shall refer
to the estimated position of the train front when SR mode was entered, or, already in Staff Responsible mode, when Override was activated.
b)	If the max permitted distance to run in SR mode is determined by the value transmitted by the RBC, or entered by the driver, the start
location of the distance shall refer to the estimated position of the train front when the distance information is received or entered.
c)	If the max permitted distance to run in SR mode is determined by the value transmitted by EUROLOOP, the distance information transmitted
by EUROLOOP shall be referred to one or more reference balise groups. On-board shall evaluate the distance to run in SR mode by matching the
reference balise groups given with the LRBG.
In case the LRBG is, due to a change of orientation, in front of the train when the distance to run in SR mode is to be determined from the
EUROLOOP information, the complete distance to run in SR mode shall be determined as the distance given by EUROLOOP plus the distance between
the estimated train front end and the LRBG.
part c (awakening on loop) isn't realized
realised by: #REQ-DESIGN-CR-0387#REF#

#REQ-DESIGN-CR-0387#REF# to.4.4.11.1.3.1 #REQ-UNISIG-SUB026-008623#REF#
The ERTMS/ETCS on-board shall determine the start location of the SR distance as follows:
a)	If the National/Default value determines the max permitted distance to run in SR mode, the starting point of this distance shall refer
to the estimated position of the train front when SR mode was entered, or, already in Staff Responsible mode, when Override was activated.
b)	If the max permitted distance to run in SR mode is determined by the value transmitted by the RBC, or entered by the driver, the start
location of the distance shall refer to the estimated position of the train front when the distance information is received or entered.
TEST APPROACH:
Following aspects have been identified:
1) National/Default value determines the max permitted distance to run in SR mode
1.1) when SR mode was entered
1.2) already in SR mode, when Override was activated
2) transmitted by the RBC
3) entered by the driver
#TEST-VAL-SUB026-5881#REF# FCT 1.1 SR distance supervision based on D_NVSTFF
#TEST-VAL-SUB026-5507#REF# FCT 1.2 End of inhibition to Trip in SR on crossing SR supervised distance
#TEST-VAL-SUB026-4027#REF# FCT 2 , CFX00035443 new MA request in SR
#TEST-VAL-SUB026-4991#REF# FCT 3 Supervising train movements against a given distance in SR/L1
#TEST-VAL-SUB026-2010#REF# EET CFX00179301 Supervision of D_NVSTFF

#REQ-UNISIG-SUB026-0189#REF# 4.4.11.1.5
The ERTMS/ETCS on-board equipment shall give the possibility to the driver to modify the value of the SR mode speed limit and of the given
distance. This shall be possible only at standstill.
is realized with enabling conditions for the button "SR speed / distance" in ERA SRS DMI
#TEST-VAL-SUB026-4026#REF# FCT basic function Change Staff Responsible Speed / Staff Responsible Distance via DMI possible at standstill only

#REQ-UNISIG-SUB026-004952#REF# 4.4.11.1.5.1
If a train movement is detected while the driver is entering the SR speed/distance limits, the ERTMS/ETCS on-board equipment shall trigger the
brake command.
UNISIG clarification:
SB is to be commanded, analogous to Entry of train data (see 3.18.3.3.1)

hint:
the SR speed/distance dialogue is stopped in this case (see ERA SRS DMI, chapter 11.7.1.7)
#TEST-VAL-SUB026-4026#REF# FCT basic function Change Staff Responsible Speed / Staff Responsible Distance via DMI possible at standstill only

#REQ-UNISIG-SUB026-0190:01#REF# 4.4.11.1.6
In level 2/3, the driver shall have the possibility to request a new distance to run in Staff Responsible, by selecting "Start". This
triggers an MA request.
is realized with enabling conditions for the button "Start" in ERA SRS DMI
realised by: #REQ-UNISIG-SUB026-0475#REF#

#REQ-DESIGN-CR-0332#REF# 4.4.11.1.6.2
When entering SR mode, the value applicable for SR mode speed limit and the value applicable for SR distance shall be the corresponding
National/Default values. Exception for SR distance: SR mode is authorised by RBC giving an SR distance.
TEST APPROACH:
Following aspects have been identified:
1) supervised distance
1.1) SR distance D_NVSTFF
1.2) SR distance D_SR 
2) supervised speed 
#TEST-VAL-SUB026-5291#REF# FCT 1.1 D_NVSTFF default
#TEST-VAL-SUB026-5664#REF# FCT 1.2, 2 Supervision of D_SR and V_NVSTFF

#REQ-DESIGN-CR-0333#REF# 4.4.11.1.6.3 #REQ-UNISIG-SUB026-002033#REF#
While in SR mode, the value applicable for the SR mode speed limit shall be, if available, the last value entered by the driver.
#TEST-VAL-SUB026-5884#REF# FCT basic function Last entered/received value for D_SR/V_SR supervised

#REQ-DESIGN-CR-0334#REF# 4.4.11.1.6.4
While in SR mode, the value applicable for the SR distance shall be, if available, the last value received by the ERTMS/ETCS on-board equipment
amongst:
a)	the distance to run in SR entered by the driver;
b)	the distance to run in SR given by trackside.
TEST APPROACH:
Following aspects have been identified:
1) entered by the driver
2) given by trackside
2.1) RBC
2.2) loop
The P13 is rejected in R8 refer #REQ-SWAnf-008826#REF# aspect 2.2 is hence omitted.
#TEST-VAL-SUB026-5884#REF# FCT 1, 2.1 Last entered/received value for D_SR/V_SR supervised
#TEST-VAL-SUB026-8276#REF# EET CFX00189145 Supervision of SR distance

#REQ-DESIGN-CR-0458#REF# 4.4.11.1.6.5
When "Override" is selected, the SR mode speed limit value and the SR distance value previously entered by driver or given by
trackside, if any, shall be deleted. The corresponding National/Default values shall enter in force.
TEST APPROACH:
Following aspects have been identified:
1) value from driver
1.1) speed 
1.2) distance
2) value from trackside
2.1) speed
#TEST-VAL-SUB026-8287#REF# FCT 1.1 SR speed supervision after override activation
#TEST-VAL-SUB026-5507#REF# FCT 1.2 End of inhibition to Trip in SR on crossing SR supervised distance
#TEST-VAL-SUB026-5418#REF# FCT 2.1 SR/L2 Override active - LTO (L1) trip order -> SR/L1 - override inactive after D_NVOVTRP
#TEST-VAL-SUB026-8107#REF# EET CFX00179301 SR/L2 Override active - delete SR distance from RBC

#REQ-UNISIG-SUB026-3100#REF# 4.4.11.1.6.6
If the train is in SR and receives a new distance to run in SR mode from the RBC, the stored list of expected balise groups, if any, shall be
deleted or shall be replaced by the list of expected balise groups sent together with the distance to run in SR.
TEST APPROACH:
The following aspects have been identified:
1) stored list of expected balise groups deleted
2) stored list of expected balise groups replaced
#TEST-VAL-SUB026-4331#REF# FCT 1 List of Balises in SR Authority deleted by new SR Authorisation
#TEST-VAL-SUB026-4330#REF# FCT 2 List of Balises in SR Authority overwritten by new List of Balises in SR Authority

#REQ-UNISIG-SUB026-004970#REF# 4.4.11.1.6.7
If an ERTMS/ETCS on-board equipment in SR mode, after having received from EUROLOOP max permitted distance to run in SR mode information,
detects the main signal balise group being part of this information then it shall ignore any new max permitted distance to run in SR mode
information from that loop.
awakening on loop isn't realized

#REQ-UNISIG-SUB026-001798#REF# 4.4.11.1.7
The ERTMS/ETCS on-board equipment shall display the train speed and the (when active) override (permission to pass a signal at danger, trip
inhibited). The permitted speed, target distance and the target speed shall be displayed only on driver request, until the driver requests to
stop their display.
the special indication only on driver request is defined also in ERA SRS DMI (see duplicate link)
realised by: #REQ-UNISIG-SUB026-3308:02#REF#
realised by: #REQ-UNISIG-SUB026-3309#REF#
realised by: #REQ-UNISIG-SUB026-3310:01#REF#
realised by: #REQ-UNISIG-SUB026-3311:01#REF#
realised by: #REQ-DESIGN-CR-0034#REF#

#REQ-UNISIG-SUB026-0193#REF# 4.4.11.1.9
If receiving a "track ahead free" request from the RBC, the ERTMS/ETCS on-board equipment requests the driver to enter the "track
ahead free" information.
mode Staff Responsible
realised by: #REQ-UNISIG-SUB026-3332#REF#

#REQ-UNISIG-SUB026-005002#REF# 4.4.12.1.3
The ERTMS/ETCS on-board equipment shall supervise train movements against a dynamic speed profile.
realised by: #REQ-UNISIG-SUB026-1042:02#REF#

#REQ-UNISIG-SUB026-001814#REF# 4.4.12.1.4
The ERTMS/ETCS on-board equipment shall display the train speed to the driver (this list is not exhaustive). The permitted speed, target
distance,target speed and release speed (if any) shall be displayed only on driver request, until the driver requests to stop their display.
the special indication only on driver request is defined also in ERA SRS DMI (see duplicate link)
realised by: #REQ-UNISIG-SUB026-3308:02#REF#
realised by: #REQ-UNISIG-SUB026-3309#REF#
realised by: #REQ-UNISIG-SUB026-3310:01#REF#
realised by: #REQ-UNISIG-SUB026-3311:01#REF#
realised by: #REQ-UNISIG-SUB026-3312#REF#

#REQ-UNISIG-SUB026-0735#REF# 4.4.12.1.5
If receiving a "track ahead free" request from the RBC, the ERTMS/ETCS on-board equipment requests the driver to enter the "track
ahead free" information.
realised by: #REQ-UNISIG-SUB026-3332#REF#

#REQ-UNISIG-SUB026-005008#REF# 4.4.12.1.6
To be in On Sight mode, SSP and gradient are not required for the whole length of the train, but shall be at least available from the FRONT END
of the train.
realised by: #REQ-DESIGN-CR-0499#REF#
realised by: #REQ-DESIGN-CR-0114#REF#

#REQ-UNISIG-SUB026-0201#REF# 4.4.12.1.7 #REQ-UNISIG-SUB026-3330#REF#
Once in On Sight mode, if SSP and gradient are not known for the whole length of the train, an indication “ENTRY IN ON SIGHT” shall be clearly
displayed to the driver until SSP and gradient are known for the whole length of the train.
#TEST-VAL-SUB026-4033#REF# FCT L1 Indication 'Entry in ON SIGHT' in L1
#TEST-VAL-SUB026-4034#REF# FCT L2/L3 Indication 'Entry in ON SIGHT' in L2
#TEST-VAL-SUB026-3729#REF# EET error expectation train length increased just before switch from SR/L1 to OS/L1

#REQ-UNISIG-SUB026-0204#REF# 4.4.13.1.2 #REQ-UNISIG-SUB026-1053#REF#
The ERTMS/ETCS on-board equipment shall command the emergency brakes (no brake release is possible in Trip mode).
#TEST-VAL-SUB026-4036#REF# FCT basic function pass EOA, L1

#REQ-UNISIG-SUB026-0205#REF# 4.4.13.1.3 #REQ-UNISIG-SUB026-3314:01#REF#
The ERTMS/ETCS on-board equipment shall indicate to the driver the reason of the train trip.
the indication is realized with the system status messages
TEST APPROACH:
The following system status messages are identified (ERA DMI Table 68), that indicate the TRIP reason:
1) Balise group error
2) Communication error
3) SH refused
4) Trackside not compatible
5) Unauthorized passing of EOA / LOA
6) No MA received at level transition
7) SR distance exceeded
8) SH stop order
9) SR stop order
10) Emergency stop
11) No track description
12) [name of NTC] brake demand
#TEST-VAL-SUB026-3175#REF# FCT 1 passage of announced BG in wrong direction
#TEST-VAL-SUB026-3197#REF# FCT 2 NVCONTACT supervision, M_NVCONTACT=0 - Train trip
#TEST-VAL-SUB026-7059#REF# FCT 3 SN/STM (EB applied) driver selects SH
#TEST-VAL-SUB026-4254#REF# FCT 4 transition SR(L2) -> SR(L1) -> TR(L1)[65]
#TEST-VAL-SUB026-4036#REF# FCT 5 pass EOA, L1
#TEST-VAL-SUB026-5084#REF# FCT 6 Level transition NTC->L1 without L1-MA
#TEST-VAL-SUB026-5881#REF# FCT 7 SR distance supervision based on D_NVSTFF
#TEST-VAL-SUB026-5506#REF# FCT 8 End of inhibition to Trip in SR/SH mode on crossing BG not in expected list of balises
#TEST-VAL-SUB026-5930#REF# FCT 9 Evaluation of 'stop if in Staff Responsible' depending on P137
#TEST-VAL-SUB026-4A51#REF# FCT 10 Unconditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-5262#REF# FCT 11 Transition from LS to TR due backward movement out of GP coverage
#TEST-VAL-SUB026-4494#REF# FCT 12 SN/STM (EB applied) - transition to L1

#REQ-UNISIG-SUB026-0206#REF# 4.4.13.1.4
The ERTMS/ETCS on-board equipment shall request an acknowledgement from the driver once train is at standstill (to allow the driver to
acknowledge the train trip).
realized by procedure Train Trip (Kap. 5.11.3 - S060)
realised by: #REQ-DESIGN-CR-0176:01#REF#

#REQ-UNISIG-SUB026-010360#REF# 4.4.13.1.6
Closing the desk while being in Trip mode will not cause a mode change but no interaction with the driver shall be possible as long as the desk
is closed, except isolation of the ERTMS/ETCS on-board equipment.
no change to another mode is defined in this case (see 4.6.2)
realised by: #REQ-UNISIG-SUB026-010488#REF#

#REQ-UNISIG-SUB026-0209#REF# 4.4.14.1.1
The Post Trip mode shall be entered immediately after the driver acknowledges the trip.
is realized through mode transition condition[7]
realised by: #REQ-UNISIG-SUB026-2253#REF#

#REQ-UNISIG-SUB026-0736#REF# 4.4.14.1.2
Once in post trip mode, the onboard equipment shall release the Command of the emergency brake.
#TEST-VAL-SUB026-4036#REF# FCT basic function pass EOA, L1

#REQ-UNISIG-SUB026-0210:01#REF# 4.4.14.1.3 #REQ-UNISIG-SUB026-1047#REF#
The train shall only be authorised to move backwards a given distance (national value). The ERTMS/ETCS on-board equipment shall supervise this
national distance for reverse movements, and shall command the service brakes if the distance is over-passed. The driver shall be informed about
the reason for the brake application.
mode Post Trip
#TEST-VAL-SUB026-4779#REF# FCT basic function SB due to PT distance exceeded released at standstill and after driver ack

#REQ-UNISIG-SUB026-005068#REF# 4.4.14.1.3.2
After the release of a brake command initiated due to an overpassed distance allowed for moving backwards in Post Trip mode, the ERTMS/ETCS
on-board equipment shall command the service brake for any further movement in the direction opposite to the train orientation.
realised by: #REQ-UNISIG-SUB026-010175#REF#

#REQ-UNISIG-SUB026-010175#REF# 4.4.14.1.3.2 #REQ-UNISIG-SUB026-005068#REF#
After the release of a brake command initiated due to an overpassed distance allowed for moving backwards in Post Trip mode and while the post
trip distance is still overpassed, the ERTMS/ETCS on-board equipment shall command the service brake for any further movement in the direction
opposite to the train orientation.
UNISIG clarification:
a forward coasting is possible. Therefore a backtracking to the former position must be possible also.
#TEST-VAL-SUB026-4779#REF# FCT basic function SB due to PT distance exceeded released at standstill and after driver ack

#REQ-UNISIG-SUB026-0211#REF# 4.4.14.1.4
When moving backwards in Post Trip mode, the train trip shall be inhibited.
#TEST-VAL-SUB026-4040#REF# FCT basic function Auf PT erfolgt kein Wechsel nach TR

#REQ-DESIGN-CR-0171#REF# 4.4.14.1.6
When ERTMS/ETCS level is 1, if the driver selects “Start” the onboard equipment proposes Staff Responsible. When ERTMS/ETCS level is 2 or 3, the
selection of Start leads to an MA Request to the RBC. It is the RBC responsibility to give an SR authorisation, or a Full Supervision MA or an
On Sight/Shunting MA to an ERTMS/ETCS equipment that is in Post Trip mode.
mode Post Trip
TEST APPROACH:
Following aspects have been identified:
1) L1
2) L2/L3
#TEST-VAL-SUB026-4041#REF# FCT 1 From PT to Start, L1
#TEST-VAL-SUB026-4523#REF# FCT 2 Movement Authority Request Parameters in PT

#REQ-UNISIG-SUB026-3084#REF# 4.4.14.1.9
In case of balise group message consistency error (refer to 3.16.2.4.4 and 3.16.2.5.1), the ERTMS/ETCS onboard equipment shall not command the
service brake.
TEST APPROACH:
The following aspects have been identified:
1) unlinked balise group message consistency  
2) linked balise group message consistency  (no linking is used onboard)
#TEST-VAL-SUB026-4704#REF# FCT 1 Table 4.5.2 --> Unlinked Balise Group Message Consistency (OS,TR,PT,RV)
#TEST-VAL-SUB026-4708#REF# FCT 2 Table 4.5.2 --> Balise Group Message Consistency if no linking consistency is checked (TR,PT,RV,NL)

#REQ-UNISIG-SUB026-005100#REF# 4.4.15.1.1.2
The ERTMS/ETCS on-board equipment shall use, as a necessary condition to enter in Non-Leading mode, a “non leading input signal" from the
train interface.
is released with mode condition[46]
realised by: #REQ-UNISIG-SUB026-2222:01#REF#

#REQ-UNISIG-SUB026-005102#REF# 4.4.15.1.1.3
If the “non leading input signal" is no longer present, the switch to Stand-By mode shall be made only if the train is at standstill.
realised by: #REQ-UNISIG-SUB026-2240:02#REF#

#REQ-UNISIG-SUB026-3727#REF# 4.4.15.1.3
The ERTMS/ETCS on-board equipment shall perform the Train Position function; in particular, the front/rear end of the engine (i.e., not the
train) shall be used to refer to train front/rear end.
realised by: #REQ-UNISIG-SUB026-1016:02#REF#
realised by: #REQ-UNISIG-SUB026-3728:01#REF#

#REQ-UNISIG-SUB026-0218#REF# 4.4.15.1.5
If possible, the train must not be stopped due to a safety critical fault in a non-leading engine. The ERTMS/ETCS on-board equipment shall
therefore try to memorise the occurrence of such fault(s), which shall be handled when the engine leaves Non Leading mode. The ERTMS/ETCS
on-board equipment shall also try to send an error information to the RBC.
Mode NON LEADING
#TEST-VAL-SUB026-4045#REF# FCT basic function Safety critical fault in a non-leading engine

#REQ-UNISIG-SUB026-0222#REF# 4.4.15.1.10
In case of balise group message consistency error (refer to 3.16.2.4.4 and 3.16.2.5.1), the ERTMS/ETCS onboard equipment shall not command the
service brake..
TEST APPROACH:
The following aspects have been identified:
1) unlinked balise group message consistency  
2) linked balise group message consistency  (no linking is used onboard)
#TEST-VAL-SUB026-4702#REF# FCT 1 Table 4.5.2 --> Check Balise Group Message Consistency unlinked balise group (FS,NL,SB,SR,UN,SH)
#TEST-VAL-SUB026-4046#REF# FCT 2 BG consistency check in NL

#REQ-DESIGN-CR-0616:02#REF# 4.4.18.1.3
The ERTMS/ETCS on-board equipment shall supervise train movements against:
a)	a ceiling speed: the Reversing mode speed limit given from trackside
b)	a distance to run in the direction opposite to the train orientation, given from trackside. The emergency brake shall be commanded if
overpassing this distance
realised by: #REQ-UNISIG-SUB026-3095#REF#
realised by: #REQ-UNISIG-SUB026-3096:02#REF#

#REQ-UNISIG-SUB026-3095#REF# 4.4.18.1.3.a #REQ-UNISIG-SUB026-3106#REF#
#REQ-DESIGN-CR-0324#REF#
#REQ-DESIGN-CR-0616:02#REF#
#REQ-UNISIG-SUB026-3107#REF#
#REQ-UNISIG-SUB026-1039:01#REF#
#REQ-UNISIG-SUB026-1046:01#REF#
Mode REVERSING
The ERTMS/ETCS on-board equipment shall supervise train movements against a ceiling speed, the Reversing mode speed limit given from trackside.
#TEST-VAL-SUB026-5728#REF# FCT basic function V_REVERSE supervision
#TEST-VAL-SUB026-5729#REF# EET error expectation V_MAX_TRAIN supervision in RV

#REQ-UNISIG-SUB026-3096:02#REF# 4.4.18.1.3.b #REQ-DESIGN-CR-0324#REF#
#REQ-DESIGN-CR-0326:01#REF#
#REQ-DESIGN-CR-0616:02#REF#
#REQ-UNISIG-SUB026-1047#REF#
Mode REVERSING
The ERTMS/ETCS on-board equipment shall only be authorised to move backwards and shall supervise train movements against a distance to run in
the direction opposite to the train orientation, given from trackside. The emergency brake shall be commanded if overpassing this distance.
#TEST-VAL-SUB026-3580#REF# FCT basic function D_REVERSE supervision
#TEST-VAL-SUB026-5625#REF# EET error expecattion RV distances supervised with estimated front end
#TEST-VAL-SUB026-3579#REF# EET error expectation Supervision of D_REVERSE after RV area shortening
#TEST-VAL-SUB026-3581#REF# EET error expectation brake due to reversing supervision information - brake release at standstill after driver acknowledgement

#REQ-UNISIG-SUB026-3099:01#REF# 4.4.18.1.4
After the release of a brake command initiated due to an overpassed reversing distance, and while the reversing distance is still overpassed,
the ERTMS/ETCS on-board equipment shall command the emergency brake for any further movement in the direction opposite to the train orientation.
mode REVERSING
#TEST-VAL-SUB026-3580#REF# FCT basic function D_REVERSE supervision

#REQ-UNISIG-SUB026-007482#REF# 4.4.18.1.5
The ERTMS/ETCS on-board equipment shall display the train speed, the permitted speed and the remaining distance to run.
mode REVERSING

realize through  table 4.7.2
realised by: #REQ-UNISIG-SUB026-3308:02#REF#
realised by: #REQ-UNISIG-SUB026-3309#REF#
realised by: #REQ-UNISIG-SUB026-3311:01#REF#

#REQ-UNISIG-SUB026-005184#REF# 4.4.18.1.6
In case the SBI supervision limit is exceeded (refer to chapter 3 table 5, triggering condition t4), the ERTMS/ETCS on-board equipment shall
command the emergency brake instead of the service brake. For the revocation of the brake command, refer to 3.13.10.2.4.
mode REVERSING
#TEST-VAL-SUB026-5729#REF# FCT V_MAX_TRAIN V_MAX_TRAIN supervision in RV
#TEST-VAL-SUB026-5728#REF# FCT V_REVERSE V_REVERSE supervision

#REQ-DESIGN-CR-0142#REF# 4.4.18.1.10
In case of balise group message consistency error (refer to 3.16.2.4.4 and 3.16.2.5.1), the ERTMS/ETCS onboard equipment shall not command the
service brake.
mode REVERSING
TEST APPROACH:
The following aspects have been identified:
1) unlinked balise group message consistency  
2) linked balise group message consistency  (no linking is used onboard)
#TEST-VAL-SUB026-4704#REF# FCT 1 Table 4.5.2 --> Unlinked Balise Group Message Consistency (OS,TR,PT,RV)
#TEST-VAL-SUB026-3521#REF# FCT 2 A.3.4.1m) effect on Reversing supervision information - RV

#REQ-UNISIG-SUB026-005194#REF# 4.4.18.1.11
In case there is an alarm reporting a malfunction for the onboard balise transmission function, the ERTMS/ETCS onboard equipment shall ignore
this alarm.
mode REVERSING

the BMM alarm is ignored independent of TC BMM
#TEST-VAL-SUB026-5941#REF# FCT basic function Alarm reporting a malfunction for the onboard balise transmission function in RV

#REQ-UNISIG-SUB026-005196#REF# 4.4.18.1.12
In case the ERTMS/ETCS system version number X transmitted by any balise is greater than the highest version X supported by the onboard
equipment (refer to 3.17.3.5), the information from this balise shall be ignored, the train shall not be tripped and the driver shall not be
informed.
realized through
realised by: #REQ-UNISIG-SUB026-3735:01#REF#

#REQ-UNISIG-SUB026-3358#REF# 4.4.19.1.3 #REQ-UNISIG-SUB026-1039:01#REF#
The ERTMS/ETCS on-board equipment shall supervise train movements against a dynamic speed profile.
realized by 4.5.2
realised by: #REQ-UNISIG-SUB026-1042:02#REF#

#REQ-UNISIG-SUB026-3359#REF# 4.4.19.1.4
The ERTMS/ETCS on-board equipment shall display the train speed. If the permitted speed is lower than both the Limited Supervision mode speed
limit and the maximum train speed, the permitted speed and the target speed shall be indicated (this list and the conditions are not exhaustive
- refer to chapter 4.7 “DMI depending on modes”).
the special speed indication is defined also in ERA SRS DMI (see duplicate link)
realised by: #REQ-UNISIG-SUB026-3308:02#REF#
realised by: #REQ-UNISIG-SUB026-3309#REF#
realised by: #REQ-UNISIG-SUB026-3310:01#REF#

#REQ-UNISIG-SUB026-3360#REF# 4.4.19.1.5
If receiving a "track ahead free" request from the RBC, the ERTMS/ETCS on-board equipment requests the driver to enter the "track
ahead free" information.
realized by 4.7.2
realised by: #REQ-UNISIG-SUB026-3332#REF#

#REQ-UNISIG-SUB026-3361#REF# 4.4.19.1.6
To be in Limited Supervision mode, SSP and gradient are not required for the whole length of the train, but shall be at least available from the
FRONT END of the train.
is realized through 3.7.2.3 and the note 3.7.2.3.1
realised by: #REQ-DESIGN-CR-0499#REF#
realised by: #REQ-DESIGN-CR-0114#REF#

#REQ-UNISIG-SUB026-005244#REF# 4.4.20.1.2
The desk of a Passive Shunting engine must be closed (since there is no driver, no information shall be shown).
realised by: #REQ-UNISIG-SUB026-010227#REF#

#REQ-UNISIG-SUB026-005246#REF# 4.4.20.1.3
As the engine is coupled to a leading engine, its ERTMS/ETCS on-board equipment shall not perform any train movement supervision.

--- FINALISED ---
The mode dependency of the functions is defined in table 4.5.2.
#ANALYSE-VALUNISIG-7641#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-005248#REF# 4.4.20.1.4
The ERTMS/ETCS on-board equipment shall perform Train Position function; in particular, the front/rear end of the engine (i.e., not the train)
shall be used to refer to train front/rear end.
realised by: #REQ-UNISIG-SUB026-1016:02#REF#
realised by: #REQ-UNISIG-SUB026-3728:01#REF#

#REQ-UNISIG-SUB026-005250#REF# 4.4.20.1.5
It shall only be possible to enter in Passive Shunting mode from the Shunting mode; while in Shunting mode, the driver shall have the
possibility to enable the function “Continue Shunting on desk closure”.
is realized with enabling conditions for the button "Maintain Shunting" in ERA SRS DMI

#REQ-UNISIG-SUB026-005252#REF# 4.4.20.1.6
When the active desk is closed, the ERTMS/ETCS on-board equipment shall switch to Passive Shunting mode if the function “Continue Shunting on
desk closure” is active and the “passive shunting input signal” is received from the train interface. If the function “Continue Shunting on desk
closure” is not active or the “passive shunting input signal” is not present, the ERTMS/ETCS on-board equipment shall switch to Stand-By mode
instead.
conform to mode transition [26], [27], [30]
realised by: #REQ-UNISIG-SUB026-010227#REF#
realised by: #REQ-UNISIG-SUB026-010228#REF#
realised by: #REQ-UNISIG-SUB026-010229#REF#

#REQ-UNISIG-SUB026-005254#REF# 4.4.20.1.7 #REQ-UNISIG-SUB026-010391#REF#
The special function “Continue Shunting on desk closure” shall allow one and only one transition from Shunting mode to Passive Shunting mode.
The special function shall be inactive once the Shunting mode is left.
TEST APPROACH:
The following aspect have been identified:
1. one and only one transition from Shunting mode to Passive Shunting mode is allowed by the special function
2. the special function shall be inactive once the Shunting mode is left
#TEST-VAL-SUB026-7957#REF# FCT 1 Special function 'Continue Shunting on desk closure' allows only one transition from SH to PS
#TEST-VAL-SUB026-7970#REF# FCT 2 Special function 'Continue Shunting on desk closure' becomes inactive once leaving SH

#REQ-UNISIG-SUB026-005256#REF# 4.4.20.1.8
If a desk of the Passive Shunting engine is opened and no “Stop Shunting on desk opening” information previously received from balise group is
stored onboard, the ERTMS/ETCS on-board equipment shall switch to Shunting mode.
conform to mode transition [23]
realised by: #REQ-UNISIG-SUB026-010226#REF#

#REQ-UNISIG-SUB026-005258#REF# 4.4.20.1.9
If a desk of the Passive Shunting engine is opened and “Stop Shunting on desk opening” information previously received from balise group is
stored onboard, the ERTMS/ETCS on-board equipment shall switch to Stand By mode.
conform to mode transition [22]
realised by: #REQ-UNISIG-SUB026-010225#REF#

#REQ-UNISIG-SUB026-005260#REF# 4.4.20.1.10
If possible, the train must not be stopped due to a safety critical fault in a Passive Shunting engine. The ERTMS/ETCS on-board equipment shall
therefore try to memorise the occurrence of such fault(s), which shall be handled when the engine leaves the Passive Shunting mode.
it's not possible to change to PS
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-005262#REF# 4.4.20.1.11 #REQ-UNISIG-SUB026-010092#REF#
When in Passive Shunting mode, the ERTMS/ETCS on-board shall not manage level transitions. However, an immediate level transition order or a
conditional level transition order shall be stored and shall be evaluated only when another mode than Shunting or Passive Shunting has been
entered (i.e. when the Shunting movement is terminated).
realised by: #REQ-UNISIG-SUB026-010115#REF#

#REQ-UNISIG-SUB026-005264#REF# 4.4.20.1.12 #REQ-DESIGN-CR-0353:01#REF#
When receiving a communication session establishment order, the ERTMS/ETCS on-board in Passive Shunting mode shall not establish the
communication session, but shall store the RBC ID/phone number information.
#TEST-VAL-SUB026-5786#REF# FCT basic function Evaluation of communication session establishment order in PS

#REQ-UNISIG-SUB026-005266#REF# 4.4.20.1.13
When in Passive Shunting mode, the ERTMS/ETCS on-board shall not manage RBC-RBC hand-over, except for storing the RBC ID/phone number
information given at the RBC/RBC border.
#TEST-VAL-SUB026-5787#REF# FCT basic function Evaluation of RBC transition order in PS

#REQ-UNISIG-SUB026-005270#REF# 4.4.20.1.15
In case of balise group message consistency error (refer to 3.16.2.4.4 and 3.16.2.5.1), the ERTMS/ETCS onboard equipment shall not command the
service brake.
it's not possible to change to PS
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

Chapter 4.5

TEST APPROACH:
The ETCS mode NP is not realized by the SW refer #REQ-UNISIG-SUB026-004698#REF# and is hence omitted. 
OBU is physically isolated from the brakes in the ETCS mode IS.
OBU does permanently command the Emergency Brakes in the ETCS mode SF.
Balise as well as RBC messages are ignored in IS and SF (refer #REQ-UNISIG-SUB026-3008#REF# and #REQ-UNISIG-SUB026-3009#REF#).
The verification for the modes SF and IS  hence limited to the function marked as active in 4.5.2.
		
#REQ-UNISIG-SUB026-0750:02#REF# 4.5.2.1
X = functions shall be active
Empty case = function shall be inactive
O = Optional (function is not required for interoperability, but is not forbidden)










Figure 1: Active Functions table
realised by: #REQ-UNISIG-SUB026-1010:01#REF#
realised by: #REQ-UNISIG-SUB026-1011:01#REF#
realised by: #REQ-UNISIG-SUB026-1012:02#REF#
realised by: #REQ-UNISIG-SUB026-1013:02#REF#
realised by: #REQ-UNISIG-SUB026-1014:02#REF#
realised by: #REQ-UNISIG-SUB026-1015:02#REF#
realised by: #REQ-UNISIG-SUB026-1116:01#REF#
realised by: #REQ-UNISIG-SUB026-1016:02#REF#
realised by: #REQ-UNISIG-SUB026-1017:02#REF#
realised by: #REQ-UNISIG-SUB026-1018:02#REF#
realised by: #REQ-DESIGN-CR-0019:02#REF#
realised by: #REQ-UNISIG-SUB026-3069:01#REF#
realised by: #REQ-UNISIG-SUB026-1021:01#REF#
realised by: #REQ-UNISIG-SUB026-1022:01#REF#
realised by: #REQ-UNISIG-SUB026-1023:02#REF#
realised by: #REQ-UNISIG-SUB026-010460#REF#
realised by: #REQ-UNISIG-SUB026-1025:02#REF#
realised by: #REQ-UNISIG-SUB026-1026:02#REF#
realised by: #REQ-UNISIG-SUB026-3079:01#REF#
realised by: #REQ-DESIGN-CR-0518:02#REF#
realised by: #REQ-DESIGN-CR-0123:02#REF#
realised by: #REQ-UNISIG-SUB026-1030:01#REF#
realised by: #REQ-UNISIG-SUB026-1031#REF#
realised by: #REQ-DESIGN-CR-0519:01#REF#
realised by: #REQ-UNISIG-SUB026-3653#REF#
realised by: #REQ-UNISIG-SUB026-1032:01#REF#
realised by: #REQ-UNISIG-SUB026-1033:01#REF#
realised by: #REQ-UNISIG-SUB026-3031#REF#
realised by: #REQ-UNISIG-SUB026-3078#REF#
realised by: #REQ-UNISIG-SUB026-1035:01#REF#
realised by: #REQ-UNISIG-SUB026-1036:01#REF#
realised by: #REQ-UNISIG-SUB026-1037:01#REF#
realised by: #REQ-UNISIG-SUB026-1038:02#REF#
realised by: #REQ-UNISIG-SUB026-1039:01#REF#
realised by: #REQ-DESIGN-CR-0147:01#REF#
realised by: #REQ-UNISIG-SUB026-3226#REF#
realised by: #REQ-UNISIG-SUB026-3227#REF#
realised by: #REQ-UNISIG-SUB026-010589#REF#
realised by: #REQ-UNISIG-SUB026-010139#REF#
realised by: #REQ-UNISIG-SUB026-3101#REF#
realised by: #REQ-UNISIG-SUB026-1042:02#REF#
realised by: #REQ-UNISIG-SUB026-1044#REF#
realised by: #REQ-UNISIG-SUB026-1045#REF#
realised by: #REQ-UNISIG-SUB026-1046:01#REF#
realised by: #REQ-UNISIG-SUB026-1047#REF#
realised by: #REQ-UNISIG-SUB026-1048:01#REF#
realised by: #REQ-UNISIG-SUB026-1049:01#REF#
realised by: #REQ-UNISIG-SUB026-1050#REF#
realised by: #REQ-UNISIG-SUB026-1051#REF#
realised by: #REQ-UNISIG-SUB026-1052#REF#
realised by: #REQ-UNISIG-SUB026-010103#REF#
realised by: #REQ-UNISIG-SUB026-1053#REF#
realised by: #REQ-UNISIG-SUB026-1054#REF#
realised by: #REQ-UNISIG-SUB026-1055:01#REF#
realised by: #REQ-UNISIG-SUB026-1056:01#REF#
realised by: #REQ-UNISIG-SUB026-1057:01#REF#
realised by: #REQ-UNISIG-SUB026-1058:02#REF#
realised by: #REQ-DESIGN-CR-0097:02#REF#
realised by: #REQ-DESIGN-CR-0481:02#REF#
realised by: #REQ-UNISIG-SUB026-010388#REF#
realised by: #REQ-UNISIG-SUB026-1061:02#REF#
realised by: #REQ-UNISIG-SUB026-1062:01#REF#
realised by: #REQ-DESIGN-CR-0560:02#REF#
realised by: #REQ-UNISIG-SUB026-1064:01#REF#
realised by: #REQ-UNISIG-SUB026-1065:01#REF#
realised by: #REQ-UNISIG-SUB026-1067:02#REF#
realised by: #REQ-UNISIG-SUB026-1068:02#REF#
realised by: #REQ-UNISIG-SUB026-1070:02#REF#
realised by: #REQ-UNISIG-SUB026-1071:01#REF#
realised by: #REQ-UNISIG-SUB026-010147#REF#
realised by: #REQ-UNISIG-SUB026-010390#REF#
realised by: #REQ-UNISIG-SUB026-010391#REF#
realised by: #REQ-UNISIG-SUB026-010392#REF#
realised by: #REQ-UNISIG-SUB026-010393#REF#
realised by: #REQ-UNISIG-SUB026-010395#REF#

#REQ-UNISIG-SUB026-1010:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-1011:01#REF#
Check linking consistency
active: FS, LS, OS
TEST APPROACH:
The requirement is not relevant for ETCS mode UN, SN, SH, PS, SL, NL, TR, RV. Linking information is deleted when entering these modes. Linking
information is rejected or buffered in L0/LSTM (UN/SN). Linking information is rejected in ETCS mode SH, PS, SL, NL, TR, RV. 
The verification is limited to SB, FS, LS, SR, OS and PT 
#TEST-VAL-SUB026-4718#REF# FCT FS, OS Table 4.5.2 --> Checking linking consistency (FS, OS)
#TEST-VAL-SUB026-4559#REF# FCT LS Mode transition LS->TR[17]
#TEST-VAL-SUB026-4700#REF# FCT SB, PT Checking linking consistency (SB, PT)
#TEST-VAL-SUB026-3961#REF# FCT SR Linking information supervision
#TEST-VAL-SUB026-4844#REF# EET error expectation Linking inforamtion in SR

#REQ-UNISIG-SUB026-1011:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
Check Balise Group Message Consistency if linking consistency is checked
active: FS, LS, OS
Realisierung entsprechend Analyse
realised by: #REQ-DESIGN-CR-0365#REF#
realised by: #REQ-UNISIG-SUB026-0658#REF#
realised by: #REQ-UNISIG-SUB026-1010:01#REF#

#REQ-UNISIG-SUB026-1012:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
Check Balise Group Message Consistency if no linking consistency is checked (because no linking information is available and/or because the
function “check linking consistency is not active)
active: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
Realisierung entsprechend Analyse
realised by: #REQ-DESIGN-CR-0366#REF#
realised by: #REQ-UNISIG-SUB026-3008#REF#

#REQ-UNISIG-SUB026-1013:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
Check Unlinked Balise Group Message Consistency
active: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
Realisierung entsprechend Analyse
realised by: #REQ-DESIGN-CR-0330#REF#
realised by: #REQ-UNISIG-SUB026-3008#REF#

#REQ-UNISIG-SUB026-3008#REF# 4.5.2 #REQ-UNISIG-SUB026-1012:02#REF#
#REQ-UNISIG-SUB026-1013:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
If the train is in the modes SF or IS balise information shall be ignored.
Mit dieser Anforderung wird sichergestellt, dass in diesen Modes keine Konsistenzprüfung stattfindet. In allen anderen Modes findet damit
"automatisch" eine Konsistenzprüfung statt.
#TEST-VAL-SUB026-4570#REF# FCT IS mode transition LS->IS[1], processing Radio/BG message in IS
#TEST-VAL-SUB026-3716#REF# FCT SF Processing Radio/BG message in SF

#REQ-UNISIG-SUB026-1014:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
Check correctness of radio messages
active: SB, SH, PS, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
realised by: #REQ-UNISIG-SUB026-3015:01#REF#
realised by: #REQ-UNISIG-SUB026-3009#REF#

#REQ-UNISIG-SUB026-1015:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
Check radio sequence
active: SB, SH, PS, FS, LS; SR, OS, SL, NL, UN, TR, PT, SN, RV
realised by: #REQ-UNISIG-SUB026-3015:01#REF#
realised by: #REQ-UNISIG-SUB026-3009#REF#

#REQ-UNISIG-SUB026-3009#REF# 4.5.2 #REQ-UNISIG-SUB026-1014:02#REF#
#REQ-UNISIG-SUB026-1015:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
If the train is in the modes SF or IS RBC Messages shall be ignored.
Mit dieser Anforderung wird sichergestellt, dass in diesen Modes keine Konsistenzprüfung stattfindet. In allen anderen Modes findet damit
"automatisch" eine Konsistenzprüfung statt.
#TEST-VAL-SUB026-4570#REF# FCT IS mode transition LS->IS[1], processing Radio/BG message in IS
#TEST-VAL-SUB026-3716#REF# FCT SF Processing Radio/BG message in SF

#REQ-UNISIG-SUB026-1116:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Check safe radio connection (only level 2/3)
active: FS, LS, OS
TEST APPROACH:
The level dependency has to be tested for the active modes only. 
#TEST-VAL-SUB026-4C83#REF# FCT FS (L1), FS (L2) Check radio link (only level 2/3): FS/L1, FS/L2
#TEST-VAL-SUB026-4680#REF# FCT LS (L1) Supervision of safe radio connection in LS
#TEST-VAL-SUB026-4554#REF# FCT LS (L2) mode transition UN->LS(L2)[71]->TR[41]
#TEST-VAL-SUB026-4F03#REF# FCT OS (L1), OS (L2) Check radio link (only level 2/3): OS/L1, OS/L2
#TEST-VAL-SUB026-5942#REF# FCT PS Reception of several LTO in PS, no supervision safe radio connection
#TEST-VAL-SUB026-4D18#REF# FCT RV Check radio link (only level 2/3); RV
#TEST-VAL-SUB026-4D17#REF# FCT SB, SL Check radio link (only level 2/3); SB, SL
#TEST-VAL-SUB026-4D19#REF# FCT SH Check radio link (only level 2/3); SH
#TEST-VAL-SUB026-4D53#REF# FCT SN Check radio link (only level 2/3): SN/STM
#TEST-VAL-SUB026-4D16#REF# FCT SR, NL Check radio link (only level 2/3); SR, NL
#TEST-VAL-SUB026-4D13#REF# FCT TR, PT Check radio link (only level 2/3); TR, PT
#TEST-VAL-SUB026-4D15#REF# FCT UN Check radio link (only level 2/3); UN

#REQ-UNISIG-SUB026-1016:02#REF# 4.5.2 #REQ-UNISIG-SUB026-3726#REF#
#REQ-UNISIG-SUB026-0167#REF#
#REQ-UNISIG-SUB026-3727#REF#
#REQ-UNISIG-SUB026-005248#REF#
#REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0002#REF#
Determine train position referenced to LRBG
active: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
see analysis - evaluation independent from the current mode

realize through 3.6.1.3
realised by: #REQ-UNISIG-SUB026-3354#REF#

#REQ-UNISIG-SUB026-1017:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0003#REF#
Determine train speed, train acceleration, train standstill
active: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
optional: IS

--- FINALISED ---
Die Ermittlung der Orts- und Geschwindigkeitsdaten erfolgt modeunabhängig. Ein Ausschluss in den Modes SF und IS ist insofern nicht notwendig,
da für die Funktionen, die diese Daten nutzen, in der Active Function Table eine separate Einstufung erfolgt.
#ANA-UNISIG-ActiveFunctionTable-0003#REF#
TEST APPROACH:
The function does not depend on the current ETCS mode.
#TEST-VAL-SUB026-4364#REF# ECT basic function PR at level change, standstill in FS, determine train speed and location

#REQ-UNISIG-SUB026-1018:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-DESIGN-CR-0598:01#REF#
Determine Geographical Position
active: SB, FS, LS, SR, OS, NL, UN, TR, PT

--- FINALISED ---
The geographical position information is managed in the same modes as this information can be received (see 4.8.4) and is deleted, when obu
changes in one of the other modes (see 4.10)
There is only one difference. The information can be accepted in SN. But in SN the received geo pos information is only buffered (see 4.8.3)

=> a separate requirement for manage the geographical position information is not necessary.
#TEST-VAL-SUB026-4264#REF# FCT FS, OS Geographical Position Information FS->OS->FS->SH->SB
#TEST-VAL-SUB026-4546#REF# FCT LS GeoPos in LS/L2; L2 FS->LS[72]
#TEST-VAL-SUB026-4458#REF# FCT SN SN/STM acceptance pkt79 GeoPos from BG - LTO L2 on board
#TEST-VAL-SUB026-4265#REF# FCT SR, UN, SB, NL Geographical Position Information FS->SR->UN->SB->NL->SB->SL-SB
#TEST-VAL-SUB026-4266#REF# FCT TR, PT Geographical Position Information FS->TR->PT

#REQ-DESIGN-CR-0019:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3070#REF#
The on-board equipment shall report its train position
if
- train reaches standstill
AND
- the mode is FS, LS, SR, OS or RV
#TEST-VAL-SUB026-4574#REF# FCT LS PR at level, standstill in LS, determine train speed and location in LS
#TEST-VAL-SUB026-4369#REF# FCT NL PR when establishing a session with RBC, determine train speed and location in NL
#TEST-VAL-SUB026-4365#REF# FCT OS PR at level, standstill in OS, determine train speed and location
#TEST-VAL-SUB026-5791#REF# FCT PS Evaluation of P45, system version and session termination order in PS
#TEST-VAL-SUB026-4372#REF# FCT PT PR when establishing a session with RBC, determine train speed and location in PT
#TEST-VAL-SUB026-4363#REF# FCT RV PR at mode change to RV, PR at standstill in RV, determine train speed and location
#TEST-VAL-SUB026-4367#REF# FCT SB PR at level change, when establishing a session with RBC, determine train speed and location
#TEST-VAL-SUB026-4393#REF# FCT SH SB->SH[6] - degraded situation RBC does not order termination of connection
#TEST-VAL-SUB026-4368#REF# FCT SL PR when establishing a session with RBC, determine train speed and location in SL
#TEST-VAL-SUB026-4728#REF# FCT SN SN/STM - PR/MA parameter
#TEST-VAL-SUB026-4314#REF# FCT SR, FS Deletion of level transition order when entering SR
#TEST-VAL-SUB026-4371#REF# FCT TR PR when establishing a session with RBC, determine train speed and location in TR
#TEST-VAL-SUB026-4370#REF# FCT UN PR when establishing a session with RBC, determine train speed and location in UN

#REQ-UNISIG-SUB026-3069:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Report train position when mode changes to ...
inactive: PS

1) For ETCS levels 2 and 3 this may imply establishing a radio communication session if none is established.

2) Exception: the transition PS => SH shall not be reported
The part 1 is realized through 3.5.3.4 c
realised by: #REQ-UNISIG-SUB026-3547:01#REF#
realised by: #REQ-UNISIG-SUB026-1020:01#REF#

#REQ-UNISIG-SUB026-1020:01#REF# 4.5.2 #REQ-UNISIG-SUB026-3071#REF#
#REQ-UNISIG-SUB026-3069:01#REF#
#REQ-DESIGN-CR-0173:01#REF#
#REQ-DESIGN-CR-0181:01#REF#
The on-board equipment shall report its train position, if the mode has changed.

Exceptions:
The change to mode PS shall not be reported.
TEST APPROACH:
The sending of a position report for entering the ETCS mode SB has to be verified for both cases closing and opening the desk.	
#TEST-VAL-SUB026-3339#REF# EET CFX00034819 SR/L2->OS/L2->EoA->TR/L2; Position Report when mode changes
#TEST-VAL-SUB026-4570#REF# FCT IS mode transition LS->IS[1], processing Radio/BG message in IS
#TEST-VAL-SUB026-4550#REF# FCT LS SR mode speed limit and distance when entering LS
#TEST-VAL-SUB026-3047#REF# FCT NL, SL, SB(desk open) Position report at mode change
#TEST-VAL-SUB026-4244#REF# FCT OS transition FS(L2) -> OS(L2-L1) -> SR
#TEST-VAL-SUB026-5944#REF# FCT PS The change to mode PS and the change from PS to SH is not reported via PR
#TEST-VAL-SUB026-4248#REF# FCT PT transition FS(L2) -> TR(L1)[18] -> PT[7] -> SR[37]
#TEST-VAL-SUB026-4363#REF# FCT RV PR at mode change to RV, PR at standstill in RV, determine train speed and location
#TEST-VAL-SUB026-4234#REF# FCT SB (desk closed) transition SB -> SH -> NL in level 0
#TEST-VAL-SUB026-4060#REF# FCT SF Test active functions in mode SF (Pos Report, JRU recording)
#TEST-VAL-SUB026-4393#REF# FCT SH SB->SH[6] - degraded situation RBC does not order termination of connection
#TEST-VAL-SUB026-4241#REF# FCT SN transition FS/L2 - SN/STM - SH/L2
#TEST-VAL-SUB026-4242#REF# FCT SR, FS transition FS -> SR -> FS in level 2
#TEST-VAL-SUB026-4254#REF# FCT TR transition SR(L2) -> SR(L1) -> TR(L1)[65]
#TEST-VAL-SUB026-4251#REF# FCT UN transition FS(L2) -> UN(L0)[21] -> SH[5] -> SB[19]
#TEST-VAL-SUB026-4358#REF# EET error expectation Mode change FS->OS within announced radio hole
#TEST-VAL-SUB026-4628#REF# EET error expectation SR->NL->SB[47]

#REQ-UNISIG-SUB026-1021:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3072#REF#
The on-board equipment shall report its train position
if
- train integrity confirmed by driver
AND
- the mode is SB, FS, LS, SR, OS or PT.
Hinweis an VAL: Nicht testbar, da Train Integrity nicht umgesetzt wird (siehe REQ-SRS-004414). Da intern aber Funktion umgesetzt, wird das Req.
belassen
#ANALYSE-VALUNISIG-5253#REF# FCT Function is not implemented in R8.0 refer #REQ-SRS-004414#REF# and hence not be validated.

#REQ-UNISIG-SUB026-1022:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3073#REF#
The on-board equipment shall report its train position
if
- loss of train integrity is detected
AND
- the mode is SB, FS, LS, SR, OS, TR, PT or RV.
Hinweis an VAL: Nicht testbar, da Train Integrity nicht umgesetzt wird (siehe REQ-SRS-004414). Da intern aber Funktion umgesetzt, wird das Req.
belassen
#ANALYSE-VALUNISIG-4042#REF# FCT Function is not implemented in R8.0 refer #REQ-SRS-004414#REF# and hence not be validated.

#REQ-UNISIG-SUB026-1023:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0004:01#REF#
The on-board equipment shall report its train position,
if
- the train front/rear passes a RBC/RBC border
AND
- the mode is FS, LS, SR, OS, SL, NL or TR.
UNISIG clarification:
see analysis - is realized with line "Manage RBC/RBC Handover"
realised by: #REQ-UNISIG-SUB026-1064:01#REF#

#REQ-UNISIG-SUB026-010460#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3025#REF#
#ANA-UNISIG-ActiveFunctionTable-0021#REF#
The on-board equipment shall report its train position if
- the train has passed a level transition border (from level 2/3 to level 0/STM/1) with its min safe rear end
AND
- the mode is SB, FS, LS, SR, OS, UN, TR, PT or SN.
realizes 3.6.5.1.4 f

UNISIG clarification:the additional condition "with its min safe rear end" is taken over from 3.6.5.1.4 f 

SB, PT and SN are added - see analysis
TEST APPROACH:
The verification for the modes SH and PS can be omitted as level transition orders are not executed in these modes. The verification for the
mode RV can be omitted as pending level transition order is deleted when entering RV and rejected in RV.
#TEST-VAL-SUB026-3616#REF# FCT ->L0, UN level transition L2->L0 RBC does not order termination of connection
#TEST-VAL-SUB026-3617#REF# FCT ->L1, FS level transition L2->L1 RBC does not order termination of connection
#TEST-VAL-SUB026-4H79#REF# FCT ->L1, LS Level transition from LS/L2 to LS/L1
#TEST-VAL-SUB026-7633#REF# FCT ->L1, NL Level transition from NL/L2 to NL/L1
#TEST-VAL-SUB026-4H78#REF# FCT ->L1, OS Level transition from OS/L2 to OS/L1
#TEST-VAL-SUB026-7631#REF# FCT ->L1, PT Level transition from PT/L2 to PT/L1
#TEST-VAL-SUB026-7630#REF# FCT ->L1, SB Level transition from SB/L2 to SB/L1
#TEST-VAL-SUB026-7632#REF# FCT ->L1, SL Level transition from SL/L2 to SL/L1
#TEST-VAL-SUB026-4H80#REF# FCT ->L1, SR Level transition from SR/L2 to SR/L1
#TEST-VAL-SUB026-4H81#REF# FCT ->L1, TR Level transition from TR/L2 to TR/L1
#TEST-VAL-SUB026-5085#REF# FCT ->NTC, SN Level transition von FS/L2 nach SN/STM
#TEST-VAL-SUB026-5484#REF# FCT BG location reference PR for L2->L1 transition - level transition not announced but indicated by border BG

#REQ-UNISIG-SUB026-1025:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-0292#REF#
#REQ-UNISIG-SUB026-0295#REF#
#REQ-UNISIG-SUB026-3594#REF#
#REQ-UNISIG-SUB026-3075#REF#
#ANA-UNISIG-ActiveFunctionTable-0021#REF#
The on-board equipment shall report its train position
when change of level due to trackside order
AND
the mode is SB, FS, LS, SR, OS, NL, TR, PT or SN.
UNISIG clarification:
It is also possible to change a level from trackside without a mode change in SB, PT and SN - see analysis
TEST APPROACH:
The verification for the modes SH and PS can be omitted as level transition orders are not executed in these modes. The verification for the
mode RV can be omitted as pending level transition order is deleted when entering RV and rejected in RV.
A level change in UN does always include a mode change (OBU has to send a PR).
#TEST-VAL-SUB026-4364#REF# FCT FS PR at level change, standstill in FS, determine train speed and location
#TEST-VAL-SUB026-4574#REF# FCT LS PR at level, standstill in LS, determine train speed and location in LS
#TEST-VAL-SUB026-4369#REF# FCT NL PR when establishing a session with RBC, determine train speed and location in NL
#TEST-VAL-SUB026-4365#REF# FCT OS PR at level, standstill in OS, determine train speed and location
#TEST-VAL-SUB026-4329#REF# FCT PT PT/L2 acceptence (Q_DIR evaluation) of Level Transition Order and Position Report Parameters
#TEST-VAL-SUB026-4367#REF# FCT SB PR at level change, when establishing a session with RBC, determine train speed and location
#TEST-VAL-SUB026-5815#REF# FCT SN PR due to level transition in SN
#TEST-VAL-SUB026-4A01#REF# FCT SR PR at level, standstill in SR, determine train speed and location in SR
#TEST-VAL-SUB026-4A04#REF# FCT TR Report train position initiated by track comanded levelchange at Mode TR
#TEST-VAL-SUB026-4246#REF# FCT UN transition FS(L2) -> UN(L0) -> OS(L2)

#REQ-UNISIG-SUB026-1026:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-0287#REF#
#REQ-UNISIG-SUB026-3075#REF#
#ANA-UNISIG-ActiveFunctionTable-0021#REF#
The on-board equipment shall report its train position
when change of level due to driver request
AND
the mode is SB, FS, LS, SR, OS, NL or SN.
UNISIG clarification:
It is also possible to change a level due to driver without a mode change in SN - see analysis
TEST APPROACH:
The requirement is valid for modes were the driver choice change level is available only. The driver choice is available in ETCS modes SB, FS,
LS, SR, OS, NL, UN, SN. A level change in UN does always include a mode change (OBU has to send a PR).
#TEST-VAL-SUB026-3534#REF# EET CFX00034847 Versenden eines Train Position Report (136) bei Wechsel SR/L1 -> SR/L2
#TEST-VAL-SUB026-4A03#REF# FCT FS Report train position initiated by drivers level change at Mode FS
#TEST-VAL-SUB026-4577#REF# FCT LS Manuell level choice and Session Management in LS
#TEST-VAL-SUB026-4244#REF# FCT OS transition FS(L2) -> OS(L2-L1) -> SR
#TEST-VAL-SUB026-4230#REF# FCT SB, NL Report train position when change of level due to driver request and when mode changes in SB
#TEST-VAL-SUB026-5815#REF# FCT SN, UN PR due to level transition in SN
#TEST-VAL-SUB026-4254#REF# FCT SR transition SR(L2) -> SR(L1) -> TR(L1)[65]

#REQ-UNISIG-SUB026-3079:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
The on-board equipment shall report its train position when establishing a session with RBC
AND
the mode is SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN or RV.
UNIISG clarification:
when a session is established successful, a PR must be sended independly from the current mode. The mode dependency is defined only over the
session establishment.
realised by: #REQ-DESIGN-CR-0318#REF#

#REQ-DESIGN-CR-0518:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
The on-board equipment shall report its train position as requested by the RBC Position Report Parameter in the modes
SB, FS, LS, SR, OS, NL, UN, TR, PT, SN or RV.
#TEST-VAL-SUB026-4394#REF# FCT FS, SH, TR Position Report parameters when entering SH/TR
#TEST-VAL-SUB026-4575#REF# FCT LS Position Report parameters when entering / in LS
#TEST-VAL-SUB026-4A08#REF# FCT NL Report train position as requested by RBC on Mode SR and NL
#TEST-VAL-SUB026-4A09#REF# FCT OS Report train position as requested by RBC on Mode OS
#TEST-VAL-SUB026-5954#REF# FCT PS MA request parameter and position report parameter when entering PS
#TEST-VAL-SUB026-4329#REF# FCT PT PT/L2 acceptence (Q_DIR evaluation) of Level Transition Order and Position Report Parameters
#TEST-VAL-SUB026-4397#REF# FCT RV Position Report parameters when entering RV
#TEST-VAL-SUB026-4A07#REF# FCT SB Report train position as requested by RBC at Mode SB ,FS ,TR and PT
#TEST-VAL-SUB026-4368#REF# FCT SL PR when establishing a session with RBC, determine train speed and location in SL
#TEST-VAL-SUB026-4728#REF# FCT SN SN/STM - PR/MA parameter
#TEST-VAL-SUB026-4207#REF# FCT SR MA request and position report parameter when entering SB/SR
#TEST-VAL-SUB026-4897#REF# FCT UN Check table 4.8.3/4.5.2 -> Position report parameters (UN/L0, SN/STM)

#REQ-DESIGN-CR-0123:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-DESIGN-CR-0007#REF#
The on-board equipment shall report its train position at every LRBG compliant balise group passage, if
- no position report parameter are stored on-board
AND
- the mode is FS, LS, SR, OS, NL, UN, TR, PT, SN or RV.
#TEST-VAL-SUB026-3861#REF# FCT FS, OS FS/OS - no position report for not announced BG
#TEST-VAL-SUB026-4549#REF# FCT LS Mode transition L2 SR->LS[72]->SR[37]
#TEST-VAL-SUB026-3860#REF# FCT NL NL - position report when passing single balise BG, no position report for BG with Q_LINK=0
#TEST-VAL-SUB026-3892#REF# FCT PT Train position reporting at LRBG complaint BG (PT)
#TEST-VAL-SUB026-4D01#REF# FCT RV, SL Report train position at every LRBG compliant balise group passage; RV, SL
#TEST-VAL-SUB026-4D00#REF# FCT SB, SH Report train position at every LRBG compliant balise group passage; SH, SB
#TEST-VAL-SUB026-4736#REF# FCT SN SN/STM - PR at every passage of an LRBG compliant balise, System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-3862#REF# FCT SR LS/SR - no position report for not LRBG compliant BG
#TEST-VAL-SUB026-4A11#REF# FCT UN, TR Report Train Position when passing LRBG compliant balise group on Mode SR, UN, TR and PT
#TEST-VAL-SUB026-3864#REF# EET error expectation OBU sends PR LRBG compliant balise group only STM/L0/L1/L2
#TEST-VAL-SUB026-4A10#REF# FCT error expectation Report Train Position when passing LRBG compliant balise group on Mode FS ,OS and NL
#TEST-VAL-SUB040-0029#REF# EET error expectation 2 BGs mit derselben Kombination NID_C/NID_BG

#REQ-UNISIG-SUB026-1030:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Request MA periodicaly with respect to approaching target indication point (T_MAR) or MA timer elapsing (T_TIMEOUTRQST) (only level 2/3)
active: FS, LS, OS
UNISIG clarification: the cyclical sending is stopped, when the active modes are left.
TEST APPROACH:
The cyclic sending of M132 due to approaching target indication point (T_MAR) or MA timer elapsing (T_TIMEOUTRQST) is limited to FS, LS and OS
an appropriated MA is supervised.
The MA request cycle has to be stopped when a the mode changes to any other mode, another level than L2/L3 is entered or the condition for the
MA request is not longer fulfilled due to reception of a new MA.
Following aspects have been identified:
1) FS
1.1) T_MAR
1.2) T_TIMEOUTRQST
2) OS
2.1) T_MAR
2.2) T_TIMEOUTRQST
3) LS
3.1) T_MAR
3.2) T_TIMEOUTRQST
4) MA request cycle stopped due to mode changes 
4.1) SB
4.2) SH
4.3) SR
4.4) NL
4.5) UN
4.6) TR
4.7) SN
4.8) RV
5) MA request cycle stopped due to level changes 
5.1) L1
5.2) NTC
5.3) L0
6) MA request cycle stopped due to reception of new MA
#TEST-VAL-SUB026-3074#REF# FCT 1.1 MA-Requests according to T_MAR
#TEST-VAL-SUB026-3075#REF# FCT 1.2, 6 MA-Requests entsprechend T_TIMEOUTRQST
#TEST-VAL-SUB026-4885#REF# FCT 2.1 MA-Requests according to T_MAR in OS
#TEST-VAL-SUB026-4882#REF# FCT 2.2 MA-Requests according to T_TIMEOUTRQST in OS
#TEST-VAL-SUB026-4677#REF# FCT 3.1 MA-Requests according to T_MAR in LS
#TEST-VAL-SUB026-4676#REF# FCT 3.2 MA-Requests according to T_TIMEOUTRQST in LS
#TEST-VAL-SUB026-4H10#REF# FCT 4.1 Cyclically MA request stopped when entering SR and aborting START procedure
#TEST-VAL-SUB026-4H08#REF# FCT 4.2 Cyclically MA request stopped when entering SH
#TEST-VAL-SUB026-4H05#REF# FCT 4.3 Cyclically MA request stopped when entering SR
#TEST-VAL-SUB026-4H07#REF# FCT 4.4 Cyclically MA request stopped when entering NL
#TEST-VAL-SUB026-4H01#REF# FCT 4.5, 5.3 Cyclically MA request due to T_MAR stopped when entering L0
#TEST-VAL-SUB026-4030#REF# FCT 4.6 Cyclically MA request due to T_OL stopped when entering TR
#TEST-VAL-SUB026-4H02#REF# FCT 4.7, 5.2 Cyclically MA request due to T_OL stopped when entering STM
#TEST-VAL-SUB026-4H06#REF# FCT 4.8 Cyclically MA request stopped when entering RV
#TEST-VAL-SUB026-4H00#REF# FCT 5.1 Cyclically MA request due to T_TIMEOUTRQST stopped when entering L1 (manual level transition)
#TEST-VAL-SUB026-4048#REF# EET error expectation Cyclically MA request due to T_MAR stopped when entering TR
#TEST-VAL-SUB026-4049#REF# EET error expectation Cyclically MA request due to T_TIMEOUTRQST stopped when entering TR
#TEST-VAL-SUB026-4H03#REF# EET error expectation Cyclically MA request due to T_OL stopped when entering L1
#TEST-VAL-SUB026-4H04#REF# EET error expectation MA request due to T_MAR stopped when entering L1

#REQ-UNISIG-SUB026-1031#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Request MA Cyclically when “Start” is selected (only level 2/3)
active: SB, SR, PT
UNISIG clarification: the cyclical sending is stopped, when the active modes or level 2/3 are left.
TEST APPROACH:
Main window with all buttons disabled and hour glass is displayed after selecting START in L2/3 with open session. The driver can cancel the
START procedure by closing the desk only. 
Following aspects have been identified:
Cyclically MA request stopped by:
1) reception of MA
1.1) M2
1.2) M3
2) mode change
3) level change
4) cab closure
#TEST-VAL-SUB026-4521#REF# FCT 1.1 Movement Authority Request Parameters in SR
#TEST-VAL-SUB026-4523#REF# FCT 1.2 Movement Authority Request Parameters in PT
#TEST-VAL-SUB026-4H09#REF# FCT 2 Cyclically MA request with default cycle (A3.1) stopped when entering SR
#TEST-VAL-SUB026-4H11#REF# FCT 3 Cyclically MA request stopped when entering L1
#TEST-VAL-SUB026-4H10#REF# FCT 4 Cyclically MA request stopped when entering SR and aborting START procedure

#REQ-DESIGN-CR-0519:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Request MA on reception of "track ahead free up to the level 2/3 transition location" (only level 0,1,STM)
active: SB, FS, LS, SR, OS, UN, TR, PT, SN
UNISIG clarification:
this MA request is not send cyclically
TEST APPROACH:
The information is accepted in L0, NTC and L1 only no level dependency has to be verified here. 
The function is excluded in the ETCS modes SH/PS/SL/NL/RV as "Track Ahead Free up to level 2/3 transition location" is not a stored information
and rejected in SH//PS/SL/NL/RV refer #REQ-DESIGN-CR-0524:01#REF#
#TEST-VAL-SUB026-4B00#REF# FCT LS Check table 4.5.2/4.8.4 Information->Track ahead free up to leve l2/3 transition location, Mode LS
#TEST-VAL-SUB026-4998#REF# FCT SB, SR, OS Check table 4.5.2/4.8.4 Information->Track ahead free upto level2/3 transition location, Mode-> SB/SR/OS
#TEST-VAL-SUB026-4270#REF# FCT SN Track Ahead Free up to level 2/3 transition location (pkt 90) STM
#TEST-VAL-SUB026-4999#REF# FKT TR, PT Check table 4.5.2/4.8.4 Information->Track ahead free upto level2/3 transition location, Mode-> TR/PT
#TEST-VAL-SUB026-4954#REF# FCT UN, FS Track Ahead Free up to level 2/3 transition location (pkt 90)

#REQ-UNISIG-SUB026-3653#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Request MA on track description deletion
active: FS, LS, OS
UNISIG clarification: the cyclical sending is stopped, when the active modes are left.
TEST APPROACH:
The types of track description which are shortened due to the condition outlined in A3.4 are accepted in FS, LS, OS, SB, SR, PT, UN, and SN.
The track description are stored in the transition buffer in L0 and NTC hence UN and SN can be omitted.
PT can be omitted as the A3.4 conditions are not valid for PT. The recognition of a balise group message consistency error does not lead to the
activation of the SB. All other supervision function are not active in PT.
Hence, the following aspects were identified:
1) MA request triggering
1.1) FS
1.2) LS
1.3) OS
1.4) SB
1.5) SR
2) MA request terminated when changing into a mode where the function is inactive 
3) MA request maintained when changing into a mode where the function is active
#TEST-VAL-SUB026-3588#REF# FCT 1.1, 2 driver manually changes to level 2 communication session to the respective RBC already exists - T_NVCONTACT expiry before
#TEST-VAL-SUB026-4573#REF# FCT 1.2 Movement Authority Request Parameters in LS
#TEST-VAL-SUB026-4522#REF# FCT 1.3 Movement Authority Request Parameters in OS
#TEST-VAL-SUB026-5813#REF# FCT 1.4 No MA request Track description deleted in SB
#TEST-VAL-SUB026-5812#REF# FCT 1.5 No MA request Track description deleted in SR
#TEST-VAL-SUB026-7854#REF# FCT 3 Ongoing MA request to RBC in FS maintained after transition to OS

#REQ-UNISIG-SUB026-1032:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Determine EOA/LOA, SL, Danger Point, etc…
active: FS, LS, OS
TEST APPROACH:
The following MA elements were identified: EoA, LoA, DP and OL. 
When a MA, is received or extracted from buffer, the mode changes to FS, LS or OS. The MA is deleted when entering any other mode. Therefore,
the verification of this requirement focuses on modes FS, LS and OS. 
#TEST-VAL-SUB026-3734#REF# FCT FS - DP DP supervision in FS
#TEST-VAL-SUB026-3735#REF# FCT FS - EoA EoA supervision in FS
#TEST-VAL-SUB026-5226#REF# FCT FS - LoA LoA supervision in FS
#TEST-VAL-SUB026-3738#REF# FCT FS - OL End of overlap supervision in FS
#TEST-VAL-SUB026-3743#REF# FCT LS - DP DP supervision in LS (SvL EBI more restictive than FBI)
#TEST-VAL-SUB026-3744#REF# FCT LS - EoA EoA supervision in LS
#TEST-VAL-SUB026-5228#REF# FCT LS - LoA LoA supervision in LS
#TEST-VAL-SUB026-3746#REF# FCT LS - OL End of overlap supervision in LS
#TEST-VAL-SUB026-3739#REF# FCT OS - DP DP supervision in OS (SvL EBI more restictive than FBI)
#TEST-VAL-SUB026-3740#REF# FCT OS - EoA EoA supervision in OS
#TEST-VAL-SUB026-5227#REF# FCT OS - LoA LoA supervision in OS
#TEST-VAL-SUB026-3742#REF# FCT OS - OL End of overlap supervision in OS
#TEST-VAL-SUB026-3736#REF# EET error expecattion End of overlap supervision in FS
#TEST-VAL-SUB026-3737#REF# EET error expectation DP supervision in FS
#TEST-VAL-SUB026-3741#REF# EET error expectation DP supervision in OS
#TEST-VAL-SUB026-3745#REF# EET error expectation DP supervision in LS

#REQ-UNISIG-SUB026-1033:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0018#REF#
Handle Co-operative MA revocation
active: FS, LS, OS

--- FINALISED ---
Die cooperative MA-Revocation ist keine zu speichernde Information. Sie soll bei Erhalt sofort berücksichtigt werden.
Die Modeabhängigkeite wird demnach von den Filterkriterien bei Empfang vorgegeben. Eine zusätzliche modeabhängige Definition für die
Funktionalität ist nicht notwendig.
#ANA-UNISIG-ActiveFunctionTable-0018#REF#
#TEST-VAL-SUB026-3098#REF# FCT FS Cooperative shortenting of MA
#TEST-VAL-SUB026-4693#REF# FCT LS Request To Shorten MA in LS
#TEST-VAL-SUB026-4D02#REF# FCT OS Handle Co-operative MA revocation; OS

#REQ-UNISIG-SUB026-3031#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0006#REF#
Manage Unconditional Emergency Stop
active: SB, FS, LS, SR, OS, PT

--- FINALISED ---
Funktional wird erwartet, dass eine Emergency Stop Message bzw. eine Revocation eines Emergency Stops mit Empfang ausgewertet werden. Die
Ausführung der Funktion ist damit lediglich abhängig von der Akzeptanz der jeweiligen Nachricht entsprechend der Level-/Mode-Filterkriterien bei
Empfang der Information.
#ANA-UNISIG-ActiveFunctionTable-0006#REF#
TEST APPROACH:
Unconditional Emergency Stop is not accepted in ETCS mode SH, PS, SL, NL, TR, PT and RV.
#TEST-VAL-SUB026-4A51#REF# FCT FS Unconditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-4561#REF# FCT LS mode change LS->TR[20]
#TEST-VAL-SUB026-4A53#REF# FCT OS Unconditional Emergency Stop; UN, OS
#TEST-VAL-SUB026-4651#REF# FCT SB Modewechsel SB->TR[20]
#TEST-VAL-SUB026-4C88#REF# FCT SN Manage Unconditional Emergency Stop: SN/STM
#TEST-VAL-SUB026-4221#REF# FCT SR PT -> SB unconditional emergency stop message deleted
#TEST-VAL-SUB026-4A54#REF# FCT UN Unconditional Emergency Stop (cond [2]); UN, OS

#REQ-UNISIG-SUB026-3078#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0006#REF#
Manage Conditional Emergency Stop
active: FS, LS, OS, PT

--- FINALISED ---
Funktional wird erwartet, dass eine Emergency Stop Message bzw. eine Revocation eines Emergency Stops mit Empfang ausgewertet werden. Die
Ausführung der Funktion ist damit lediglich abhängig von der Akzeptanz der jeweiligen Nachricht entsprechend der Level-/Mode-Filterkriterien bei
Empfang der Information.
#ANA-UNISIG-ActiveFunctionTable-0006#REF#
TEST APPROACH:
Conditional Emergency Stop is not accepted in ETCS mode SB, SH, PS, SR, SL, NL, TR, PT and RV. The verification for UN and SN is omitted as the
information is buffered in L0 and NTC. 
The evaluation of pending ES for the acceptance of information is covered by 4.8.3 condition [5].
Hence, the testing is limited to FS, LS and OS.
#TEST-VAL-SUB026-4A68#REF# FCT FS Conditional Emergency Stop Revocation; FS, OS
#TEST-VAL-SUB026-4F14#REF# FCT LS Manage Conditional Emergency Stop; LS
#TEST-VAL-SUB026-4901#REF# FCT OS Stored Conditional Emergency Stop; FS
#TEST-VAL-SUB026-7855#REF# EET error expectation Management of Conditional Emergency Stop in PT, no EoA supervised, no transition to TR

#REQ-UNISIG-SUB026-1035:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
SSP
active: FS, LS, OS
TEST APPROACH:
The information is deleted when entering any other mode than FS, OS or LS.
The information is accepted in SB, FS, LS, SR, OS, UN, PT and SN. The verification for the ETCS mode UN and SN is omitted, as the information is
buffered in L0 and NTC.
The verification of this requirement is limited to the modes SB, FS, LS, SR, OS, PT.
#TEST-VAL-SUB026-5976#REF# FCT FS Speed and distance supervision function in FS
#TEST-VAL-SUB026-5978#REF# FCT LS Speed and distance supervision function in LS
#TEST-VAL-SUB026-5977#REF# FCT OS Speed and distance supervision function in OS
#TEST-VAL-SUB026-4C18#REF# FCT PT Stored data: MA, GP, International SSP, Axle load SP when changing to TR/L2, PT/L2, FS/L2
#TEST-VAL-SUB026-4C14#REF# FCT SB Stored data: MA, GP, International SSP, Axle load SP when changing to SB/L2, SL/L2, FS/L2
#TEST-VAL-SUB026-4C12#REF# FCT SR Stored data: MA, GP, International SSP, Axle load SP when changing to SR/L2, FS/L2

#REQ-UNISIG-SUB026-1036:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
ASP
active: FS, LS, OS
TEST APPROACH:
The information is deleted when entering any other mode than FS, OS or LS.
The information is accepted in SB, FS, LS, SR, OS, UN, PT and SN. The verification for the ETCS mode UN and SN is omitted as the information is
buffered in L0 and NTC.
The verification of this requirement is limited to the modes SB, FS, LS, SR, OS, PT.
#TEST-VAL-SUB026-5976#REF# FCT FS Speed and distance supervision function in FS
#TEST-VAL-SUB026-5978#REF# FCT LS Speed and distance supervision function in LS
#TEST-VAL-SUB026-5977#REF# FCT OS Speed and distance supervision function in OS
#TEST-VAL-SUB026-4C18#REF# FCT PT Stored data: MA, GP, International SSP, Axle load SP when changing to TR/L2, PT/L2, FS/L2
#TEST-VAL-SUB026-4C14#REF# FCT SB Stored data: MA, GP, International SSP, Axle load SP when changing to SB/L2, SL/L2, FS/L2
#TEST-VAL-SUB026-4C12#REF# FCT SR Stored data: MA, GP, International SSP, Axle load SP when changing to SR/L2, FS/L2

#REQ-UNISIG-SUB026-005297#REF# to.4.5.2
GA (GA profile from trackside)
active: FS, LS, OS
UNISIG clarification: it's not clear, whether the GA profile from trackside is used in SR too.
decision from systemgroup - no is not used outside FS/LS/OS
#TEST-VAL-SUB026-7679#REF# FCT FS, LS, OS The use of Gradient Profile: FS, LS, OS
#TEST-VAL-SUB026-7669#REF# FCT SR The use of Gradient Profile: SR

#REQ-UNISIG-SUB026-1037:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
TSR
active: FS, LS, SR, OS, UN
TEST APPROACH:
The information is deleted when entering any other mode than FS, LS, SR, OS, UN, TR or PT.
The information is accepted in SB, FS, LS, SR, OS, UN, PT and SN. The verification for the ETCS mode SN is omitted as the information is
buffered in NTC.
The verification of this requirement is limited to the ETCS modes SB, FS, LS, SR, OS, UN, TR and PT.
#TEST-VAL-SUB026-5976#REF# FCT FS Speed and distance supervision function in FS
#TEST-VAL-SUB026-5978#REF# FCT LS Speed and distance supervision function in LS
#TEST-VAL-SUB026-5977#REF# FCT OS Speed and distance supervision function in OS
#TEST-VAL-SUB026-4D30#REF# FCT SB TSR: FS, SL
#TEST-VAL-SUB026-5961#REF# FCT SR Speed supervision based on V_TSR, V_NVSTFF and V_NVSUPOVTRP
#TEST-VAL-SUB026-4D34#REF# FCT TR, PT TSR: TR, PT and Delete Revoked TSR: TR, PT
#TEST-VAL-SUB026-5963#REF# FCT UN Speed supervision based on V_TSR, V_NVUNFIT and V_NVSUPOVTRP

#REQ-UNISIG-SUB026-1038:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Signalling related speed restriction when evaluated as a speed limit
active: FS, LS, OS
TEST APPROACH:
The signalling related speed restriction is part is announced via P12 (L1 MA) the acceptance of this information leads to the transition to FS,
LS or OS. The information is deleted when entering any other mode (refer chapter 4.10).
The verification of this requirement is limited to the ETCS modes FS, LS and OS.
#TEST-VAL-SUB026-4F02#REF# FCT FS Signalling related speed restriction: FS/L1, OS/L1
#TEST-VAL-SUB026-4679#REF# FCT LS MA(L1 V_MAIN)/SSP/GP ASP when entering LS
#TEST-VAL-SUB026-4F01#REF# FCT OS Signalling related speed restriction: OS/L1, FS/L1

#REQ-UNISIG-SUB026-1039:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0007#REF#
Mode related speed restriction
active: SH, LS, SR, OS, UN, RV
realised by: #REQ-UNISIG-SUB026-0052:01#REF#
realised by: #REQ-UNISIG-SUB026-3105#REF#
realised by: #REQ-UNISIG-SUB026-3090#REF#
realised by: #REQ-UNISIG-SUB026-3094#REF#
realised by: #REQ-UNISIG-SUB026-3086#REF#
realised by: #REQ-UNISIG-SUB026-3095#REF#
realised by: #REQ-UNISIG-SUB026-3358#REF#

#REQ-DESIGN-CR-0147:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Train related speed restriction
active: FS, LS, SR, OS, UN, RV
for supervision in SH see 
#REQ-BA-Ueberw-0001:02#REF#
TEST APPROACH:
The verification for the ETCS mode TR is omitted as the emergency brake is applied in TR anyway.
#TEST-VAL-SUB026-5976#REF# FCT FS Speed and distance supervision function in FS
#TEST-VAL-SUB026-5978#REF# FCT LS Speed and distance supervision function in LS
#TEST-VAL-SUB026-4441#REF# FCT NL Train data in NL
#TEST-VAL-SUB026-5977#REF# FCT OS Speed and distance supervision function in OS
#TEST-VAL-SUB026-5960#REF# FCT PS No speed supervision in PS
#TEST-VAL-SUB026-4440#REF# FCT RV train data in RV
#TEST-VAL-SUB026-4442#REF# FCT SB, PT train data in TR/PT
#TEST-VAL-SUB026-5695#REF# FCT SH SH the parameterized upper limit for the maximum permitted speed supervised as ceiling speed
#TEST-VAL-SUB026-7856#REF# FCT SL Train data in SL
#TEST-VAL-SUB026-4476#REF# FCT SN SN/STM - Train related speed restriction
#TEST-VAL-SUB026-4A25#REF# FCT SR Determine Most Restrictive Speed Profile, based on Train related SR at Mode SR
#TEST-VAL-SUB026-4A27#REF# FCT UN Determine Most Restrictive Speed Profile, based on Train related speed restriction at Mode UN

#REQ-UNISIG-SUB026-3226#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-1046:01#REF#
#ANA-UNISIG-ActiveFunctionTable-0013#REF#
STM max speed
active: FS, LS, SR, OS, UN, SN
TEST APPROACH:
The information is evaluated within a level transition phase to STM (STM in HS refer SUBSET-035) only.
Level transition order is deleted when entering SB, SH, SR, SL, NL, UN, SN and RV.
The information is rejected/not executed in SH, PS, SL, NL and RV.
The verification of this requirement is limited to the ETCS modes SB, FS, LS, SR, OS, UN, TR, PT and SN. 
#TEST-VAL-SUB026-4474#REF# FCT FS, SN FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4571#REF# FCT LS LS/L2 - STM system speed and distance and STM max speed; LS->SN[56]
#TEST-VAL-SUB026-4481#REF# FCT OS OS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4533#REF# FCT SB SB/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4482#REF# FCT SR SR/L1 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4C97#REF# FCT TR, PT Stored data: STM max speed and STM system speed/distance when entering TR/PT/L2
#TEST-VAL-SUB026-4483#REF# FCT UN UN/L0 - STM system speed and distance and STM max speed

#REQ-UNISIG-SUB026-3227#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0013#REF#
STM system speed
active: FS, LS, SR, OS, UN
TEST APPROACH:
The information is evaluated together with a level transition order to STM.
Level transition order is deleted when entering SB, SH, SR, SL, NL, UN, SN and RV.
The information is rejected in SH, PS, SL, NL, SN and RV.
The verification of this requirement is limited to the ETCS modes SB, FS, LS, SR, OS, UN, TR and PT. 
#TEST-VAL-SUB026-4474#REF# FCT FS FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4571#REF# FCT LS LS/L2 - STM system speed and distance and STM max speed; LS->SN[56]
#TEST-VAL-SUB026-4481#REF# FCT OS OS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4533#REF# FCT SB SB/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4482#REF# FCT SR SR/L1 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4C97#REF# FCT TR, PT Stored data: STM max speed and STM system speed/distance when entering TR/PT/L2
#TEST-VAL-SUB026-4483#REF# FCT UN UN/L0 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4484#REF# EET error expectation SN/STM - STM system speed

#REQ-UNISIG-SUB026-010589#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
LX speed
active: FS, LS, OS
TEST APPROACH:
The information is deleted when entering any other mode than FS, OS or LS.
The information is accepted in SB, FS, LS, SR, OS, UN, PT and SN. The verification for the ETCS mode UN and SN
is omitted as the information is buffered in L0 and NTC.
The verification of this requirement is limited to the modes SB, FS, LS, SR, OS, PT.
#TEST-VAL-SUB026-5976#REF# FCT FS Speed and distance supervision function in FS
#TEST-VAL-SUB026-5978#REF# FCT LS Speed and distance supervision function in LS
#TEST-VAL-SUB026-5977#REF# FCT OS Speed and distance supervision function in OS
#TEST-VAL-SUB026-7654#REF# FCT SR, SB, PT Supervision of LX speed in SR, SB and PT

#REQ-UNISIG-SUB026-010139#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Speed restriction to ensure a given permitted braking distance
active: FS, LS, OS
TEST APPROACH:
Information accepted in SB, FS, LS, SR, OS, PT, UN and SN only
Information buffered in L0/NTC
Information is deleted when entering any other ETCS mode than FS, LS, OS or PT
The verification is hence limited to the ETCS modes SB, SR, PT, RV, FS, LS and OS.
#TEST-VAL-SUB026-3A65#REF# FCT FS PBD Information accepted in mode UN via RBC/L0[2] and supervised in mode FS
#TEST-VAL-SUB026-3A67#REF# FCT LS PBD Information - accepted in UN/L0 (from BG), supervised when in LS/L1
#TEST-VAL-SUB026-3A68#REF# FCT OS PBD Information - accepted in SN/NTC (from BG), supervised when in OS/L1
#TEST-VAL-SUB026-3A71#REF# FCT PT PT/L2: acceptance and supervision of PBD Information from RBC
#TEST-VAL-SUB026-3A78#REF# FCT RV PBD Information in mode RV
#TEST-VAL-SUB026-3A70#REF# FCT SB SB/L2: acceptance of PBD Information from RBC
#TEST-VAL-SUB026-3A69#REF# FCT SR SR/L1 - Acceptance of PBD Information from BG

#REQ-UNISIG-SUB026-3101#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3103#REF#
Override related speed restriction
active: SH, SR, UN
Remark: 
the supervision of NV V_NVSUPOVTRP is meant
TEST APPROACH:
Override can be selected in SB, FS, LS, SR, OS, UN, PT, SN and SH. The activation of override in SB, FS, LS, OS and PT leads to a mode
transition to SR.
Override can be active in the modes SR, SH, UN and SN only. The verification of this requirement is limited to these modes.
#TEST-VAL-SUB026-5962#REF# FCT SH Speed supervision based on V_NVSHUNT and V_NVSUPOVTRP
#TEST-VAL-SUB026-4751#REF# FCT SN SN/STM - V_NVSUPOVTRP, V_NVALLOWOVTRP
#TEST-VAL-SUB026-5961#REF# FCT SR Speed supervision based on V_TSR, V_NVSTFF and V_NVSUPOVTRP
#TEST-VAL-SUB026-5963#REF# FCT UN Speed supervision based on V_TSR, V_NVUNFIT and V_NVSUPOVTRP

#REQ-UNISIG-SUB026-1042:02#REF# 4.5.2 #REQ-UNISIG-SUB026-004877#REF#
#REQ-UNISIG-SUB026-005002#REF#
#REQ-UNISIG-SUB026-3358#REF#
#REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-010417#REF#
Speed and Distance Monitoring based on MRSP, MA, release speed, gradient, mode profile, non protected LX start location, and route unsuitability
location
active: FS, LS, OS
TEST APPROACH:
The aspect route unsuitability location is covered by #REQ-UNISIG-SUB026-1062:01#REF#.
The aspect mode related speed restriction is covered by #REQ-UNISIG-SUB026-0052:01#REF#/#REQ-UNISIG-SUB026-3105#REF#. 
The brake curve calculation has no mode dependency all inputs are evaluated (speed restriction, EoA, SvL and release speed as well as gradient
profile).
#TEST-VAL-SUB026-5976#REF# FCT FS Speed and distance supervision function in FS
#TEST-VAL-SUB026-5978#REF# FCT LS Speed and distance supervision function in LS
#TEST-VAL-SUB026-5977#REF# FCT OS Speed and distance supervision function in OS

#REQ-UNISIG-SUB026-1044#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Speed and distance Monitoring based on MRSP
active: UN
#TEST-VAL-SUB026-5505#REF# FCT basic function Re-activation of Trip inhibition/Supervision of speed when Override aktiv in UN

#REQ-UNISIG-SUB026-1045#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Speed and distance Monitoring based on MRSP, allowed distance to run in Staff Resp. mode
active: SR
#TEST-VAL-SUB026-4C78#REF# FCT basic function Stored data: List of balises for SR + SR speed + SR distance when mode changes to TR/L1, PT/L1

#REQ-UNISIG-SUB026-1046:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Ceiling speed monitoring only (no braking curve) based on MRSP
active: SH, SN, RV
UNISIG clarification:
in SN the supervision of stm max speed is meant

realisiert durch die Anforderungen an die Geschwindigkeitsüberwachung in den konkreten Modes bzw. die Aktivierung von STM max speed supervision.
realised by: #REQ-UNISIG-SUB026-3090#REF#
realised by: #REQ-UNISIG-SUB026-3095#REF#
realised by: #REQ-UNISIG-SUB026-3226#REF#

#REQ-UNISIG-SUB026-1047#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Backwards Distance Monitoring
active: PT, RV
realizes through 4.4.14.1.3 for PT and 4.4.18.1.3 for RV
realised by: #REQ-UNISIG-SUB026-0210:01#REF#
realised by: #REQ-UNISIG-SUB026-3096:02#REF#

#REQ-UNISIG-SUB026-1048:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Roll Away Protection
active: SH, FS, LS, SR, OS, UN, PT, RV
TEST APPROACH:
In modes PS and SL there is no active desk. In mode TR, the EB is applied anyway. In mode SB, the brake is triggered after moving in any
direction for more than D_NVROLL anyway. 
Hence, the verification for these modes is omitted. 
#TEST-VAL-SUB026-4A32#REF# FCT FS Supervise train movements - Roll Away Protection at mode FS
#TEST-VAL-SUB026-4541#REF# FCT LS RAP, RMP and Standstill supervision with service brake
#TEST-VAL-SUB026-8102#REF# FCT NL Roll Away Protection not active in mode NL
#TEST-VAL-SUB026-4A34#REF# FCT OS Supervise train movements - Rollaway Protection in mode OS
#TEST-VAL-SUB026-4531#REF# FCT PT Roll Away Protection in PT
#TEST-VAL-SUB026-4440#REF# FCT RV train data in RV
#TEST-VAL-SUB026-4A31#REF# FCT SH Supervise train movements - Roll Way Protection at mode SH
#TEST-VAL-SUB026-4730#REF# FCT SN SN/STM - no protection against unexpected train movement
#TEST-VAL-SUB026-4A33#REF# FCT SR Supervise train movements - Roll Away Protection in mode SR
#TEST-VAL-SUB026-4A35#REF# FCT UN Supervise train movements - Roll Way Protection at mode UN

#REQ-UNISIG-SUB026-1049:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3089#REF#
Reverse Movement Protection
active: FS, LS, SR, OS, PT, RV
TEST APPROACH:
In modes SB, PS, SH, SL, NL, UN, TR, SN there is no movement authority, and no special case defined for reverse movement. Hence, the
verification for these modes is omitted. 
#TEST-VAL-SUB026-4A37#REF# FCT FS Supervise train movements - Reverse Movement Protection at mode FS
#TEST-VAL-SUB026-4541#REF# FCT LS RAP, RMP and Standstill supervision with service brake
#TEST-VAL-SUB026-4A39#REF# FCT OS Supervise train movements - Reverse Movement Protection at mode OS
#TEST-VAL-SUB026-4A40#REF# FCT PT Supervise train movements - Reverse Movement Protection at mode PT
#TEST-VAL-SUB026-4F65#REF# FCT RV , CFX00079322 Reverse Movement Protection in RV - Supervision based on max safe front RAW end
#TEST-VAL-SUB026-4A38#REF# FCT SR Supervise train movements - Reverse Movement Protection in mode SR
#TEST-VAL-SUB026-2060#REF# EET error expectation RAP / RMP in UN and NL
#TEST-VAL-SUB026-4038#REF# EET error expectation Reverse Movement Protection in PT/L1
#TEST-VAL-SUB026-5653#REF# EET error expectation RMP after switching from PT to SR
#TEST-VAL-SUB026-5654#REF# EET error expectation RMP after switching from PT to OS
#TEST-VAL-SUB026-5655#REF# EET error expectation RMP after switching from PT to FS

#REQ-UNISIG-SUB026-1050#REF# 4.5.2 #REQ-UNISIG-SUB026-3665#REF#
#REQ-UNISIG-SUB026-0750:02#REF#
Standstill Supervision
active: SB
#TEST-VAL-SUB026-4541#REF# FCT SB RAP, RMP and Standstill supervision with service brake

#REQ-UNISIG-SUB026-1051#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Supervise “danger for shunting” information and list of expected balises for shunting
active: SH
TEST APPROACH:
The information danger for shunting is accepted in SH only.
The list of expected balises for shunting is deleted when entering SB, SR, SL, NL, UN, TR, SN, RV and rejected in mode SL, NL, TR, RV. The
information is buffered in buffered in L0 and NTC and hence not relevant for UN and SN.
The list of expected balise for shunting is accepted in combination with a MA or SH authorisation only. The acceptance of one of this
information in SR leads to a mode transition.
The verification of this requirement is limited to the ETCS modes PS, FS, LS, OS, and SH.
#TEST-VAL-SUB026-5959#REF# FCT FS, OS, LS, SH - list of BG in SH Evaluation of List of balises for SH area
#TEST-VAL-SUB026-5985#REF# FCT PS - list of BG in SH List of balises for SH area when entering PS
#TEST-VAL-SUB026-4C76#REF# FCT SH - stop in SH Acceptence of -Danger for SH- and -Stop if in SR- in SH

#REQ-UNISIG-SUB026-1052#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Supervise “Stop if in SR” information and list of expected balises for Staff Responsible
active: SR
TEST APPROACH:
The information Stop if in SR is accepted in SR only.
The list of expected balise for Staff Responsible is deleted when entering any mode apart from SR and accepted in SB, PT and SR only. The list
of expected balise for Staff Responsible is accepted together with SR Authorisation only, which leads to SR.
The verification is hence limited to SR.
#TEST-VAL-SUB026-4023#REF# EET error expectation leere BG-Liste fuer SR
#TEST-VAL-SUB026-4349#REF# FCT list of BG in SR OBU establishes communication session and sends PR due to mode change SR->TR
#TEST-VAL-SUB026-4898#REF# FCT stop in SR Transition table 4.6.3 - Conditions 36, 54

#REQ-UNISIG-SUB026-010103#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ModeTransition-0004#REF#
Supervise signalling related speed restriction when evaluated as a trip order
active: SB, FS, LS, SR, OS

--- FINALISED ---
The trip order is considered during evaluation of a received movement authority (see mode transitions and the exclusion for infill ma in
3.11.6.5). The information has not stored (see 4.10.1.4.2 x) and a later evaluation is not defined. Therefore an extra management of this
information is not necessary.
TEST APPROACH:
The information is accepted in L1 only.
The information is accepted in SB, FS, LS, SR, OS, UN (only buffered), SN(only buffered), PT(4.8.4 PT[1] is not fulfilled in L1).
The verification is limited to the modes SB, FS, LS, SR and OS.
#TEST-VAL-SUB026-4110#REF# FCT FS Mode transition from FS to TR due to trip order
#TEST-VAL-SUB026-4555#REF# FCT LS Mode transition from LS to TR due to trip order
#TEST-VAL-SUB026-4111#REF# FCT OS Mode transition from OS to TR due to trip order
#TEST-VAL-SUB026-5957#REF# FCT SB Reception of MA with V_MAIN=0 in SB
#TEST-VAL-SUB026-4113#REF# FCT SR Mode transition from SR to TR due to trip order

#REQ-UNISIG-SUB026-1053#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0017#REF#
Command Emergency Brake
active: NP, TR, SF
is realized with the concrete requirements for the defined modes
realised by: #REQ-UNISIG-SUB026-3672#REF#
realised by: #REQ-UNISIG-SUB026-0721#REF#
realised by: #REQ-UNISIG-SUB026-0204#REF#

#REQ-UNISIG-SUB026-1054#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Determine ERTMS/ETCS Mode
active: all modes

--- FINALISED ---
The determination of the mode is independent of the current mode. A special requirement with an mode dependency definition is not necessary.
#ANALYSE-VALUNISIG-4806#REF# FCT The evaluation of the ETCS mode is a basic function covered by the verification of the mode transition defined in chapter 4.6.

#REQ-UNISIG-SUB026-1055:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Determine ERTMS/ETCS level
inactive: SF
#ANALYSE-VALUNISIG-4807#REF# FCT The evaluation of the ETCS level is a basic function. The mode level combination is checked in the default start/end condition check of each test case. A separated verification is not needed.

#REQ-UNISIG-SUB026-1056:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#ANA-UNISIG-ActiveFunctionTable-0001#REF#
System Version Management
inactive: SF, IS

--- FINALISED ---
Sowohl der Aufbau einer Session als auch die Auswertung von Balisenmessages sind in den Modes SF und IS nicht möglich.
Aus diesem Grund kann das Versionsmanagement modeunabhängig behandelt werden.
#ANALYSE-VALUNISIG-7453#REF# FCT The management of the System Version Management is not mode dependent.

#REQ-UNISIG-SUB026-1057:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Manage Communication Session
inactive: SF, IS

--- FINALISED ---
Funktional wird erwartet, dass eine bestehende Session unabhängig vom aktuellen Mode gemanagt wird. Die Akzeptanz der Sessionauf- und
–abbaukommandos ist durch die Filterkriterien in  Kap. 4.8, gegeben. Damit ist eine modeabhängige Vorgabe nicht notwendig.
#ANALYSE-VALUNISIG-4090#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-1058:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Delete Revoked TSR
active: SB, FS, LS, SR, OS, UN, TR, PT
Rel. 8.0:
TR is new
--- FINALISED ---
TSR revocation is a non stored information (see 4.10.1.4.2). Therefore the information can be evaluated only directly after receiving.
TEST APPROACH:
A TSR is accepted in SB, FS, LS, SR, OS, UN, TR, PT and SN. A stored TSR is deleted when entering any other mode. 
The verification of TSR revocation is relevant if a valid TSR is available on-board.
The verification for the ETCS mode SN is omitted as the information TSR and TSR revocation are
buffered in NTC.
The verification of this requirement is limited to the ETCS modes SB, FS, LS, SR, OS, UN, TR and PT.
#TEST-VAL-SUB026-4D20#REF# FCT FS, OS TSR + Delete Revoked TSR; FS, OS
#TEST-VAL-SUB026-4551#REF# FCT LS TSR when entering LS, TSR in LS; OS->LS[70]
#TEST-VAL-SUB026-4D29#REF# FCT SR, SB TSR: SR, NL, SB and Delete Revoked TSR: SR, SB
#TEST-VAL-SUB026-4D34#REF# FCT TR, PT TSR: TR, PT and Delete Revoked TSR: TR, PT
#TEST-VAL-SUB026-4D31#REF# FCT UN Delete Revoked TSR: UN

#REQ-DESIGN-CR-0097:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-DESIGN-CR-0034#REF#
Override (Trip inhibition)
active: SH, SR, UN, SN

note: For UN and SN mode, conditions for re-activation of transition to Trip mode (see § 5.8.4.1a) & b)) shall be supervised.
TEST APPROACH:
The activation of override in FS, OS, LS, PT and SB leads to the transition to SR.
The driver choice override is not available PS, NL, SL, TR and RV.
The verification of the override function is limited to the ETCS modes SR, SH, UN and SN.
#TEST-VAL-SUB026-4899#REF# FCT SH Transition table 4.6.3 - Condition 49
#TEST-VAL-SUB026-5518#REF# FCT SN Re-activation of Trip inhibition after Override aktiv in SN
#TEST-VAL-SUB026-4898#REF# FCT SR Transition table 4.6.3 - Conditions 36, 54
#TEST-VAL-SUB026-5505#REF# FCT UN Re-activation of Trip inhibition/Supervision of speed when Override aktiv in UN

#REQ-UNISIG-SUB026-3028#REF# 4.5.2 #ANA-UNISIG-ActiveFunctionTable-0100#REF#
If obu changed to a mode, in which the trip inhibition is not managed (see table 4.5.2, line "Override"), the "override
active" shall be deleted.
TEST APPROACH:
The following modes are identified, where Trip inhibition is not managed: SB, PS< FS< LS, OS, SL, NL, TR, PT, RV. Modes PS and SL are entered
from SB or SH, where override active is already deleted. Mode PT is entered from TR, where override active is already deleted. Mode RV in
entered from modes FS, LS or OS, where override active is already deleted. 
So, the verification for transition to modes PS, SL, PT and RV is omitted. 
#TEST-VAL-SUB026-4685#REF# FCT FS, TR override indication when entering FS/TR
#TEST-VAL-SUB026-4689#REF# FCT LS override indication when entering LS
#TEST-VAL-SUB026-4686#REF# FCT OS, SN override indication when entering OS/SN/SR
#TEST-VAL-SUB026-4684#REF# FCT SB, NL , CFX00037703 override indication when entering SB/NL
#TEST-VAL-SUB026-4688#REF# FCT SH, SR override indication when entering LS, SH, SR
#TEST-VAL-SUB026-4687#REF# FCT UN override indication when entering LS/UN/SR

#REQ-DESIGN-CR-0481:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-DESIGN-CR-0479:03#REF#
Manage Track Conditions excluding Sound Horn, Non Stopping Areas, Tunnel Stopping Areas and Big Metal Masses
active: FS, LS, OS, NL, TR, PT
TEST APPROACH:
The following 'Track Conditions excluding Sound Horn, Non Stopping Areas, Tunnel Stopping Areas and Big Metal Masses' equivalence classes were
identified:
1) TC change of traction
2) TCs in Packet 68 excluding sound horn, tunnel stop and non-stop areas (switch off brakes, radio hole, air tightness, pantograph, main power)

TCs in P40 and P69 are processed as soon as received from trackside (refer #REQ-UNISIG-SUB026-002147#REF#, #REQ-UNISIG-SUB026-002149#). The
verification is done via verification of  #REQ-UNISIG-SUB026-010469#.

Regarding modes UN and SN: when received in these modes, TCs are buffered in LT buffer. When entering these modes, TCs are deleted. Hence, the
verification of these modes is omitted.
Regarding modes PS, SH, SL and RV: when received in these modes, TCs are not accepted. When entering these modes, TCs are deleted. Hence, the
verification of these modes is omitted.
#TEST-VAL-SUB026-4E08#REF# FCT 1) - LS TC Change of Traction Power in LS/L2
#TEST-VAL-SUB026-4972#REF# FCT 1) - OS, FS Check table 4.5.2, 4.8.4, 4.10 TC Change of traction power (FS/OS/NL)
#TEST-VAL-SUB026-7756#REF# FCT 1) - SB TC change of traction power retained in SB and manged after transition to FS
#TEST-VAL-SUB026-5572#REF# FCT 1), 2) - SR, NL TC excl. BMM and sound horn, tunnel and non-stop areas retained in SR, but only processed after transition to NL
#TEST-VAL-SUB026-4B75#REF# FCT 1), 2) - TR, PT Acceptance of track conditions (P68, P39) in mode TR
#TEST-VAL-SUB026-4310#REF# FCT 2) - FS TC Excluding Big Metal Masses PT/SR/FS
#TEST-VAL-SUB026-4583#REF# FCT 2) - LS TC Excluding Big Metal Masses (P68) FS/LS
#TEST-VAL-SUB026-4305#REF# FCT 2) - SB, OS TC Excluding Big Metal Masses FS/SB/OS
#TEST-VAL-SUB026-4974#REF# EET CFX00037056 Check table 4.5.2, 4.8.4, 4.10 Information->TC Change of traction power (TR/PT)
#TEST-VAL-SUB026-4993#REF# EET error expectation Check table 4.5.2 Information->TC Excluding Big Metal Masses (TR - L1, L2, STM)

#REQ-UNISIG-SUB026-3564:01#REF# to.4.5.2 #ANA-UNISIG-ActiveFunctionTable-0015:01#REF#
If the on board unit receives Track Conditions excluding Sound Horn, Non Stopping Areas, Tunnel Stopping Areas and Big Metal Masses in other
modes than FS, LS, OS, NL, TR or PT, these track conditions shall be stored and executed only after a change to FS, LS, OS, NL, TR.

Remark:
The mode change from another mode than TR to PT is not possible.
TEST APPROACH:
The following 'Track Conditions excluding Sound Horn, Non Stopping Areas, Tunnel Stopping Areas and Big Metal Masses' equivalence classes were
identified:
1) TC change of traction
2) TCs in Packet 68 excluding sound horn, tunnel stop and non-stop areas (switch off brakes, radio hole, air tightness, pantograph, main power)

TCs in P40 and P69 are processed as soon as received from trackside (refer #REQ-UNISIG-SUB026-002147#REF#, #REQ-UNISIG-SUB026-002149#). The
verification is done via verification of  #REQ-UNISIG-SUB026-010469#.

Modes where TCs mentioned in 1) and 2) are accepted and not managed are: SB, SR, UN, SN.
Regarding modes UN and SN: when received in these modes, TCs are buffered in LT buffer. When entering these modes, TCs are deleted. Hence, the
verification of these modes is omitted.
Regarding modes SB and SR: 1-wise coverage is provided for the transition from (SR, SB) to (FS, LS, OS, NL, TR).
#TEST-VAL-SUB026-7756#REF# FCT 1) - SB->FS TC change of traction power retained in SB and manged after transition to FS
#TEST-VAL-SUB026-7784#REF# FCT 1) - SB->OS TC Change of Traction System accepted in SB but supervised only after transition to OS
#TEST-VAL-SUB026-5572#REF# FCT 1) - SR->NL TC excl. BMM and sound horn, tunnel and non-stop areas retained in SR, but only processed after transition to NL
#TEST-VAL-SUB026-5573#REF# FCT 1), 2) - SR->LS TC powerless section (pantograph) and traction system accepted in SR, supervised in LS
#TEST-VAL-SUB026-5574#REF# FCT 1), 2) - SR->TR TC powerless section (pantograph) and traction system accepted in SR, supervised in TR
#TEST-VAL-SUB026-7785#REF# FCT 2) - SB->NL TC Powerless section accepted in SB but supervised only after transition to NL
#TEST-VAL-SUB026-4305#REF# FCT 2) - SB->OS TC Excluding Big Metal Masses FS/SB/OS
#TEST-VAL-SUB026-4310#REF# FCT 2) - SR->FS TC Excluding Big Metal Masses PT/SR/FS

#REQ-UNISIG-SUB026-010388#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-010389#REF#
Manage Track Conditions Sound Horn, Non Stopping Areas, Tunnel Stopping Areas
active: FS, LS, OS
TEST APPROACH:
Regarding modes UN and SN: when received in these modes, TCs are buffered in LT buffer. When entering these modes, TCs are deleted. Hence, the
verification of these modes is omitted.
Regarding modes PS, SH, SL and RV: when received in these modes, TCs are not accepted. When entering these modes, TCs are deleted. Hence, the
verification of these modes is omitted.
#TEST-VAL-SUB026-7745#REF# FCT FS Indication of TC 'Tunnel Stopping Area'
#TEST-VAL-SUB026-7746#REF# FCT LS Indication of TC 'Non Stopping Area'
#TEST-VAL-SUB026-7744#REF# FCT NL Handling of TCs Sound Horn, NSA, TSA in modes NL and SB
#TEST-VAL-SUB026-7741#REF# FCT PT Handling of TCs Sound Horn, NSA, TSA in mode PT
#TEST-VAL-SUB026-4830#REF# FCT SB, OS Track condition excluding BMM not executed in SB but after transition to OS
#TEST-VAL-SUB026-7743#REF# FCT SR Handling of TCs Sound Horn, NSA, TSA in modes SR, LS
#TEST-VAL-SUB026-4B75#REF# FCT TR Acceptance of track conditions (P68, P39) in mode TR

#REQ-UNISIG-SUB026-010494#REF# to.4.5.2 #ANA-UNISIG-ActiveFunctionTable-0015:01#REF#
If the on board unit receives Track Conditions Sound Horn, Non Stopping Areas or Tunnel Stopping Areas in other modes than FS, LS, OS, these
track conditions shall be stored and executed only after a change to FS, LS, OS.
TEST APPROACH:
Modes where TCs are accepted and not managed are: SB, SR, NL, UN, TR, PT, SN.
Regarding modes UN and SN: when received in these modes, TCs are buffered in LT buffer. When entering these modes, TCs are deleted. Hence, the
verification of these modes is omitted.
Regarding mode NL, the transition to FS, LS or OS is possible only via modes where TCs are deleted. Hence, the verification of this mode is
omitted.
Regarding mode TR, the only mode transition allowed from this mode is into PT, where TCs are deleted. Hence, the verification of this mode is
omitted.
Regarding modes SB, SR and PT: 1-wise coverage is provided for the transition from (SB, SR, PT) to (FS, LS, OS).
#TEST-VAL-SUB026-7741#REF# FCT PT->FS Handling of TCs Sound Horn, NSA, TSA in mode PT
#TEST-VAL-SUB026-4830#REF# FCT SB->OS Track condition excluding BMM not executed in SB but after transition to OS
#TEST-VAL-SUB026-7743#REF# FCT SR->LS Handling of TCs Sound Horn, NSA, TSA in modes SR, LS

#REQ-UNISIG-SUB026-1061:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Manage Track Condition big metal masses in the following modes:
SB, PS, SH, FS, LS, SR, OS, SL, NL UN, TR, PT, SN
Rel. 8.0:
RV is deleted
TEST APPROACH:
TC BMM is not accepted in mode RV, and deleted when entering mode RV. Hence, the verification of this mode is omitted.
#TEST-VAL-SUB026-4222#REF# FCT FS, OS BMM handling in FS/OS
#TEST-VAL-SUB026-4576#REF# FCT LS BMM handling in FS/LS
#TEST-VAL-SUB026-4227#REF# FCT NL BMM handling in SB/NL
#TEST-VAL-SUB026-5953#REF# FCT PS Evaluation of P67 in PS
#TEST-VAL-SUB026-4225#REF# FCT SB, SH , CFX00036963 BMM handling in SB/SH
#TEST-VAL-SUB026-4228#REF# FCT SL BMM handling in SB/SL
#TEST-VAL-SUB026-4223#REF# FCT SR, TR, PT BMM handling in SR/TR/PT in L1
#TEST-VAL-SUB026-4224#REF# FCT UN, SN BMM handling in UN/SN

#REQ-UNISIG-SUB026-1062:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-010434#REF#
Manage Route Suitability
active: FS, LS, OS
TEST APPROACH:
The information is deleted when entering SB, PS, SH, SR, SL, NL, UN, TR, SN and RV
The information is rejected in PS, SH, SL, NL, TR and RV.
The information is buffered in L0 and NTC.
The verification has to take place for ETCS modes SB, FS, LS, SR, OS and PT.
ETCS modes SB, SR and PT are verified via #REQ-UNISIG-SUB026-010502#REF#.
The verification is limited to ETCS modes FS, LS and OS here.
#TEST-VAL-SUB026-5964#REF# FCT FS FS, SR - Route Suitability Data processing
#TEST-VAL-SUB026-5966#REF# FCT LS LS - Route Suitability Data processing
#TEST-VAL-SUB026-5965#REF# FCT OS OS - Route Suitability Data processing

#REQ-UNISIG-SUB026-010502#REF# to.4.5.2 #ANA-UNISIG-ActiveFunctionTable-0015:01#REF#
If the on board unit receives Route Suitability information in other modes than FS, LS, OS, these Route Suitability information shall be stored
and executed only after a change to FS, LS, OS.
TEST APPROACH:
Following modes have been identified were received Route Suitability information has to be stored for later use:
1) SB
2) SR
3) PT
Note: The information is stored in the level transition buffer in the modes UN and SN.
#TEST-VAL-SUB026-4D71#REF# FCT 1 Acceptance of Route Suitability information: SB/L2
#TEST-VAL-SUB026-7091#REF# FCT 2 Number of Route suitability data memorized on board
#TEST-VAL-SUB026-5968#REF# FCT 3 PT - Route Suitability Data processing

#REQ-DESIGN-CR-0560:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3054#REF#
#REQ-UNISIG-SUB026-3055#REF#
#REQ-UNISIG-SUB026-3056#REF#
#REQ-UNISIG-SUB026-3057#REF#
#ANA-UNISIG-ActiveFunctionTable-0020:01#REF#
Manage Text Display to the driver
active: SB, FS, LS, SR, OS, NL, UN, TR, PT, RV

--- FINALISED ---
Text messages (trackside information, internal text messages, system status messages) are managed independent of the current mode.
TEST APPROACH:
All texts are considered as one equivalence class. One example test case per mode is presented here. 
Verification for modes PS and SL is omitted, as the desk is closed in these modes. 
#TEST-VAL-SUB026-4378#REF# FCT FS text message UN->FS
#TEST-VAL-SUB026-4542#REF# FCT LS text message FS->LS
#TEST-VAL-SUB026-4384#REF# FCT NL text message SB->NL
#TEST-VAL-SUB026-4377#REF# FCT OS text message FS->OS
#TEST-VAL-SUB026-4374#REF# FCT PT text message TR->PT
#TEST-VAL-SUB026-4376#REF# FCT RV text message FS->RV
#TEST-VAL-SUB026-4382#REF# FCT SB text message SB
#TEST-VAL-SUB026-4385#REF# FCT SH text message FS->SH
#TEST-VAL-SUB026-4437#REF# FCT SN text messages from BG in SN/STM
#TEST-VAL-SUB026-4375#REF# FCT SR text message PT->SR
#TEST-VAL-SUB026-4380#REF# FCT TR text message OS->TR
#TEST-VAL-SUB026-4381#REF# FCT UN text message SB->UN
#TEST-VAL-SUB026-4379#REF# EET error expectation text message SR->FS
#TEST-VAL-SUB026-4387#REF# EET error expectation acknowledge plain text SR/TR
#TEST-VAL-SUB026-4388#REF# EET error expectation acknowledge plain text UN/PT
#TEST-VAL-SUB026-4389#REF# EET error expectation acknowledge plain text NL
#TEST-VAL-SUB026-4390#REF# EET error expectation acknowledge plain text OS/RV
#TEST-VAL-SUB026-4545#REF# EET error expectation P76 M_MODETEXTDISPLAY = LS, L2 FS->LS[70]->FS[31]

#REQ-UNISIG-SUB026-1064:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-1023:02#REF#
Manage RBC/RBC Handover
active: FS, LS, SR, OS, SL, NL, TR
TEST APPROACH:
The information RBC/RBC Handover is accepted in level 2/3 only. 
A announced RBC/RBC Handover is deleted when entering modes other than FS, OS or LS (PT can be entered via TR only). 
The information is rejected in RV. 
The RBC ID/phone number given at the RBC/RBC border is stored in SH and PS only.
The aspect reception of RBC transition order in SB and PT is covered by #REQ-UNISIG-SUB026-3140:01#REF#.
The verification of this requirement is limited to the ETCS modes FS, LS, SR, OS, SL, NL and TR.
#TEST-VAL-SUB026-3879#REF# EET CFX00036753 Effect of closing desk during SoM on NationalValues and RBC transitionOrder (two mobiles)
#TEST-VAL-SUB026-4A76#REF# FCT FS Manage RBC Handover; FS - Conditional Emergency Stop within RBC transition buffer
#TEST-VAL-SUB026-4B05#REF# FCT LS Stored RBC Handover; LS
#TEST-VAL-SUB026-4A86#REF# FCT NL Manage RBC Handover; NL
#TEST-VAL-SUB026-4A74#REF# FCT OS Manage RBC Handover; OS
#TEST-VAL-SUB026-4A89#REF# FCT SL (Q_SLEEPSESSION = 0) , CFX00038472 Manage RBC Handover; SL - Q_SLEEPSESSION = 0
#TEST-VAL-SUB026-4A84#REF# FCT SL (Q_SLEEPSESSION = 1) Manage RBC Handover; SL
#TEST-VAL-SUB026-4A78#REF# FCT SR Manage RBC Handover; SR
#TEST-VAL-SUB026-4A80#REF# FCT TR Manage RBC Handover; TR

#REQ-UNISIG-SUB026-3140:01#REF# to.4.5.2 #ANA-UNISIG-ActiveFunctionTable-0014:01#REF#
If the on board unit receives a RBC Handover Transition Order in the modes SB or PT, the information shall be stored and only after a change to
FS, LS or OS this Handover shall be executed.
TEST APPROACH:
The requirement is relevant for transition to FS, OS and LS only. A RBC transition order is deleted when entering any other mode refer
#REQ-DESIGN-DATEN-0022:02#REF#.
#TEST-VAL-SUB026-3462#REF# FCT PT->FS , CFX00036753 RBC transition order stored in PT and executed when entering FS
#TEST-VAL-SUB026-4835#REF# FCT PT->LS , CFX00036753 RBC transition order stored in PT and executed when entering LS
#TEST-VAL-SUB026-8103#REF# FCT PT->OS RBC transition order stored in PT and executed when entering OS
#TEST-VAL-SUB026-4A82#REF# FCT SB->FS RBC transition order stored in SB and evaluated when entering FS
#TEST-VAL-SUB026-8104#REF# FCT SB->LS RBC transition order stored in SB and evaluated when entering LS
#TEST-VAL-SUB026-4B07#REF# FCT SB->OS , CFX00036753 RBC transition order stored in SB and evaluated when entering OS
#TEST-VAL-SUB026-4837#REF# EET error expectation RBC transition order stored in PT not executed when entering SR
#TEST-VAL-SUB026-4838#REF# EET error expectation RBC transition order stored in SB not executed when entering TR

#REQ-UNISIG-SUB026-1065:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-3303#REF#
#REQ-UNISIG-SUB026-3332#REF#
Manage Track Ahead Free Request
active: SB, LS, SR, OS, PT

--- FINALISED ---
The TAF Request is managed in the same modes as this information can be received (see 4.8.4) and is deleted, when obu changes in one of tthe
other modes (see 4.10)
=> a separate requirement for manage the TAF is not necessary.
TEST APPROACH:
The requirement is relevant for the indicated active modes only. Track Ahead Free Request is not accepted in any other mode and deleted when
entering any mode apart from SR/OS.
#TEST-VAL-SUB026-4D61#REF# FCT LS Manage Track Ahead Free request: LS
#TEST-VAL-SUB026-4D40#REF# FCT PT Manage Track Ahead Free request: TR, PT
#TEST-VAL-SUB026-4D37#REF# FCT SB Manage Track Ahead Free request: SB, NL
#TEST-VAL-SUB026-4D35#REF# FCT SR, OS Manage Track Ahead Free request: SR, OS

#REQ-UNISIG-SUB026-1067:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Provide Fixed Values, and Default/National Values
active: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV

--- FINALISED ---
Die Bereitstellung der fixed und national Values erfolgt modeunabhängig. Eventuelle Modeabhängigkeiten werden durch die Funktionen, die diese
Werte benutzen, vorgegeben.
Die Bewertung der National Values in SF und IS ist dadurch ausgeschlossen, dass in diesen Modes keine Balisen und Radio Nachrichten ausgewertet
werden.
#ANALYSE-VALUNISIG-4808#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-1068:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
#REQ-UNISIG-SUB026-010422#REF#
Manage change of Train Data from external sources
active: SB, FS, LS, SR, OS, UN, TR, PT, SN

#REQ-UNISIG-SUB026-1070:02#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Provide Date and Time
active: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV

--- FINALISED ---
The time and date is provided whenever its possible. A mode depenendency makes no sense.
TEST APPROACH:
The requirement does not define a mode dependency refer finalisation.
#TEST-VAL-SUB026-3220#REF# ECT basic function Availability of Time and Date

#REQ-UNISIG-SUB026-1071:01#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Provide Juridical Data
optional: SF, IS
UNISIG clarification:
with version 3.3.0 SF/IS is set to optional. The former requirement (SF activ, IS inactiv) is maintained.
--- FINALISED ---
The juridical recording is executed whenever its possible. A mode dependency makes no sense.
#TEST-VAL-SUB026-4394#REF# FCT FS, SH Position Report parameters when entering SH/TR
#TEST-VAL-SUB026-4570#REF# FCT IS mode transition LS->IS[1], processing Radio/BG message in IS
#TEST-VAL-SUB026-4575#REF# FCT LS Position Report parameters when entering / in LS
#TEST-VAL-SUB026-4395#REF# FCT OS, TR, PT Position Report parameters when entering OS/SR/TR/PT
#TEST-VAL-SUB026-5960#REF# FCT PS No speed supervision in PS
#TEST-VAL-SUB026-4397#REF# FCT RV Position Report parameters when entering RV
#TEST-VAL-SUB026-4060#REF# FCT SF Test active functions in mode SF (Pos Report, JRU recording)
#TEST-VAL-SUB026-4396#REF# FCT SL, SB, NL Position Report parameters when entering SL/NL/SB
#TEST-VAL-SUB026-4728#REF# FCT SN SN/STM - PR/MA parameter
#TEST-VAL-SUB026-4399#REF# FCT SR Position Report parameters when entering FS
#TEST-VAL-SUB026-4398#REF# FCT UN Position Report parameters when entering FS(L2)/UN/FS(L1)

#REQ-UNISIG-SUB026-010147#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Inhibition of revocable TSRs from balises(only level 2/3)
active: FS, LS, OS, TR, PT
TEST APPROACH:
The information is accepted in SB, FS, LS, SR, OS, UN, TR, PT, SN only.
The information is buffered in L0 and NTC.
The information is deleted when entering any other ETCS mode than FS, LS, OS, TR or PT.
The verification is hence limited to the ETCS modes SB, FS, LS, SR, OS, TR and PT.
#TEST-VAL-SUB026-5818#REF# FCT FS Inhibition of revocable TSRs from balises in L2/3 deleted due to session termination
#TEST-VAL-SUB026-5826#REF# FCT LS Inhibition of revocable TSRs from balises in L2/3 in LS
#TEST-VAL-SUB026-5825#REF# FCT OS Inhibition of revocable TSRs from balises in L2/3 in OS
#TEST-VAL-SUB026-5828#REF# FCT PT Inhibition of revocable TSRs from balises in L2/3 in PT
#TEST-VAL-SUB026-5830#REF# FCT SB Inhibition of revocable TSRs from balises in L2/3 in SB
#TEST-VAL-SUB026-5829#REF# FCT SR Inhibition of revocable TSRs from balises in L2/3 in SR
#TEST-VAL-SUB026-5827#REF# FCT TR Inhibition of revocable TSRs from balises in L2/3 in TR

#REQ-UNISIG-SUB026-010390#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Cold Movement Detection
optional: NP

#REQ-UNISIG-SUB026-010391#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Continue Shunting on desk closure (Enabling transition to Passive Shunting mode)
active: SH
is realized with 4.4.20.1.7
realised by: #REQ-UNISIG-SUB026-005254#REF#

#REQ-UNISIG-SUB026-010392#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Manage “Stop Shunting on desk opening” information
active: PS
the use of this information is defined in 4.4.20 and the mode transitions [22] and [23] from PS
realised by: #REQ-UNISIG-SUB026-010225#REF#
realised by: #REQ-UNISIG-SUB026-010226#REF#

#REQ-UNISIG-SUB026-010393#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Manage Virtual Balise Covers
optional: SF, IS

--- FINALISED ---
In SF and IS are ignored balise information (see #REQ-UNISIG-SUB026-3008#REF#). Therefore a special definition for this function is not
necessary in these modes.
TEST APPROACH:
The requirement does not define a mode dependency.

#REQ-UNISIG-SUB026-010395#REF# 4.5.2 #REQ-UNISIG-SUB026-0750:02#REF#
Advance display of route related information
optional: FS
is also defined in ERA SRS DMI (see chapter 8.3)

Chapter 4.6

TEST APPROACH:
L2 and L3 are taken into account as one equivalence class for the verification of mode transitions 
		
#REQ-UNISIG-SUB026-0247:01#REF# 4.6.2- #REQ-UNISIG-SUB026-3337#REF#


Figure 2: Transition table.

--- FINALISED ---
The application software cannot changed into the mode No Power(see #REQ-UNISIG-SUB026-004698#REF# and the realization of this requirement).
Therefore all transitions to NP including the condition[29] are not relevant for the application software.

------
Transition table:
transiton from PS to SF
"13>" with priority "-p3-"

This transition is not possible due to 4.4.20.1.10.
realised by: #REQ-UNISIG-SUB026-2212#REF#
realised by: #REQ-UNISIG-SUB026-010396#REF#
realised by: #REQ-DESIGN-CR-0399#REF#
realised by: #REQ-DESIGN-CR-0400#REF#
realised by: #REQ-UNISIG-SUB026-3500#REF#
realised by: #REQ-DESIGN-CR-0401#REF#
realised by: #REQ-DESIGN-CR-0402#REF#
realised by: #REQ-DESIGN-CR-0406#REF#
realised by: #REQ-DESIGN-CR-0407#REF#
realised by: #REQ-DESIGN-CR-0403#REF#
realised by: #REQ-DESIGN-CR-0036:01#REF#
realised by: #REQ-UNISIG-SUB026-2224#REF#
realised by: #REQ-UNISIG-SUB026-2226#REF#
realised by: #REQ-DESIGN-CR-0405#REF#
realised by: #REQ-UNISIG-SUB026-010234#REF#
realised by: #REQ-UNISIG-SUB026-010235#REF#
realised by: #REQ-UNISIG-SUB026-010236#REF#
realised by: #REQ-UNISIG-SUB026-010238#REF#
realised by: #REQ-UNISIG-SUB026-005322#REF#
realised by: #REQ-UNISIG-SUB026-010239#REF#
realised by: #REQ-UNISIG-SUB026-2231#REF#
realised by: #REQ-UNISIG-SUB026-2232#REF#
realised by: #REQ-UNISIG-SUB026-2234#REF#
realised by: #REQ-UNISIG-SUB026-2235#REF#
realised by: #REQ-UNISIG-SUB026-2297#REF#
realised by: #REQ-UNISIG-SUB026-2298#REF#
realised by: #REQ-UNISIG-SUB026-3501#REF#
realised by: #REQ-UNISIG-SUB026-2299#REF#
realised by: #REQ-UNISIG-SUB026-2330#REF#
realised by: #REQ-UNISIG-SUB026-2331#REF#
realised by: #REQ-UNISIG-SUB026-2332#REF#
realised by: #REQ-DESIGN-CR-0037:01#REF#
realised by: #REQ-UNISIG-SUB026-2292#REF#
realised by: #REQ-UNISIG-SUB026-2293#REF#
realised by: #REQ-UNISIG-SUB026-2295#REF#
realised by: #REQ-UNISIG-SUB026-2296#REF#
realised by: #REQ-UNISIG-SUB026-3371#REF#
realised by: #REQ-UNISIG-SUB026-3372#REF#
realised by: #REQ-UNISIG-SUB026-3373#REF#
realised by: #REQ-UNISIG-SUB026-3374#REF#
realised by: #REQ-UNISIG-SUB026-3375:01#REF#
realised by: #REQ-UNISIG-SUB026-3376#REF#
realised by: #REQ-UNISIG-SUB026-3377#REF#
realised by: #REQ-UNISIG-SUB026-3378:01#REF#
realised by: #REQ-UNISIG-SUB026-3379#REF#
realised by: #REQ-UNISIG-SUB026-3380#REF#
realised by: #REQ-UNISIG-SUB026-3381#REF#
realised by: #REQ-UNISIG-SUB026-3382#REF#
realised by: #REQ-UNISIG-SUB026-2270#REF#
realised by: #REQ-DESIGN-CR-0113#REF#
realised by: #REQ-DESIGN-CR-0592#REF#
realised by: #REQ-UNISIG-SUB026-3502#REF#
realised by: #REQ-DESIGN-CR-0103#REF#
realised by: #REQ-UNISIG-SUB026-2271#REF#
realised by: #REQ-UNISIG-SUB026-2272#REF#
realised by: #REQ-DESIGN-CR-0461#REF#
realised by: #REQ-UNISIG-SUB026-2274#REF#
realised by: #REQ-UNISIG-SUB026-2275#REF#
realised by: #REQ-UNISIG-SUB026-2277#REF#
realised by: #REQ-UNISIG-SUB026-2278#REF#
realised by: #REQ-UNISIG-SUB026-2279#REF#
realised by: #REQ-DESIGN-CR-0593#REF#
realised by: #REQ-UNISIG-SUB026-3503:01#REF#
realised by: #REQ-UNISIG-SUB026-2280#REF#
realised by: #REQ-UNISIG-SUB026-2281#REF#
realised by: #REQ-UNISIG-SUB026-2282#REF#
realised by: #REQ-DESIGN-CR-0039:01#REF#
realised by: #REQ-UNISIG-SUB026-2283#REF#
realised by: #REQ-UNISIG-SUB026-2287#REF#
realised by: #REQ-UNISIG-SUB026-2289#REF#
realised by: #REQ-UNISIG-SUB026-2290#REF#
realised by: #REQ-UNISIG-SUB026-2236#REF#
realised by: #REQ-UNISIG-SUB026-2238#REF#
realised by: #REQ-UNISIG-SUB026-2239#REF#
realised by: #REQ-UNISIG-SUB026-2241#REF#
realised by: #REQ-DESIGN-CR-0337#REF#
realised by: #REQ-DESIGN-CR-0340#REF#
realised by: #REQ-DESIGN-CR-0341#REF#
realised by: #REQ-UNISIG-SUB026-3504#REF#
realised by: #REQ-DESIGN-CR-0335:01#REF#
realised by: #REQ-DESIGN-CR-0342#REF#
realised by: #REQ-DESIGN-CR-0336:01#REF#
realised by: #REQ-UNISIG-SUB026-2247#REF#
realised by: #REQ-UNISIG-SUB026-2246#REF#
realised by: #REQ-DESIGN-CR-0339#REF#
realised by: #REQ-UNISIG-SUB026-007068#REF#
realised by: #REQ-UNISIG-SUB026-2250:01#REF#
realised by: #REQ-UNISIG-SUB026-2252#REF#
realised by: #REQ-UNISIG-SUB026-2254#REF#
realised by: #REQ-UNISIG-SUB026-2255#REF#
realised by: #REQ-UNISIG-SUB026-2259#REF#
realised by: #REQ-DESIGN-CR-0013#REF#
realised by: #REQ-DESIGN-CR-0130#REF#
realised by: #REQ-DESIGN-CR-0016#REF#
realised by: #REQ-UNISIG-SUB026-3505#REF#
realised by: #REQ-DESIGN-CR-0015#REF#
realised by: #REQ-DESIGN-CR-0014#REF#
realised by: #REQ-UNISIG-SUB026-2260#REF#
realised by: #REQ-UNISIG-SUB026-2261#REF#
realised by: #REQ-UNISIG-SUB026-2262#REF#
realised by: #REQ-DESIGN-CR-0378#REF#
realised by: #REQ-DESIGN-CR-0498:01#REF#
realised by: #REQ-DESIGN-CR-0379#REF#
realised by: #REQ-UNISIG-SUB026-3506#REF#
realised by: #REQ-DESIGN-CR-0376#REF#
realised by: #REQ-DESIGN-CR-0380#REF#
realised by: #REQ-DESIGN-CR-0539#REF#
realised by: #REQ-DESIGN-CR-0377:02#REF#
realised by: #REQ-UNISIG-SUB026-2264#REF#
realised by: #REQ-UNISIG-SUB026-2266#REF#
realised by: #REQ-UNISIG-SUB026-2267#REF#
realised by: #REQ-UNISIG-SUB026-2268#REF#
realised by: #REQ-UNISIG-SUB026-2269#REF#

#REQ-UNISIG-SUB026-2212#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from NP to SB
"4>" with priority "-p2-"

note: The mode Stand By is the initial mode, when the ERTMS/ETCS on-board equipment power up.
#TEST-SWHWINT-STARTUP-0019#REF# FCT basic function Hochlauf mit Fahrt Level 1 über reale Teilstrecke

#REQ-UNISIG-SUB026-010396#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from NP to IS
"1>" with priority "-p1-"

--- FINALISED ---
The transition from NP to IS is'nt realized in the application software, because the change to IS is realized outside the EVC via hardware.
A transition from NP to IS is therefore not possible.
#ANALYSE-VALUNISIG-4814#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-DESIGN-CR-0399#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to SH
"5, 6, 50>" with priority "-p7-"
#TEST-VAL-SUB026-4112#REF# FCT [50] SOM - L2/SH
#TEST-VAL-SUB026-4291#REF# FCT [5] L0 SoM stored level L0, valid RBC data and location, to SH/L0 (E12)
#TEST-VAL-SUB026-4235#REF# FCT [5] L1 transition SB -> SH -> TR [49] in level 1
#TEST-VAL-SUB026-5788#REF# FCT [5] NTC Mode transition from SN(HS) to SH
#TEST-VAL-SUB026-4393#REF# FCT [6] SB->SH[6] - degraded situation RBC does not order termination of connection

#REQ-DESIGN-CR-0400#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to FS
"10>" with priority "-p7-"
#TEST-VAL-SUB026-5406#REF# FCT [10] SOM - L2/FS

#REQ-UNISIG-SUB026-3500#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SB to LS
"70>" with priority "-p7-"
#TEST-VAL-SUB026-4558#REF# FCT [70] linking information when entering LS, L2 LS->SB[28]->LS[70]->TR[66] ->PT->LS[70]

#REQ-DESIGN-CR-0401#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to SR
"8, 37>" with priority "-p7-"
#TEST-VAL-SUB026-4600#REF# FCT [37] Mode change SB->SR [37]
#TEST-VAL-SUB026-3669#REF# FCT [8] Train location data - nominal/revers of LRBG

#REQ-DESIGN-CR-0402#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to OS
"15>" with priority "-p7-"
#TEST-VAL-SUB026-4288#REF# FCT [15] Last reported balise group identities transition FS(L2)-> RV(L2)-> SB(L2) -> OS(L2) ->FS(L2)

#REQ-DESIGN-CR-0406#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to SL
"14>" with priority "-p5-"
#TEST-VAL-SUB026-4205#REF# EET CFX00175725, CFX00035450 Modechange FS -> SB -> SL
#TEST-VAL-SUB026-4233#REF# FCT [14] transition SB-> SL in level 0

#REQ-DESIGN-CR-0407#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to NL
"46>" with priority "-p6-"
#TEST-VAL-SUB026-4232#REF# FCT [46] transition SB-> NL in level 0

#REQ-DESIGN-CR-0403#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to UN
"60>" with priority "-p7-"
#TEST-VAL-SUB026-5402#REF# FCT [60] SOM - L0/UN

#REQ-DESIGN-CR-0036:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#ANA-UNISIG-ModeTransition-0004#REF#
Transition table:
transiton from SB to TR
"18, 20>" with priority "-p4-"
UNISIG clarification:
condition[18] is added on - see analysis
#TEST-VAL-SUB026-5957#REF# FCT [18] Reception of MA with V_MAIN=0 in SB
#TEST-VAL-SUB026-4651#REF# FKT [20] Modewechsel SB->TR[20]

#REQ-UNISIG-SUB026-2224#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4004#REF# FCT [13] Mode transition SB->SF

#REQ-UNISIG-SUB026-007715:01#REF# 4.6.2 #REQ-OBU_SRS-Modes-0001:02#REF#
#ANA-UNISIG-ModeTransition-0002:01#REF#
In case of a safety critical fault during startup the change from mode SB to mode SL shall have higher priority than the change to mode SF
during a parameterizable delay time.

Note: To deactivate this functionality, the delay can be set to a special value (e.g. zero).
TEST APPROACH:
The following aspects have been identified:
1) delay timer expires while in mode SL
2) delay timer expires while in mode different than SL
3) functionality disabled
#TEST-VAL-SUB026-5292#REF# FCT 1 Start up with fault that effects safety: delay timer expires while in mode SL
#TEST-VAL-SUB026-7636#REF# FCT 2 Start up with fault that effects safety: delay timer expires while in mode different than SL
#TEST-VAL-SUB026-7637#REF# FCT 3 Start up with fault that effects safety: inhibition of SF is deactivated

#REQ-UNISIG-SUB026-2226#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4200#REF# EET CFX00034635 Kein RKS wenn im IS Mode die Start of mission betaetigt wird (SB->IS)
#TEST-VAL-SUB026-4601#REF# FCT [1] Modewechsel SB->IS [1]

#REQ-DESIGN-CR-0405#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SB to SN
"58>" with priority "-p7-"
#TEST-VAL-SUB026-4949#REF# FCT [58] Transition from SB to SN

#REQ-UNISIG-SUB026-010234#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from PS to SB
"22>" with priority "-p4-"
it's not possible to change to PS and so leaves PS too.
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-010235#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from PS to SH
"23>" with priority "-p4-"
it's not possible to change to PS and so leaves PS too.
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-010236#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from PS to SL
"14>" with priority "-p4-"
it's not possible to change to PS and so leaves PS too.
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-010238#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from PS to IS
"1>" with priority "-p1-"
it's not possible to change to PS and so leaves PS too.
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-005322#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SH to SB
"19, 27, 30>" with priority "-p5-"
the PS functionality isn't realized => the previsous conditions for transition from SH to SB are remain valid
realised by: #REQ-UNISIG-SUB026-2228#REF#

#REQ-UNISIG-SUB026-2228#REF# 4.6.2 #REQ-UNISIG-SUB026-005322#REF#
Transition table:
transiton from SH to SB
"19, 28>" with priority "-p5-"
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#. Condition [30] is hence not relevant for R8.0 and condition [27] is similar to [28].
#TEST-VAL-SUB026-7135#REF# EET CFX00033834 Mode transition SR->SH[6](override active) SH->SB[19]
#TEST-VAL-SUB026-4480#REF# EET CFX00035026 SN/STM acceptance MP-SH - LTO L2 onboard
#TEST-VAL-SUB026-7134#REF# FCT [19] mode transition SR(L1) -> SH[5] -> SB[19]
#TEST-VAL-SUB026-4231#REF# FCT [27] transition SB -> SH -> SB in level 0

#REQ-UNISIG-SUB026-010239#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SH to PS
"26>" with priority "-p5-"
it's not possible to change to PS and so leaves PS too.
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-2231#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SH to NL
"46>" with priority "-p5-"
#TEST-VAL-SUB026-4234#REF# FCT [46] transition SB -> SH -> NL in level 0

#REQ-UNISIG-SUB026-2232#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SH to TR
"49, 52, 65>" with priority "-p4-"
#TEST-VAL-SUB026-4013#REF# FCT [49] Baliseninformation 'Stop if in Shunting'
#TEST-VAL-SUB026-4105#REF# FCT [52] Listen von BGs im SH-Bereich
#TEST-VAL-SUB026-4878#REF# FCT [65] L1 Balise telegram with a non compatible version of the ERTMS/ETCS language received SH/L1
#TEST-VAL-SUB026-5412#REF# FCT [65] L2 SH overrive EoA active when receiving balise telegram with a non compatible version
#TEST-VAL-SUB026-8111#REF# EET error expectation Acceptance of Danger for Shunting: level NTC

#REQ-UNISIG-SUB026-2234#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SH to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4605#REF# FCT [13] Mode change SH->SF[13]

#REQ-UNISIG-SUB026-2235#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SH to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4606#REF# FCT basic function Modewechsel SH->IS [1]

#REQ-UNISIG-SUB026-2297#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from FS to SB
"28>" with priority "-p5-"
#TEST-VAL-SUB026-4238#REF# FCT [28] Report train position when change of level due to driver request and when mode changes FS -> SB (L1)

#REQ-UNISIG-SUB026-2298#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from FS to SH
"5, 6, 50, 51>" with priority "-p6-"
Level 0 and STM (NTC) in condition[5] are not relevant for this transition
#TEST-VAL-SUB026-5000#REF# FCT [50] FS->SH
#TEST-VAL-SUB026-3141#REF# FCT [51] Start and end of mode profile
#TEST-VAL-SUB026-4607#REF# FCT [5] Mode transition FS->SH [5]
#TEST-VAL-SUB026-5011#REF# FCT [6] Shunting initiated by driver L2, FS

#REQ-UNISIG-SUB026-3501#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from FS to LS
"70, 72>" with priority "-p6-"
#TEST-VAL-SUB026-4544#REF# FCT 70 Pkt 72 M_MODETEXTDISPLAY = LS, L1 FS->LS[70]->FS[32]
#TEST-VAL-SUB026-4546#REF# FCT [72] GeoPos in LS/L2; L2 FS->LS[72]

#REQ-UNISIG-SUB026-2299#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from FS to SR
"37>" with priority "-p6-"
#TEST-VAL-SUB026-4980#REF# FCT [37] Transition Table 4.6.3 OS->FS[32]->SR[37]->FS[31]->SR[37]->TR[54]

#REQ-UNISIG-SUB026-2330#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from FS to OS
"15, 40>" with priority "-p6-"
#TEST-VAL-SUB026-4239#REF# FCT [15] transition FS -> OS in level 1
#TEST-VAL-SUB026-4240#REF# FCT [40] transition FS -> OS in level 1 condition [40]

#REQ-UNISIG-SUB026-2331#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from FS to NL
"46>" with priority "-p6-"
#TEST-VAL-SUB026-4341#REF# FCT [46] OBU establishes communication session and sends PR due to mode change FS->NL

#REQ-UNISIG-SUB026-2332#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from FS to UN
"21>" with priority "-p6-"
#TEST-VAL-SUB026-5138#REF# EET CFX00035330 Level transition L2->L0, EoA ends at level transition border
#TEST-VAL-SUB026-4121#REF# FCT [21] Mode transition from FS to UN

#REQ-DESIGN-CR-0037:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from FS to TR
"12, 16, 17, 18, 20, 41, 65, 66, 69>" with priority "-p4-"
#TEST-VAL-SUB026-4588#REF# FCT [12] EoA supervision - MA with OL on board FS/L1
#TEST-VAL-SUB026-3159#REF# FCT [16] Transition to TR at EOA/LOA
#TEST-VAL-SUB040-0031#REF# FCT [17] Processing of infill linking information from unlinked BG
#TEST-VAL-SUB026-4110#REF# FCT [18] Mode transition from FS to TR due to trip order
#TEST-VAL-SUB026-4880#REF# FCT [20] Deletion of unconditional EmergencyStop on entry into SN
#TEST-VAL-SUB026-3197#REF# FCT [41] NVCONTACT supervision, M_NVCONTACT=0 - Train trip
#TEST-VAL-SUB026-8105#REF# FCT [65] L1 Balise telegram with a non compatible version of the ERTMS/ETCS language received: FS/L1
#TEST-VAL-SUB026-3206#REF# FCT [65] L2 BG with unsupported M_VERSION: transition into TR
#TEST-VAL-SUB026-3175#REF# FCT [66] passage of announced BG in wrong direction
#TEST-VAL-SUB026-7087#REF# FCT [69] GP Deletion of accepted and stored information when used GP
#TEST-VAL-SUB026-7086#REF# FCT [69] SSP Deletion of accepted and stored information when used SSP
#TEST-VAL-SUB026-4157#REF# EET error expectation Passage of BG with TRIP order while overlap timer (T_OL infinite) running
#TEST-VAL-SUB026-4258#REF# FCT error expectation transition FS/L1 -> TR/L0 [18]; (FS->UN p6)<(FS->TR p4)

#REQ-UNISIG-SUB026-2292#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from FS to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4812#REF# FCT [13] mode change FS->SF[13] due to reception of overlapping MP OS/SH

#REQ-UNISIG-SUB026-2293#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from FS to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4609#REF# FCT [1] Modewechsel FS->IS [1]

#REQ-UNISIG-SUB026-2295#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from FS to SN
"56>" with priority "-p6-"
#TEST-VAL-SUB026-4286#REF# FCT [56] acceptance of radio message with former LRBG FS, SN, TR, PT

#REQ-UNISIG-SUB026-2296#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from FS to RV
"59>" with priority "-p6-"
#TEST-VAL-SUB026-3169#REF# FCT [59] Reversing

#REQ-UNISIG-SUB026-3371#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to SB
"28>" with priority "-p5-"
#TEST-VAL-SUB026-4558#REF# FCT [28] linking information when entering LS, L2 LS->SB[28]->LS[70]->TR[66] ->PT->LS[70]

#REQ-UNISIG-SUB026-3372#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-UNISIG-SUB026-3532#REF#
Transition table:
transition from LS to SH
"5, 6, 50, 51>" with priority "-p6-"
#TEST-VAL-SUB026-4567#REF# FCT [50] mode change LS->SH[50]
#TEST-VAL-SUB026-4566#REF# FCT [51] mode change LS->SH[51]
#TEST-VAL-SUB026-4572#REF# FCT [5] Mode transition LS->SH[5]
#TEST-VAL-SUB026-4565#REF# FCT [6] mode change LS->SH[6]
#TEST-VAL-SUB026-4569#REF# EET error expectation mode change LS->SH[51]

#REQ-UNISIG-SUB026-3373#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-UNISIG-SUB026-3532#REF#
Transition table:
transition from LS to FS
"31, 32>" with priority "-p6-"
#TEST-VAL-SUB026-4545#REF# FCT [31] P76 M_MODETEXTDISPLAY = LS, L2 FS->LS[70]->FS[31]
#TEST-VAL-SUB026-4544#REF# FCT [32] Pkt 72 M_MODETEXTDISPLAY = LS, L1 FS->LS[70]->FS[32]

#REQ-UNISIG-SUB026-3374#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to SR
"37>" with priority "-p6-"
#TEST-VAL-SUB026-4548#REF# FCT [37] Mode transition L1 SR->LS[72]->SR[37]

#REQ-UNISIG-SUB026-3375:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-UNISIG-SUB026-3532#REF#
Transition table:
transition from LS to OS
"15, 73>" with priority "-p6-"
Rel. 8.0:
[40] ->[73]
#TEST-VAL-SUB026-4553#REF# FCT [15] Mode transition L1 OS->LS[74]->OS[15]
#TEST-VAL-SUB026-5949#REF# FCT [73] Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind

#REQ-UNISIG-SUB026-3376#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to NL
"46>" with priority "-p6-"
#TEST-VAL-SUB026-4564#REF# FCT [46] mode change LS->NL[46]

#REQ-UNISIG-SUB026-3377#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to UN
"21>" with priority "-p6-"
#TEST-VAL-SUB026-4560#REF# FCT [21] mode transition LS->TR[65], PT->LS[70]->UN[21]

#REQ-UNISIG-SUB026-3378:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to TR
"12, 16, 17, 18, 20, 41, 65, 66, 69>" with priority "-p4-"
#TEST-VAL-SUB026-4587#REF# FCT [12] EoA EoA supervision - MA with OL on board LS/L1
#TEST-VAL-SUB026-4H18#REF# FCT [12] LoA LoA supervision - LS/L1
#TEST-VAL-SUB026-4586#REF# FCT [16] EoA EoA supervision - MA with DP on board LS/L2
#TEST-VAL-SUB026-4H17#REF# FCT [16] LoA LoA supervision - LS/L2
#TEST-VAL-SUB026-4559#REF# FCT [17] Mode transition LS->TR[17]
#TEST-VAL-SUB026-4555#REF# FCT [18] Mode transition from LS to TR due to trip order
#TEST-VAL-SUB026-4561#REF# FCT [20] mode change LS->TR[20]
#TEST-VAL-SUB026-4554#REF# FCT [41] mode transition UN->LS(L2)[71]->TR[41]
#TEST-VAL-SUB026-5799#REF# FCT [65] L1 Evaluation of M_VERSION from BG in L1
#TEST-VAL-SUB026-4560#REF# FCT [65] L2 mode transition LS->TR[65], PT->LS[70]->UN[21]
#TEST-VAL-SUB026-4558#REF# FCT [66] linking information when entering LS, L2 LS->SB[28]->LS[70]->TR[66] ->PT->LS[70]
#TEST-VAL-SUB026-5262#REF# FCT [69] GP Transition from LS to TR due backward movement out of GP coverage
#TEST-VAL-SUB026-5260#REF# FCT [69] SSP Transition from LS to TR due backward movement out of SSP coverage

#REQ-UNISIG-SUB026-3379#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4563#REF# FCT [13] mode change LS->SF[13] due to reception of overlapping MP

#REQ-UNISIG-SUB026-3380#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4570#REF# FCT [1] mode transition LS->IS[1], processing Radio/BG message in IS

#REQ-UNISIG-SUB026-3381#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to SN
"56>" with priority "-p6-"
#TEST-VAL-SUB026-4571#REF# FCT [56] LS/L2 - STM system speed and distance and STM max speed; LS->SN[56]

#REQ-UNISIG-SUB026-3382#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from LS to RV
"59>" with priority "-p6-"
#TEST-VAL-SUB026-4562#REF# FCT [59] mode change LS->RV[59]

#REQ-UNISIG-SUB026-2270#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to SB
"28>" with priority "-p5-"
#TEST-VAL-SUB026-5121#REF# FCT [28] Transition from SR to SB

#REQ-DESIGN-CR-0113#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to SH
"5, 6, 51>" with priority "-p6-"
Level 0 and STM (NTC) in condition[5] are not relevant for this transition
#TEST-VAL-SUB026-4611#REF# FCT [51] Modewechsel SR-> SH [51]
#TEST-VAL-SUB026-5010#REF# FCT [5] Shunting initiated by driver L1, SR
#TEST-VAL-SUB026-7135#REF# FCT [6] Mode transition SR->SH[6](override active) SH->SB[19]

#REQ-DESIGN-CR-0592#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to FS
"31, 32>" with priority "-p6-"
#TEST-VAL-SUB026-3001#REF# EET CFX00036745 Accepting new SSP with starting point bevor stored SSP
#TEST-VAL-SUB026-4242#REF# FCT [31] transition FS -> SR -> FS in level 2
#TEST-VAL-SUB026-3687#REF# FCT [32] transition SR->FS[32]

#REQ-UNISIG-SUB026-3502#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SR to LS
"72>" with priority "-p6-"
#TEST-VAL-SUB026-4548#REF# FCT [72] Mode transition L1 SR->LS[72]->SR[37]

#REQ-DESIGN-CR-0103#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to OS
"40>" with priority "-p6-"
#TEST-VAL-SUB026-4836#REF# FCT [40] mode transition L1 SR->OS[40]->SH[51]
#TEST-VAL-SUB026-4617#REF# EET error expectation SR->OS[40]->SH[51]

#REQ-UNISIG-SUB026-2271#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to NL
"46>" with priority "-p6-"
#TEST-VAL-SUB026-4628#REF# EET CFX00036464 SR->NL->SB[47]
#TEST-VAL-SUB026-4243#REF# FCT [46] transition FS(L2->L1) -> SR -> NL

#REQ-UNISIG-SUB026-2272#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to UN
"21>" with priority "-p6-"
#TEST-VAL-SUB026-4123#REF# FCT [21] Mode transition SR to UN [21]

#REQ-DESIGN-CR-0461#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to TR
"18, 20, 36, 42, 43, 54, 65>" with priority "-p4-"
#TEST-VAL-SUB026-4113#REF# FCT [18] Mode transition from SR to TR due to trip order
#TEST-VAL-SUB026-4584#REF# FCT [20] mode transition SR-TR[20]
#TEST-VAL-SUB026-4349#REF# FCT [36] OBU establishes communication session and sends PR due to mode change SR->TR
#TEST-VAL-SUB026-5664#REF# FCT [42] Supervision of D_SR and V_NVSTFF
#TEST-VAL-SUB026-5509#REF# FCT [43] Retention of EoA when override EoA done in FS/OS
#TEST-VAL-SUB026-3327#REF# FCT [54] L1 SR - reception of MA and P137(next balise) -> L1 TRIP [54]
#TEST-VAL-SUB026-4254#REF# FCT [65] L1 transition SR(L2) -> SR(L1) -> TR(L1)[65]
#TEST-VAL-SUB026-5413#REF# FCT [65] L2 SR overrive EoA active when receiving balise telegram with a non compatible version
#TEST-VAL-SUB026-4H14#REF# EET error expectation Conditional level transition order (L2->L0) with Stop if in Staff Responsible

#REQ-UNISIG-SUB026-2274#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-3278#REF# FCT [13] Ortungsfehler (Richtung)

#REQ-UNISIG-SUB026-2275#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4106#REF# FCT [1] SR->IS[1]

#REQ-UNISIG-SUB026-2277#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SR to SN
"56>" with priority "-p6-"
#TEST-VAL-SUB026-3430#REF# FCT [56] Mode transition SR->SN[56]->SH[61]

#REQ-UNISIG-SUB026-2278#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to SB
"28>" with priority "-p5-"
#TEST-VAL-SUB026-5118#REF# FCT [28] Uebergang OS nach SB

#REQ-UNISIG-SUB026-2279#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-DESIGN-CR-0633:01#REF#
Transition table:
transiton from OS to SH
"5, 6, 50, 51>" with priority "-p6-"
Level 0 and STM (NTC) in condition[5] are not relevant for this transition
#TEST-VAL-SUB026-5001#REF# FCT [50] OS->SH [50]
#TEST-VAL-SUB026-4836#REF# FCT [51] mode transition L1 SR->OS[40]->SH[51]
#TEST-VAL-SUB026-4615#REF# FCT [5] OS->SH[5]
#TEST-VAL-SUB026-4616#REF# FCT [6] OS->SH[6]

#REQ-DESIGN-CR-0593#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-DESIGN-CR-0633:01#REF#
Transition table:
transiton from OS to FS
"<31, 32" with priority "-p6-"
#TEST-VAL-SUB026-3141#REF# FCT [31] Start and end of mode profile
#TEST-VAL-SUB026-4980#REF# FCT [32] Transition Table 4.6.3 OS->FS[32]->SR[37]->FS[31]->SR[37]->TR[54]
#TEST-VAL-SUB026-4099#REF# EET error expectation Modewechsel und MA-Ruecknahme

#REQ-UNISIG-SUB026-3503:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-DESIGN-CR-0633:01#REF#
Transition table:
transition from OS to LS
"70, 74>" with priority "-p6-"
Rel. 8.0:
[72]->[74]
#TEST-VAL-SUB026-4551#REF# FCT [70] TSR when entering LS, TSR in LS; OS->LS[70]
#TEST-VAL-SUB026-5949#REF# FCT [74] Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind

#REQ-UNISIG-SUB026-2280#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to SR
"37>" with priority "-p6-"
#TEST-VAL-SUB026-4244#REF# FCT [37] transition FS(L2) -> OS(L2-L1) -> SR

#REQ-UNISIG-SUB026-2281#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to NL
"46>" with priority "-p6-"
#TEST-VAL-SUB026-4619#REF# FCT [46] OS->NL

#REQ-UNISIG-SUB026-2282#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to UN
"21>" with priority "-p6-"
#TEST-VAL-SUB026-4120#REF# FCT [21] Modewechsel: Von OS nach UN wegen [21]

#REQ-DESIGN-CR-0039:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to TR
"12, 16, 17, 18, 20, 41, 65, 66, 69>" with priority "-p4-"
#TEST-VAL-SUB026-4877#REF# FCT [12] EoA EoA supervision - MA with OL on board OS/L1
#TEST-VAL-SUB026-4H16#REF# FCT [12] LoA LoA supervision - OS/L1
#TEST-VAL-SUB026-4876#REF# FCT [16] EoA OS/L2 -> TR/L2 when passing EoA/LoA with min safe front end
#TEST-VAL-SUB026-4H15#REF# FCT [16] LoA LoA supervision - OS/L2
#TEST-VAL-SUB026-4118#REF# FCT [17] Modewechsel: Von OS nach TR wegen [17]
#TEST-VAL-SUB026-4111#REF# FCT [18] Mode transition from OS to TR due to trip order
#TEST-VAL-SUB026-4653#REF# FCT [20] Modewechsel OS->TR[20]
#TEST-VAL-SUB026-4621#REF# FCT [41] OS->TR[41]
#TEST-VAL-SUB026-5799#REF# FCT [65] L1 Evaluation of M_VERSION from BG in L1
#TEST-VAL-SUB026-4119#REF# FCT [65] L2 Mode transition from OS to TR due to BG with incompatible version
#TEST-VAL-SUB026-4622#REF# FCT [66] OS->TR[66]
#TEST-VAL-SUB026-5261#REF# FCT [69] GP Transition from OS to TR due backward movement out of GP coverage
#TEST-VAL-SUB026-5263#REF# FCT [69] SSP Transition from OS to TR due backward movement out of SSP coverage
#TEST-VAL-SUB026-3693#REF# EET error expectation OS/L2 -> TR/L2 due to section timer timeout
#TEST-VAL-SUB026-4259#REF# EET error expectation transition OS(L1) -> TR(L0)[18]

#REQ-UNISIG-SUB026-2283#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4623#REF# FCT [13] OS->SF

#REQ-UNISIG-SUB026-2287#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4624#REF# FCT [1] OS->IS

#REQ-UNISIG-SUB026-2289#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to SN
"56>" with priority "-p6-"
#TEST-VAL-SUB026-4625#REF# FCT [56] OS->SN

#REQ-UNISIG-SUB026-2290#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from OS to RV
"59>" with priority "-p6-"
#TEST-VAL-SUB026-4626#REF# FCT [59] OS->RV

#REQ-UNISIG-SUB026-2236#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SL to SB
"2, 3>" with priority "-p4-"
#TEST-VAL-SUB026-4245#REF# FCT [2] transition SL -> SB (L1)
#TEST-VAL-SUB026-4008#REF# FCT [3] Mode transition SL to SB

#REQ-UNISIG-SUB026-2238#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SL to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4627#REF# FCT [1] SL->IS

#REQ-UNISIG-SUB026-2239#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from NL to SB
"28, 47>" with priority "-p3-"
#TEST-VAL-SUB026-5120#REF# FCT [28] Uebergang NL nach SB
#TEST-VAL-SUB026-4628#REF# FCT [47] SR->NL->SB[47]

#REQ-UNISIG-SUB026-2241#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from NL to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4629#REF# FCT [1] NL->IS

#REQ-DESIGN-CR-0337#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to SB
"28>" with priority "-p6-"
#TEST-VAL-SUB026-5119#REF# FCT [28] Uebergang UN nach SB

#REQ-DESIGN-CR-0340#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to SH
"5, 61>" with priority "-p7-"
#TEST-VAL-SUB026-4251#REF# FCT [5] transition FS(L2) -> UN(L0)[21] -> SH[5] -> SB[19]
#TEST-VAL-SUB026-4274#REF# FCT [61] L1 Pkt 80 accepted and buffered in UN
#TEST-VAL-SUB026-4630#REF# FCT [61] L2 Mode transition UN->SH[61]

#REQ-DESIGN-CR-0341#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to FS
"25>" with priority "-p7-"
#TEST-VAL-SUB026-4403#REF# EET CFX00038338 Manual level choice (L1) to already announced destination level (UN->FS)
#TEST-VAL-SUB026-3197#REF# FCT [25] L1 NVCONTACT supervision, M_NVCONTACT=0 - Train trip
#TEST-VAL-SUB026-5424#REF# FCT [25] L2 transition from UN/L0 to FS/L2

#REQ-UNISIG-SUB026-3504#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to LS
"71>" with priority "-p7-"
#TEST-VAL-SUB026-4556#REF# FCT [71] L1 Mode transition UN->LS(L1)[71]->TR[12]
#TEST-VAL-SUB026-4554#REF# FCT [71] L2 mode transition UN->LS(L2)[71]->TR[41]

#REQ-DESIGN-CR-0335:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to SR
"44, 45>" with priority "-p4-"
#TEST-VAL-SUB026-4255#REF# FCT [44] Override in L0 - level change to L1
#TEST-VAL-SUB026-5027#REF# FCT [45] Override in L0
#TEST-VAL-SUB026-4256#REF# EET error expectation UN override active - transition to L2 (L2 MA available)
#TEST-VAL-SUB026-4423#REF# EET error expectation level transition L0/L1 - L1 MA in transition buffer override EoA active

#REQ-DESIGN-CR-0342#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to OS
"34>" with priority "-p7-"
#TEST-VAL-SUB026-4260#REF# FCT [34] L1 UN - pass BG LTO(L1) now + MA, SSP, GP, MP (OS now) -> OS(L1)[34]
#TEST-VAL-SUB026-4246#REF# FCT [34] L2 transition FS(L2) -> UN(L0) -> OS(L2)

#REQ-DESIGN-CR-0336:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to TR
"20, 39, 67>" with priority "-p5-"
#TEST-VAL-SUB026-4325#REF# FCT [20] mode transition UN->TR[20] while override EoA active
#TEST-VAL-SUB026-4262#REF# FCT [39] L1 UN - pass BG LTO(L1) now + MA, GP but no SSP -> TR(L1)[39]
#TEST-VAL-SUB026-4253#REF# FCT [39] L2 transition FS(L2) -> UN(L0)[21] -> TR(L2)[39]
#TEST-VAL-SUB026-4404#REF# FCT [67] UN->L1/TR[67] trip order out of level transition buffer
#TEST-VAL-SUB026-4406#REF# EET error expectation UN->TR/L1[67] level transition buffer includes valid MA followed by trip order

#REQ-UNISIG-SUB026-2247#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from UN to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4631#REF# FCT [13] Mode change UN->SF[13]

#REQ-UNISIG-SUB026-2246#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from UN to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4632#REF# FCT [1] Modewechsel UN->IS[1]

#REQ-DESIGN-CR-0339#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from UN to SN
"56>" with priority "-p7-"
#TEST-VAL-SUB026-5089#REF# FCT [56] Acknowledgment request at level transition L0 to NTC

#REQ-UNISIG-SUB026-007068#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-UNISIG-SUB026-010135#REF#
Transition table:
transition from TR to SH
"68>" with priority "-p4-"
#TEST-VAL-SUB026-4H32#REF# FCT [68] L0 mode/level transition SH/L1->TR/L1->TR/L0->SH/L0
#TEST-VAL-SUB026-4H31#REF# FCT [68] NTC mode/level transition SH/L1->TR/L1->TR/STM->SH/STM

#REQ-UNISIG-SUB026-2250:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-UNISIG-SUB026-010136#REF#
Transition table:
transiton from TR to UN
"62>" with priority "-p4-"
#TEST-VAL-SUB026-4124#REF# FCT [62] Mode transition SR->TR[54] TR->UN[62]

#REQ-UNISIG-SUB026-2252#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-DESIGN-CR-0179:01#REF#
Transition table:
transiton from TR to PT
"7>" with priority "-p4-"
#TEST-VAL-SUB026-4248#REF# FCT [7] L1 transition FS(L2) -> TR(L1)[18] -> PT[7] -> SR[37]
#TEST-VAL-SUB026-3159#REF# FCT [7] L2 Transition to TR at EOA/LOA

#REQ-UNISIG-SUB026-2254#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from TR to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4633#REF# FCT [13] Modewechsel TR->SF[13]

#REQ-UNISIG-SUB026-2255#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from TR to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4634#REF# FCT [1] Modewechsel TR->IS[1]

#REQ-UNISIG-SUB026-2259#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
#REQ-DESIGN-CR-0132:02#REF#
Transition table:
transiton from TR to SN
"63>" with priority "-p4-"
#TEST-VAL-SUB026-4635#REF# FCT basic function TR->SN[63]

#REQ-DESIGN-CR-0013#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transitions Table:
transition from PT to SB
"28>" with priority "-p4-"
#TEST-VAL-SUB026-5470#REF# FCT [28] Mode transition L2 PT->SB - M6 not received yet
#TEST-VAL-SUB026-5471#REF# EET error expectation Mode transition L2 TR->PT->SB - no communication session open, RBC contact data not available

#REQ-DESIGN-CR-0130#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from PT to SH
"5, 6, 50>" with priority "-p5-"
Level 0 and STM (NTC) in condition[5] are not relevant for this transition
#TEST-VAL-SUB026-4938#REF# FCT [50] Mode transition SR->TR[54], SH->TR[49], PT->SH[50], PT->SR[37], PT->OS[15]
#TEST-VAL-SUB026-4042#REF# FCT [5] Transition from PT/L1 to SH/L1
#TEST-VAL-SUB026-5543#REF# FCT [6] PT->SH[6] - degraded situation RBC does not order termination of connection

#REQ-DESIGN-CR-0016#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transitions Table:
transition from PT to FS
"31>" with priority "-p5-"
#TEST-VAL-SUB026-5110#REF# EET CFX00034775 Kanten der TR-Prozedur testen mit Emergency Message
#TEST-VAL-SUB026-4286#REF# FCT [31] acceptance of radio message with former LRBG FS, SN, TR, PT

#REQ-UNISIG-SUB026-3505#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from PT to LS
"70>" with priority "-p4-"
#TEST-VAL-SUB026-4560#REF# FCT [70] mode transition LS->TR[65], PT->LS[70]->UN[21]

#REQ-DESIGN-CR-0015#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transitions Table:
transition from PT to SR
"8, 37>" with priority "-p5-"
#TEST-VAL-SUB026-8267#REF# EET CFX00188962 Override activation in PT while train is moving
#TEST-VAL-SUB026-3725#REF# FCT [37] L0->L2 Level transition buffer information evaluation due to train category change
#TEST-VAL-SUB026-4041#REF# FCT [8] From PT to Start, L1

#REQ-DESIGN-CR-0014#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transitions Table:
transition from PT to OS
"15>" with priority "-p5-"
#TEST-VAL-SUB026-4654#REF# EET CFX00035858 PT->OS[15]
#TEST-VAL-SUB026-4938#REF# FCT [15] Mode transition SR->TR[54], SH->TR[49], PT->SH[50], PT->SR[37], PT->OS[15]

#REQ-UNISIG-SUB026-2260#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from PT to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4638#REF# FCT [13] Modewechsel PT->SF[13]

#REQ-UNISIG-SUB026-2261#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from PT to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4639#REF# FCT [1] Modewechsel PT->IS[1]

#REQ-UNISIG-SUB026-2262#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SF to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4640#REF# FCT [1] Mode change SF->IS[1]

#REQ-DESIGN-CR-0378#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to SB
"28>" with priority "-p6-"
#TEST-VAL-SUB026-4641#REF# FCT [28] Modewechsel SN->SB[28]

#REQ-DESIGN-CR-0498:01#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to SH
"5, 61>" with priority "-p7-"
#TEST-VAL-SUB026-7061#REF# FCT [5] Driver selects SH in NTC
#TEST-VAL-SUB026-3430#REF# FCT [61] L1 Mode transition SR->SN[56]->SH[61]
#TEST-VAL-SUB026-4241#REF# FCT [61] L2 transition FS/L2 - SN/STM - SH/L2

#REQ-DESIGN-CR-0379#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to FS
"25>" with priority "-p7-"
#TEST-VAL-SUB026-5094#REF# FCT [25] L1 Acknowledgment request at level transition NTC to L1
#TEST-VAL-SUB026-4880#REF# FCT [25] L2 Deletion of unconditional EmergencyStop on entry into SN

#REQ-UNISIG-SUB026-3506#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to LS
"71>" with priority "-p7-"
#TEST-VAL-SUB026-4590#REF# FCT [71] L1 mode transition SN->LS(L1)[71]
#TEST-VAL-SUB026-4557#REF# FCT [71] L2 mode transition SN->LS(L2)[71]->TR[16]

#REQ-DESIGN-CR-0376#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to SR
"44, 45>" with priority "-p4-"
#TEST-VAL-SUB026-5417#REF# FCT [44] Override in SN -> LTO (L1) - MA + MP (SH) -> SR
#TEST-VAL-SUB026-4475#REF# FCT [45] SN/STM - Report train position when change of level due to driver request

#REQ-DESIGN-CR-0380#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to OS
"34>" with priority "-p7-"
#TEST-VAL-SUB026-4643#REF# FCT [34] L1 SN->OS[34] L1
#TEST-VAL-SUB026-4479#REF# FCT [34] L2 SN/STM acceptance MP-OS - LTO L2 onboard

#REQ-DESIGN-CR-0539#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to UN
"21>" with priority "-p7-"
#TEST-VAL-SUB026-5093#REF# FCT [21] Acknowledgement of level transition

#REQ-DESIGN-CR-0377:02#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from SN to TR
"20, 35, 38, 39, 67>" with priority "-p5-"
#TEST-VAL-SUB026-4C88#REF# FCT [20] Manage Unconditional Emergency Stop: SN/STM
#TEST-VAL-SUB026-7059#REF# FCT [35] SN/STM (EB applied) driver selects SH
#TEST-VAL-SUB026-4493#REF# FCT [38] L0 SN/NTC (EB applied) transition to L0
#TEST-VAL-SUB026-4494#REF# FCT [38] L1 SN/STM (EB applied) - transition to L1
#TEST-VAL-SUB026-4495#REF# FCT [38] L2 SN/STM (EB applied) - transition to L2
#TEST-VAL-SUB026-5084#REF# FCT [39] L1 Level transition NTC->L1 without L1-MA
#TEST-VAL-SUB026-4286#REF# FCT [39] L2 acceptance of radio message with former LRBG FS, SN, TR, PT
#TEST-VAL-SUB026-4644#REF# FCT [67] SN->TR[67]

#REQ-UNISIG-SUB026-2264#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SN to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4646#REF# FCT [13] Mode change SN->SF[13]

#REQ-UNISIG-SUB026-2266#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from SN to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4647#REF# FCT [1] Modewechsel SN->IS[1]

#REQ-UNISIG-SUB026-2267#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transition from RV to SB
"28>" with priority "-p4-"
#TEST-VAL-SUB026-4288#REF# FCT [28] Last reported balise group identities transition FS(L2)-> RV(L2)-> SB(L2) -> OS(L2) ->FS(L2)

#REQ-UNISIG-SUB026-2268#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from RV to SF
"13>" with priority "-p3-"
#TEST-VAL-SUB026-4649#REF# FCT [13] Mode transition RV->SF[13]

#REQ-UNISIG-SUB026-2269#REF# 4.6.2 #REQ-UNISIG-SUB026-0247:01#REF#
Transition table:
transiton from RV to IS
"1>" with priority "-p1-"
#TEST-VAL-SUB026-4650#REF# FCT [1] Modewechsel RV->IS[1]

#REQ-UNISIG-SUB026-2214:01#REF# 4.6.3 #REQ-UNISIG-SUB026-3337#REF#
Transitions Conditions Table








{1} The request to acknowledge On Sight is displayed to the driver only if certain conditions are fulfilled. These conditions are not specified
here. See the “On Sight” procedure” of SRS-§5 (for transitions from FS/LS/UN to OS) and the "Start of mission" procedure (for
transition from SB to OS).
{2} This transition to the Unfitted mode is also a transition of level.. For further information, See the “Level Transition” procedure” (SRS-§5)
for transitions from FS/SR/OS/LS to UN and the “Start Of Mission” procedure” (SRS-§5) for transition from SB to UN.
{3} See the “Override” procedure” of SRS-§5.
{4} The Staff Responsible mode is proposed to the driver only if certain conditions are fulfilled. These conditions are not specified here. See
the “Start Of Mission” procedure and the "Train Trip" procedure of SRS-§5.
{5} The request to acknowledge Shunting is displayed to the driver only if certain conditions are fulfilled. These conditions are not specified
here. See the “Entry in Shunting” procedure and the “Start Of Mission” procedure of SRS-§5.
{6} The request to acknowledge Reversing is displayed to the driver when certain conditions are fulfilled. These conditions are not specified
here. See the “reversing” procedure of SRS-§5.
{7} The request to acknowledge Limited Supervision is displayed to the driver only if certain conditions are fulfilled. These conditions are not
specified here. See the “Limited Supervision” procedure” of SRS-§5 (for transitions from FS/OS/UN to LS) and the "Start of mission"
procedure (for transition from SB to LS).
{8} Refer to Subset-035 for details.
TEST APPROACH:
UNISG distinguishes between L1 and L2/L3 MA/MP and that this has been taken into account in the aspect definition for conditions [10], [15],
[40], [51], [70] and [72]
Levels 2 and 3 are considered in the same equivalence class. 
realised by: #REQ-UNISIG-SUB026-2227#REF#
realised by: #REQ-UNISIG-SUB026-2213#REF#
realised by: #REQ-UNISIG-SUB026-2237#REF#
realised by: #REQ-UNISIG-SUB026-2334#REF#
realised by: #REQ-UNISIG-SUB026-2215:01#REF#
realised by: #REQ-DESIGN-CR-0737#REF#
realised by: #REQ-UNISIG-SUB026-2253#REF#
realised by: #REQ-UNISIG-SUB026-2218#REF#
realised by: #REQ-UNISIG-SUB026-2217#REF#
realised by: #REQ-DESIGN-CR-0596#REF#
realised by: #REQ-UNISIG-SUB026-2225#REF#
realised by: #REQ-UNISIG-SUB026-2221#REF#
realised by: #REQ-UNISIG-SUB026-2220#REF#
realised by: #REQ-DESIGN-CR-0597#REF#
realised by: #REQ-UNISIG-SUB026-2284#REF#
realised by: #REQ-UNISIG-SUB026-2273#REF#
realised by: #REQ-UNISIG-SUB026-2229#REF#
realised by: #REQ-DESIGN-CR-0362#REF#
realised by: #REQ-UNISIG-SUB026-2263#REF#
realised by: #REQ-UNISIG-SUB026-010225#REF#
realised by: #REQ-UNISIG-SUB026-010226#REF#
realised by: #REQ-UNISIG-SUB026-2242#REF#
realised by: #REQ-UNISIG-SUB026-010227#REF#
realised by: #REQ-UNISIG-SUB026-010228#REF#
realised by: #REQ-UNISIG-SUB026-2230#REF#
realised by: #REQ-UNISIG-SUB026-010229#REF#
realised by: #REQ-DESIGN-CR-0594#REF#
realised by: #REQ-DESIGN-CR-0595#REF#
realised by: #REQ-DESIGN-CR-0049#REF#
realised by: #REQ-UNISIG-SUB026-010397#REF#
realised by: #REQ-DESIGN-CR-0465#REF#
realised by: #REQ-UNISIG-SUB026-2219:01#REF#
realised by: #REQ-UNISIG-SUB026-3461#REF#
realised by: #REQ-UNISIG-SUB026-2245#REF#
realised by: #REQ-DESIGN-CR-0050#REF#
realised by: #REQ-UNISIG-SUB026-2285#REF#
realised by: #REQ-DESIGN-CR-0459#REF#
realised by: #REQ-DESIGN-CR-0462#REF#
realised by: #REQ-UNISIG-SUB026-2243:01#REF#
realised by: #REQ-UNISIG-SUB026-3480#REF#
realised by: #REQ-UNISIG-SUB026-2222:01#REF#
realised by: #REQ-UNISIG-SUB026-2240:02#REF#
realised by: #REQ-DESIGN-CR-0466#REF#
realised by: #REQ-UNISIG-SUB026-2216#REF#
realised by: #REQ-DESIGN-CR-0059#REF#
realised by: #REQ-DESIGN-CR-0467#REF#
realised by: #REQ-DESIGN-CR-0468:01#REF#
realised by: #REQ-UNISIG-SUB026-2249:01#REF#
realised by: #REQ-DESIGN-CR-0110:02#REF#
realised by: #REQ-UNISIG-SUB026-2291#REF#
realised by: #REQ-UNISIG-SUB026-2223#REF#
realised by: #REQ-DESIGN-CR-0060#REF#
realised by: #REQ-UNISIG-SUB026-2251:01#REF#
realised by: #REQ-UNISIG-SUB026-2258:02#REF#
realised by: #REQ-UNISIG-SUB026-2233:01#REF#
realised by: #REQ-UNISIG-SUB026-2286#REF#
realised by: #REQ-UNISIG-SUB026-2244#REF#
realised by: #REQ-UNISIG-SUB026-007623:01#REF#
realised by: #REQ-UNISIG-SUB026-006975#REF#
realised by: #REQ-UNISIG-SUB026-3396#REF#
realised by: #REQ-UNISIG-SUB026-3397#REF#
realised by: #REQ-UNISIG-SUB026-3398#REF#
realised by: #REQ-UNISIG-SUB026-010231#REF#
realised by: #REQ-UNISIG-SUB026-010232#REF#

#REQ-UNISIG-SUB026-2227#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [1]
The driver isolates the ERTMS/ETCS on-board equipment.
#TEST-VAL-SUB026-4640#REF# FCT basic function Mode change SF->IS[1]

#REQ-UNISIG-SUB026-2213#REF# 4.6.3 #REQ-UNISIG-SUB026-0723#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
condition [2]
(a desk is open)
#TEST-VAL-SUB026-4245#REF# FCT basic function transition SL -> SB (L1)

#REQ-UNISIG-SUB026-2237#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [3]
(no “go sleeping” input signal is received any more) AND (train is at standstill)
#TEST-VAL-SUB026-4008#REF# FCT basic function Mode transition SL to SB

#REQ-UNISIG-SUB026-2334#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [4]
(The ERTMS/ETCS on-board equipment is powered.)
#TEST-SWHWINT-STARTUP-0019#REF# FCT basic function Hochlauf mit Fahrt Level 1 über reale Teilstrecke

#REQ-UNISIG-SUB026-2215:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-010541#REF#
condition [5]
(train is at standstill) AND (ERTMS/ETCS level is 0 or NTC or 1) AND (driver selects Shunting mode)
#TEST-VAL-SUB026-4251#REF# FCT L0, train at standstill transition FS(L2) -> UN(L0)[21] -> SH[5] -> SB[19]
#TEST-VAL-SUB026-4235#REF# FCT L1 transition SB -> SH -> TR [49] in level 1
#TEST-VAL-SUB026-7061#REF# FCT NTC(DA) Driver selects SH in NTC
#TEST-VAL-SUB026-7640#REF# FCT NTC(FA) Driver selects SH in NTC(FA)
#TEST-VAL-SUB026-5788#REF# FCT NTC(HS) Mode transition from SN(HS) to SH

#REQ-DESIGN-CR-0737#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-010542#REF#
condition [6]
(train is at standstill) AND (ERTMS/ETCS level is 2 or 3) AND (reception of the information “Shunting granted by RBC”, due to a Shunting request
from the driver)
condition standstill valid for initial shunting request only
#TEST-VAL-SUB026-4616#REF# FCT basic function OS->SH[6]

#REQ-UNISIG-SUB026-2253#REF# 4.6.3 #REQ-UNISIG-SUB026-0209#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
condition [7]
(the driver acknowledges the train trip) AND (the train is at standstill) AND (the ERTMS/ETCS level is different from 0, NTC)
condition standstill valid for initial request to acknowledge TR only
TEST APPROACH:
The condition "the train is at standstill" is evaluated for the activation of the TRIP acknowledgment request.
A train movement after standstill can be excluded from operational point of view as the EB remain active.
#TEST-VAL-SUB026-4248#REF# FCT L1 transition FS(L2) -> TR(L1)[18] -> PT[7] -> SR[37]
#TEST-VAL-SUB026-3159#REF# FCT L2, standstill Transition to TR at EOA/LOA

#REQ-UNISIG-SUB026-2218#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-010386#REF#
condition [8]
(Staff Responsible mode is proposed to the driver) AND (driver acknowledges)
#TEST-VAL-SUB026-4041#REF# FCT L1 From PT to Start, L1
#TEST-VAL-SUB026-3669#REF# FCT L2 Train location data - nominal/revers of LRBG
#TEST-VAL-SUB026-7155#REF# EET error expectation SR acknowledgment request triggered in L1, acknowledged in L2

#REQ-UNISIG-SUB026-2217#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-1098:01#REF#
condition [10]
(valid Train Data is stored on board) AND (MA + SSP + gradient are on-board) AND (no specific mode is required by a Mode Profile)
TEST APPROACH:
The condition "Train Data is stored on board" is sufficiently covered by #REQ-UNISIG-SUB026-3462#REF#.
#TEST-VAL-SUB026-4887#REF# FCT L1 Check table 4.8.4 -> Repositioning Information (SB/L1)
#TEST-VAL-SUB026-5406#REF# FCT L2 SOM - L2/FS

#REQ-DESIGN-CR-0596#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [12]
(Train/engine overpasses the EoA/LoA with its min safe antenna position) AND (ERTMS/ETCS level is 1)
#TEST-VAL-SUB026-3429#REF# EET CFX00037616 Mode transition FS->OS [15] ->TR [12] ->PT [7]
#TEST-VAL-SUB026-4587#REF# FCT EoA EoA supervision - MA with OL on board LS/L1
#TEST-VAL-SUB026-4H16#REF# FCT LoA LoA supervision - OS/L1
#TEST-VAL-SUB040-0005#REF# EET error expectation Maximal antenna distance

#REQ-UNISIG-SUB026-2225#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [13]
The ERTMS/ETCS on-board equipment detects a fault that affects safety
TEST APPROACH:
The aim of the test is to verify the condition by example only. An exhaustive test is omitted here the conditions for the transition to SF are
tested via the appropriated requirements.
#TEST-VAL-SUB026-4633#REF# FCT BG error Modewechsel TR->SF[13]
#TEST-VAL-SUB026-3278#REF# FCT ODO outage Ortungsfehler (Richtung)
#TEST-VAL-SUB026-4563#REF# FCT track error mode change LS->SF[13] due to reception of overlapping MP

#REQ-UNISIG-SUB026-2221#REF# 4.6.3 #REQ-UNISIG-SUB026-0723#REF#
#REQ-UNISIG-SUB026-0156#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
condition [14]
(The “sleeping” input signal is received) AND (train is at standstill) AND (all desks connected to the ERTMS/ETCS on-board equipment are closed)
#TEST-VAL-SUB026-5800#REF# FCT basic function Conditions for transition to SL

#REQ-UNISIG-SUB026-2220#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-DESIGN-CR-0055#REF#
condition [15]
(An ackn. request for On Sight is displayed to the driver) AND (the driver acknowledges)    see {1} here under
#TEST-VAL-SUB026-4239#REF# FCT L1 transition FS -> OS in level 1
#TEST-VAL-SUB026-4288#REF# FCT L2 Last reported balise group identities transition FS(L2)-> RV(L2)-> SB(L2) -> OS(L2) ->FS(L2)

#REQ-DESIGN-CR-0597#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [16]
(The Train/engine overpasses the EoA/LoA with its min safe front end) AND (ERTMS/ETCS level is 2 or 3)
#TEST-VAL-SUB026-4317#REF# EET CFX00037616 EoA supervision after L1->L2 transition
#TEST-VAL-SUB026-4876#REF# FCT EoA OS/L2 -> TR/L2 when passing EoA/LoA with min safe front end
#TEST-VAL-SUB026-4H15#REF# FCT LoA LoA supervision - OS/L2

#REQ-UNISIG-SUB026-2284#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [17]
The onboard reacts according to a linking reaction set to “trip”.
#TEST-VAL-SUB026-5474#REF# EET CFX00041126 Reception of M3 with shortened MA and linking information for BG beyond the new EoA
#TEST-VAL-SUB026-4559#REF# FCT basic function Mode transition LS->TR[17]

#REQ-UNISIG-SUB026-2273#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [18]
(the train/engine receives and uses a trip order given by balise) AND (override is not active)
#TEST-VAL-SUB026-4E16#REF# FCT override active Override active, pass BG with MA with V_MAIN=0 (trip order)
#TEST-VAL-SUB026-4110#REF# FCT override not active Mode transition from FS to TR due to trip order

#REQ-UNISIG-SUB026-2229#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [19]
(driver selects “exit Shunting”) AND (train is at standstill).
#TEST-VAL-SUB026-7134#REF# FCT basic function mode transition SR(L1) -> SH[5] -> SB[19]

#REQ-DESIGN-CR-0362#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [20]:
(unconditional emergency stop message is accepted)
#TEST-VAL-SUB026-5414#REF# EET CFX00037093 SR overrive EoA active when receiving unconditional emergency stop message
#TEST-VAL-SUB026-4584#REF# FCT basic function mode transition SR-TR[20]
#TEST-VAL-SUB026-4325#REF# EET error expectation mode transition UN->TR[20] while override EoA active

#REQ-UNISIG-SUB026-2263#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [21]
(ERTMS/ETCS level switches to 0)     see {2} here under
#TEST-VAL-SUB026-4H46#REF# EET CFX00035330 Level transition location and EoA passed at same time due to location synchronization according to P5
#TEST-VAL-SUB026-5093#REF# FCT level transition ordered by track side Acknowledgement of level transition
#TEST-VAL-SUB026-4252#REF# FCT manual level choice transition FS(L2) -> FS(L1) -> UN [21]

#REQ-UNISIG-SUB026-010225#REF# 4.6.3 #REQ-UNISIG-SUB026-005258#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-010392#REF#
condition [22]
(a desk is open) AND (”Stop Shunting on desk opening” information is stored onboard)
PS is not realized => this condition is not realized too
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-010226#REF# 4.6.3 #REQ-UNISIG-SUB026-005256#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-006449#REF#
#REQ-UNISIG-SUB026-010392#REF#
condition [23]
(a desk is open) AND (no ”Stop Shunting on desk opening” information is stored onboard)
PS is not realized => this condition is not realized too
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-2242#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [25]
(ERTMS/ETCS level switches to 1,2 or 3) AND (MA+SSP+gradient are on-board) AND (no specific mode is required by a Mode Profile)
#TEST-VAL-SUB026-3197#REF# FCT L1 NVCONTACT supervision, M_NVCONTACT=0 - Train trip
#TEST-VAL-SUB026-5424#REF# FCT L2 transition from UN/L0 to FS/L2

#REQ-UNISIG-SUB026-010227#REF# 4.6.3 #REQ-UNISIG-SUB026-005244#REF#
#REQ-UNISIG-SUB026-005252#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-006447#REF#
condition [26]
(desks are closed) AND (”Continue Shunting on desk closure” function is active) AND (the “passive shunting” input signal is received)
PS is not realized => this condition is not realized too

UNISIG clarification: 
 the state of “passive shunting” input signal is only relevant for the change to PS not inside PS.
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-010228#REF# 4.6.3 #REQ-UNISIG-SUB026-005252#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
condition [27]
(desks are closed) AND (”Continue Shunting on desk closure” function is not active)
PS is not realized => this condition is not realized too

#REQ-UNISIG-SUB026-2230#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-006400#REF#
condition [28]
(desks are closed)
#TEST-VAL-SUB026-4238#REF# FCT basic function Report train position when change of level due to driver request and when mode changes FS -> SB (L1)
#TEST-VAL-SUB026-7673#REF# EET error expectation Closing the CAB while in TR

#REQ-UNISIG-SUB026-010229#REF# 4.6.3 #REQ-UNISIG-SUB026-005252#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
condition [30]
(desks are closed) AND (no “passive shunting” input signal is received)
it's not possible to change to PS and so leaves PS too.
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-DESIGN-CR-0594#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [31]:
(MA+SSP+gradient are on-board) AND (no specific mode is required by a Mode Profile) AND (ERTMS/ETCS level is 2 or 3)
#TEST-VAL-SUB026-4242#REF# FCT MP deleted transition FS -> SR -> FS in level 2
#TEST-VAL-SUB026-3141#REF# FCT end of MP Start and end of mode profile
#TEST-VAL-SUB026-3139#REF# FCT new MA without MP Mode Profile deleted due to new MA without MP

#REQ-DESIGN-CR-0595#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [32]:
(MA+SSP+gradient are on-board) AND (no specific mode is required by a Mode Profile) AND (ERTMS/ETCS level is 1) AND (no trip order is given by
balise)
#TEST-VAL-SUB026-4099#REF# FCT MP deleted Modewechsel und MA-Ruecknahme
#TEST-VAL-SUB026-4544#REF# FCT end of MP Pkt 72 M_MODETEXTDISPLAY = LS, L1 FS->LS[70]->FS[32]
#TEST-VAL-SUB026-3687#REF# FCT new MA without MP transition SR->FS[32]

#REQ-DESIGN-CR-0049#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-DESIGN-CR-0168#REF#
condition [34]:
(A Mode Profile defining an On Sight area is on-board) AND (The max safe front end of the train is inside the On Sight area) AND (The ERTMS/ETCS
level switches to 1, 2 or 3)
#TEST-VAL-SUB026-4260#REF# FCT L1 UN - pass BG LTO(L1) now + MA, SSP, GP, MP (OS now) -> OS(L1)[34]
#TEST-VAL-SUB026-4479#REF# FCT L2 SN/STM acceptance MP-OS - LTO L2 onboard
#TEST-VAL-SUB026-8295#REF# EET error expectation Evaluation of buffered MP, estimated front end inside MP, max safe front end outside MP

#REQ-UNISIG-SUB026-010397#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-010540#REF#
#ANA-UNISIG-ModeTransition-0003#REF#
condition [35]:
(driver selects Shunting mode) AND (The ERTMS/ETCS on-board equipment is interfaced to the National System through an STM) AND (Emergency Brake
is commanded by this STM)

note: see also Subset 35 for details
difference to subset 26, version 3.3.0 - see analysis
#TEST-VAL-SUB026-7059#REF# FCT basic function SN/STM (EB applied) driver selects SH

#REQ-DESIGN-CR-0465#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [36]:
(the identity of the over-passed balise group is not in the list of expected balises related to SR mode) AND (override is not active)
#TEST-VAL-SUB026-4898#REF# FCT basic function Transition table 4.6.3 - Conditions 36, 54

#REQ-UNISIG-SUB026-2219:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [37]
(driver selects “override”) AND (train speed is under or equal to the speed limit for triggering the “override” function)
#TEST-VAL-SUB026-5473#REF# EET CFX00040383 Mode transition PT/L2-SR/L2 without reception of M6
#TEST-VAL-SUB026-5932#REF# FCT basic function Availability of driver choice override depending on train speed

#REQ-UNISIG-SUB026-3461#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#ANA-UNISIG-ModeTransition-0003#REF#
condition [38]
(The ERTMS/ETCS on-board equipment is interfaced to the National System through an STM) AND (The ERTMS/ETCS level switches to 0,1,2 or 3) AND
(Emergency Brake is commanded by this STM)

note: see also Subset 35 for details
difference to subset 26, version 3.3.0 - see analysis
#TEST-VAL-SUB026-4493#REF# FCT L0 SN/NTC (EB applied) transition to L0
#TEST-VAL-SUB026-4494#REF# FCT L1 SN/STM (EB applied) - transition to L1
#TEST-VAL-SUB026-4495#REF# FCT L2 SN/STM (EB applied) - transition to L2

#REQ-UNISIG-SUB026-2245#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-0294#REF#
#REQ-UNISIG-SUB026-0298#REF#
#REQ-UNISIG-SUB026-0304#REF#
#REQ-UNISIG-SUB026-0306#REF#
condition [39]
(The ERTMS/ETCS level switches to 1, 2 or 3) AND (no MA has been accepted)
#TEST-VAL-SUB026-5084#REF# FCT L1 Level transition NTC->L1 without L1-MA
#TEST-VAL-SUB026-4253#REF# FCT L2 transition FS(L2) -> UN(L0)[21] -> TR(L2)[39]

#REQ-DESIGN-CR-0050#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [40]:
(A Mode Profile defining an On Sight area is on-board) AND (The max safe front end of the train is inside the On Sight area)
#TEST-VAL-SUB026-4836#REF# FCT L1 mode transition L1 SR->OS[40]->SH[51]
#TEST-VAL-SUB026-5038#REF# FCT L2 OS mode not acknowleged in time
#TEST-VAL-SUB026-8294#REF# EET error expectation Evaluation of MP, estimated front end inside MP, max safe front end outside MP

#REQ-UNISIG-SUB026-2285#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [41]
(T_NVCONTACT is passed) AND (associated reaction is “train trip”)
#TEST-VAL-SUB026-4621#REF# FCT basic function OS->TR[41]

#REQ-DESIGN-CR-0459#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [42]:
(the train/engine overpasses SR distance with its estimated front end) AND (override is not active)
#TEST-VAL-SUB026-5507#REF# FCT basic function End of inhibition to Trip in SR on crossing SR supervised distance

#REQ-DESIGN-CR-0462#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [43]:
(The train/engine overpasses the former EoA (when Override was activated) with the min safe antenna position) AND (override is not active), see
{3} here under
TEST APPROACH:
The following aspects have been identified:
1) evaluation of "former EoA":
1.1) EoA of MA evaluated as former EoA
1.2) override location evaluated as former EoA
2) dependency on override activation
#TEST-VAL-SUB026-5509#REF# FCT 1.1 Retention of EoA when override EoA done in FS/OS
#TEST-VAL-SUB026-5514#REF# FCT 1.2 train position when override is activated in SB/PT is evaluated as former EoA
#TEST-VAL-SUB026-5031#REF# FCT 2 Override, MinFront > EOA
#TEST-VAL-SUB026-5490#REF# EET error expectation SR/L1 - passage of BG with TRIP while override active and later passage of former EoA

#REQ-UNISIG-SUB026-2243:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [44]
(“override” function is active) AND  (ERTMS/ETCS level switches to 1)
#TEST-VAL-SUB026-4255#REF# FCT basic function Override in L0 - level change to L1

#REQ-UNISIG-SUB026-3480#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [45]
(“override” function is active) AND (no unconditional emergency stop message has been received) AND (ERTMS/ETCS level switches to 2 or 3) see
{3} here under
TEST APPROACH:
The aspect dependency on override is covered by condition [39].
The ERTMS/ETCS level switches to 1/0/NTC is covered by [44]/[21]/[56] no additional level dependency is defined here.
The following aspects have been identified:
1) unconditional emergency stop message has been received
2) unconditional emergency stop message has not been received
#TEST-VAL-SUB026-5801#REF# FCT 1 Override active when switching to L2 with unconditional emergency stop within transition buffer
#TEST-VAL-SUB026-5027#REF# FCT 2 Override in L0

#REQ-UNISIG-SUB026-2222:01#REF# 4.6.3 #REQ-UNISIG-SUB026-005100#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
condition [46]
(Driver selects NON LEADING) AND (train is at standstill) AND (The “non leading” input signal is received)
#TEST-VAL-SUB026-5802#REF# FCT basic function Transition to/from NL, NL input signal available

#REQ-UNISIG-SUB026-2240:02#REF# 4.6.3 #REQ-UNISIG-SUB026-005102#REF#
#REQ-UNISIG-SUB026-2214:01#REF#
condition [47]
(no “non leading” input signal is received any more) AND (train is at standstill)
#TEST-VAL-SUB026-5802#REF# FCT basic function Transition to/from NL, NL input signal available

#REQ-DESIGN-CR-0466#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [49]:
(reception of information “stop if in shunting”) AND (override is not active)
#TEST-VAL-SUB026-4899#REF# FCT basic function Transition table 4.6.3 - Condition 49

#REQ-UNISIG-SUB026-2216#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-DESIGN-CR-0062#REF#
condition [50]
(An ackn. request for Shunting is displayed to the driver) AND (the driver acknowledges)    see {5} here under
#TEST-VAL-SUB026-5000#REF# FCT basic function FS->SH

#REQ-DESIGN-CR-0059#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [51]:
(A Mode Profile defining the entry of a Shunting area is used on-board) AND (The max safe front end of the train is inside the Shunting area)
#TEST-VAL-SUB026-4836#REF# FCT L1 mode transition L1 SR->OS[40]->SH[51]
#TEST-VAL-SUB026-4611#REF# FCT L2 Modewechsel SR-> SH [51]
#TEST-VAL-SUB026-8294#REF# EET error expectation Evaluation of MP, estimated front end inside MP, max safe front end outside MP

#REQ-DESIGN-CR-0467#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [52]:
(the identity of the over-passed balise group is not in the list of expected balise groups related to SH mode) AND (override is not active).
#TEST-VAL-SUB026-5467#REF# EET CFX00040838 Reception of M3 with shortened MA, MP-SH and empty list of BG in SH
#TEST-VAL-SUB026-5506#REF# FCT basic function End of inhibition to Trip in SR/SH mode on crossing BG not in expected list of balises

#REQ-DESIGN-CR-0468:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [54]:
(reception of information “stop if in Staff Responsible”) AND (no list of expected balise groups related to SR mode has been received or the
list of expected balise groups related to SR mode does not include the identity of the over-passed balise group) AND (override is not active)
#TEST-VAL-SUB026-5930#REF# FCT dependency on P63/P137 Evaluation of 'stop if in Staff Responsible' depending on P137
#TEST-VAL-SUB026-4898#REF# FCT dependency on override Transition table 4.6.3 - Conditions 36, 54

#REQ-UNISIG-SUB026-2249:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [56]
(the ERTMS/ETCS level switches to “NTC”)
#TEST-VAL-SUB026-4H45#REF# EET CFX00035330 Level transition point L1->STM equals EoA, LT executed before EoA passage evaluation takes place
#TEST-VAL-SUB026-3430#REF# FCT basic function Mode transition SR->SN[56]->SH[61]

#REQ-DESIGN-CR-0110:02#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-010384#REF#
condition [58]
(the ERTMS/ETCS level is “NTC”) AND (an acknowledgement request for SN mode is displayed to the driver) AND (the driver acknowledges)
#TEST-VAL-SUB026-7639#REF# FCT basic function Transition SB->SN

#REQ-UNISIG-SUB026-2291#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-0324#REF#
condition [59]
(train is at standstill) AND (driver has acknowledged the reversing)
#TEST-VAL-SUB026-3169#REF# FCT basic function Reversing

#REQ-UNISIG-SUB026-2223#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-010385#REF#
condition [60]
(an acknowledgement request for UN mode is displayed to the driver) AND (the driver acknowledges)
#TEST-VAL-SUB026-5402#REF# FCT basic function SOM - L0/UN

#REQ-DESIGN-CR-0060#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [61]:
(A Mode Profile defining a Shunting area is on-board) AND (The max safe front end of the train is inside the Shunting area) AND (The ERTMS/ETCS
level switches to 1,2 or 3)
#TEST-VAL-SUB026-3430#REF# FCT L1 Mode transition SR->SN[56]->SH[61]
#TEST-VAL-SUB026-4241#REF# FCT L2 transition FS/L2 - SN/STM - SH/L2
#TEST-VAL-SUB026-8295#REF# EET error expectation Evaluation of buffered MP, estimated front end inside MP, max safe front end outside MP

#REQ-UNISIG-SUB026-2251:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [62]
(the driver acknowledges the train trip) AND (the train is at standstill) AND (the ERTMS/ETCS level is 0) AND (valid Train Data is on-board)
TEST APPROACH:
The condition "the train is at standstill" is evaluated for the activation of the TRIP acknowledgment request.
A train movement after standstill can be excluded from operational point of view as the EB remain active.
Note: Condition [68] covers the case 'no valid Train Data is on-board'.
#TEST-VAL-SUB026-4124#REF# FCT basic function Mode transition SR->TR[54] TR->UN[62]

#REQ-UNISIG-SUB026-2258:02#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [63]
(the driver acknowledges the train trip) AND (the train is at standstill) AND (the ERTMS/ETCS level is NTC) AND (valid Train Data is on-board)
TEST APPROACH:
The condition "the train is at standstill" is evaluated for the activation of the TRIP acknowledgment request.
A train movement after standstill can be excluded from operational point of view as the EB remain active.
Note: Condition [68] covers the case 'no valid Train Data is on-board'.
#TEST-VAL-SUB026-4635#REF# FCT basic function TR->SN[63]

#REQ-UNISIG-SUB026-2233:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [65]
(The system version number X of a received balise telegram is greater than the highest version number X supported by the on-board equipment) AND
(ERTMS/ETCS level is 1, 2 or 3)
#TEST-VAL-SUB026-5412#REF# EET CFX00037093 SH overrive EoA active when receiving balise telegram with a non compatible version
#TEST-VAL-SUB026-5413#REF# EET CFX00037093 SR overrive EoA active when receiving balise telegram with a non compatible version
#TEST-VAL-SUB026-4254#REF# FCT L1 transition SR(L2) -> SR(L1) -> TR(L1)[65]
#TEST-VAL-SUB026-3206#REF# FCT L2 , CFX00037093 BG with unsupported M_VERSION: transition into TR
#TEST-VAL-SUB026-8106#REF# EET error expectation SH/L0 - no Trip when passing BG with unsupported version

#REQ-UNISIG-SUB026-2286#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [66]
A balise group contained in the linking information is passed in the unexpected direction
#TEST-VAL-SUB026-4622#REF# FCT basic function OS->TR[66]

#REQ-UNISIG-SUB026-2244#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3103#REF#
condition [67]
(The ERTMS/ETCS level switches to level 1) AND (a trip order has been received) AND (override is not active)
TEST APPROACH:
Trip order is indicated via P12 which is accepted in L1 only no addition level dependency defined here.
The following aspects have been identified:
1) override active 
2) override inactive
#TEST-VAL-SUB026-5416#REF# FCT 1 Override in SN -> LTO (L1) - trip order -> SR
#TEST-VAL-SUB026-4644#REF# FCT 2 SN->TR[67]

#REQ-UNISIG-SUB026-007623:01#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [68]
(the driver acknowledges the train trip) AND (the train is at standstill) AND (the ERTMS/ETCS level is 0 or NTC) AND (no valid Train Data is
on-board)
TEST APPROACH:
The condition "the train is at standstill" is evaluated for the activation of the TRIP acknowledgment request.
A train movement after standstill can be excluded from operational point of view as the EB remain active.
The following aspects have been identified:
1) dependency on train data
1.1) train data not available
1.2) train data invalid
2) dependency on Level
2.1) L0
2.2) NTC
#TEST-VAL-SUB026-4H32#REF# FCT 1.1, 2.1 , CFX00039885 mode/level transition SH/L1->TR/L1->TR/L0->SH/L0
#TEST-VAL-SUB026-4H31#REF# FCT 2.2 mode/level transition SH/L1->TR/L1->TR/STM->SH/STM
#TEST-VAL-SUB026-7034#REF# FCT 2.2 TRIP acknowledgment train data in state TBR

#REQ-UNISIG-SUB026-006975#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [69]
Estimated train front end is in rear of the start location of either SSP or gradient profile stored on-board.
reason for this trip condition: 
Backward movement after entry in FS/OS mode
#TEST-VAL-SUB026-5261#REF# FCT GP L1 Transition from OS to TR due backward movement out of GP coverage
#TEST-VAL-SUB026-7087#REF# FCT GP L2 Deletion of accepted and stored information when used GP
#TEST-VAL-SUB026-5263#REF# FCT SSP L1 Transition from OS to TR due backward movement out of SSP coverage
#TEST-VAL-SUB026-7086#REF# FCT SSP L2 Deletion of accepted and stored information when used SSP

#REQ-UNISIG-SUB026-3396#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
#REQ-UNISIG-SUB026-3530#REF#
condition [70]
(An ackn. request for Limited Supervision is displayed to the driver) AND (the driver acknowledges)
#TEST-VAL-SUB026-4544#REF# FCT L1 Pkt 72 M_MODETEXTDISPLAY = LS, L1 FS->LS[70]->FS[32]
#TEST-VAL-SUB026-4551#REF# FCT L2 TSR when entering LS, TSR in LS; OS->LS[70]

#REQ-UNISIG-SUB026-3397#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [71]
(A Mode Profile defining a Limited Supervision area is on-board) AND (The max safe front end of the train is inside the Limited Supervision
area) AND (The ERTMS/ETCS level switches to 1,2 or 3)
#TEST-VAL-SUB026-4590#REF# FCT L1 mode transition SN->LS(L1)[71]
#TEST-VAL-SUB026-4554#REF# FCT L2 mode transition UN->LS(L2)[71]->TR[41]
#TEST-VAL-SUB026-8295#REF# EET error expectation Evaluation of buffered MP, estimated front end inside MP, max safe front end outside MP

#REQ-UNISIG-SUB026-3398#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [72]
(A Mode Profile defining a Limited Supervision area is on-board) AND (The max safe front end of the train is inside the Limited Supervision
area).
#TEST-VAL-SUB026-4548#REF# FCT L1 Mode transition L1 SR->LS[72]->SR[37]
#TEST-VAL-SUB026-4546#REF# FCT L2 GeoPos in LS/L2; L2 FS->LS[72]
#TEST-VAL-SUB026-8294#REF# EET error expectation Evaluation of MP, estimated front end inside MP, max safe front end outside MP

#REQ-UNISIG-SUB026-010231#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [73]
(A Mode Profile defining an On Sight area is on-board) AND (The max safe front end of the train is inside the On Sight area) AND (The estimated
front end of the train is not inside an LS acknowledgement area)
UNISIG clarification: The former mode profile element has not to be taken into account any more after acknowledgment of a new mode. The
requirement is no valid for a newly received mode profile.
TEST APPROACH:
1) No fallback to LS after acknowledging OS inside LS area
#TEST-VAL-SUB026-5949#REF# FCT 1 Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind
#TEST-VAL-SUB026-7638#REF# EET error expectation Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind

#REQ-UNISIG-SUB026-010232#REF# 4.6.3 #REQ-UNISIG-SUB026-2214:01#REF#
condition [74]
(A Mode Profile defining a Limited Supervision area is on-board) AND (The max safe front end of the train is inside the Limited Supervision
area) AND (The estimated front end of the train is not inside an OS acknowledgement area)
UNISIG clarification: The former mode profile element has not to be taken into account any more after acknowledgment of a new mode. The
requirement is no valid for a newly received mode profile.
TEST APPROACH:
1) No fallback to OS after acknowledging LS inside OS area
#TEST-VAL-SUB026-5949#REF# FCT 1 Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind
#TEST-VAL-SUB026-7638#REF# EET error expectation Evaluation of MP acknowledgment requests for two non overlapping MP areas of different kind

Chapter 4.7

TEST APPROACH:
The ETCS mode NP is not realized by the SW refer #REQ-UNISIG-SUB026-004698#REF#. There is no active DMI in PS and SL as the desk is closed. The
verification for NP, PS and SL is omitted.
The verification for the ETCS modes SF and IS is limited to #REQ-UNISIG-SUB026-010489#REF# and #REQ-UNISIG-SUB026-010491#REF#.
		
#REQ-UNISIG-SUB026-0248:01#REF# 4.7.2.1.4 #REQ-UNISIG-SUB035-008726#REF#
#REQ-UNISIG-SUB035-008727#REF#
NA = Not Applicable: This concerns the modes SF and IS in which the DMI inputs and outputs cannot be determined.








realised by: #REQ-UNISIG-SUB026-010489#REF#
realised by: #REQ-UNISIG-SUB026-010491#REF#
realised by: #REQ-UNISIG-SUB026-3285:01#REF#
realised by: #REQ-UNISIG-SUB026-3287:01#REF#
realised by: #REQ-UNISIG-SUB026-3290:01#REF#
realised by: #REQ-UNISIG-SUB026-3286#REF#
realised by: #REQ-UNISIG-SUB026-3291:01#REF#
realised by: #REQ-UNISIG-SUB026-3293#REF#
realised by: #REQ-DESIGN-CR-0442:01#REF#
realised by: #REQ-UNISIG-SUB026-3294#REF#
realised by: #REQ-UNISIG-SUB026-3295#REF#
realised by: #REQ-DESIGN-CR-0012#REF#
realised by: #REQ-UNISIG-SUB026-3297#REF#
realised by: #REQ-UNISIG-SUB026-010402#REF#
realised by: #REQ-UNISIG-SUB026-3299#REF#
realised by: #REQ-UNISIG-SUB026-3300#REF#
realised by: #REQ-UNISIG-SUB026-3054#REF#
realised by: #REQ-UNISIG-SUB026-3055#REF#
realised by: #REQ-DESIGN-CR-0101:01#REF#
realised by: #REQ-DESIGN-CR-0051:01#REF#
realised by: #REQ-DESIGN-CR-0128:01#REF#
realised by: #REQ-UNISIG-SUB026-3588:01#REF#
realised by: #REQ-UNISIG-SUB026-3587#REF#
realised by: #REQ-UNISIG-SUB026-3279#REF#
realised by: #REQ-UNISIG-SUB026-010403#REF#
realised by: #REQ-UNISIG-SUB026-3302#REF#
realised by: #REQ-UNISIG-SUB026-010404#REF#
realised by: #REQ-UNISIG-SUB026-010405#REF#
realised by: #REQ-UNISIG-SUB026-010406#REF#
realised by: #REQ-UNISIG-SUB026-010123#REF#
realised by: #REQ-UNISIG-SUB026-010408#REF#
realised by: #REQ-UNISIG-SUB026-010407#REF#
realised by: #REQ-UNISIG-SUB026-3303#REF#
realised by: #REQ-UNISIG-SUB026-3304#REF#
realised by: #REQ-UNISIG-SUB026-010409#REF#
realised by: #REQ-UNISIG-SUB026-010411#REF#
realised by: #REQ-UNISIG-SUB026-3305:02#REF#
realised by: #REQ-UNISIG-SUB026-3306:02#REF#
realised by: #REQ-UNISIG-SUB026-3308:02#REF#
realised by: #REQ-UNISIG-SUB026-3309#REF#
realised by: #REQ-UNISIG-SUB026-010413#REF#
realised by: #REQ-UNISIG-SUB026-3310:01#REF#
realised by: #REQ-UNISIG-SUB026-3311:01#REF#
realised by: #REQ-UNISIG-SUB026-3312#REF#
realised by: #REQ-UNISIG-SUB026-3313:01#REF#
realised by: #REQ-UNISIG-SUB026-3314:01#REF#
realised by: #REQ-UNISIG-SUB026-3316:01#REF#
realised by: #REQ-UNISIG-SUB026-3320:01#REF#
realised by: #REQ-UNISIG-SUB026-3319:01#REF#
realised by: #REQ-UNISIG-SUB026-010414#REF#
realised by: #REQ-UNISIG-SUB026-010415#REF#
realised by: #REQ-UNISIG-SUB026-010416#REF#
realised by: #REQ-UNISIG-SUB026-3056#REF#
realised by: #REQ-UNISIG-SUB026-3057#REF#
realised by: #REQ-UNISIG-SUB026-3325#REF#
realised by: #REQ-DESIGN-CR-0479:03#REF#
realised by: #REQ-UNISIG-SUB026-010389#REF#
realised by: #REQ-DESIGN-CR-0598:01#REF#
realised by: #REQ-DESIGN-CR-0034#REF#
realised by: #REQ-UNISIG-SUB026-010417#REF#
realised by: #REQ-UNISIG-SUB026-3327#REF#
realised by: #REQ-UNISIG-SUB026-3328#REF#
realised by: #REQ-UNISIG-SUB026-3329#REF#
realised by: #REQ-UNISIG-SUB026-3330#REF#
realised by: #REQ-UNISIG-SUB026-3332#REF#
realised by: #REQ-UNISIG-SUB026-3331:01#REF#
realised by: #REQ-UNISIG-SUB026-010418#REF#
realised by: #REQ-UNISIG-SUB026-010419#REF#
realised by: #REQ-UNISIG-SUB026-010420#REF#
realised by: #REQ-UNISIG-SUB026-010421#REF#
realised by: #REQ-UNISIG-SUB026-3281#REF#
realised by: #REQ-UNISIG-SUB026-009509#REF#
realised by: #REQ-UNISIG-SUB026-010422#REF#
realised by: #REQ-UNISIG-SUB026-010424#REF#
realised by: #REQ-UNISIG-SUB026-010423#REF#
realised by: #REQ-UNISIG-SUB026-010425#REF#
realised by: #REQ-UNISIG-SUB026-010426#REF#
realised by: #REQ-UNISIG-SUB026-010427#REF#
realised by: #REQ-UNISIG-SUB026-010428#REF#
realised by: #REQ-UNISIG-SUB026-010429#REF#
realised by: #REQ-UNISIG-SUB026-010430#REF#
realised by: #REQ-UNISIG-SUB026-010432#REF#
realised by: #REQ-UNISIG-SUB026-010431#REF#
realised by: #REQ-UNISIG-SUB026-010433#REF#
realised by: #REQ-UNISIG-SUB026-010434#REF#

#REQ-UNISIG-SUB026-010489#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#REQ-UNISIG-SUB026-3305:02#REF#
When the train is in mode System Failure,
all input information from the DMI shall be ignored
AND
all output information to the DMI shall be suppressed except
- the current mode
- the current time
- system status information, if available
- the information about the active DMI.
UNISIG clarification:
it is necessary to define, which data should be indicated in mode SF
#TEST-VAL-SUB026-7943#REF# FCT basic function Input/Output information in SF

#REQ-UNISIG-SUB026-010491#REF# 4.7.2 #REQ-SAD-Isolation-0003#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
#REQ-UNISIG-SUB026-3305:02#REF#
When the train is in mode Isolation,
- all input information from the DMI shall be ignored
AND
- all output information to the DMI shall be suppressed.
mode IS is realized via HW (EVC is switched off).
The application should suppress all indications and doesn't allowed any driver action.
#ANALYSE-VALUNISIG-7530#REF# FCT The requirement is realised by the module MMI, the requirement is tested by MMI module test.

#REQ-UNISIG-SUB026-3285:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Train Data (refer to 3.18.3.2)"
available: SB, FS, LS, SR, OS, UN, SN
is realized with enabling conditions for button "train data" in ERA SRS DMI

The enabling conditions are valid for the main window only. 
The conditions in the dialogue sequences, especially in the Start Up dialogue sequence, are described separately.
#TEST-VAL-SUB026-4593#REF# FCT dependency on standstill driver choice input train data unavailable if condition -train is at standstill not fulfilled

#REQ-UNISIG-SUB026-3287:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Selection of language"
active: -
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV
is realized with enabling conditions for button "language (soft)" in ERA SRS DMI

#REQ-UNISIG-SUB026-3290:01#REF# 4.7.2 #REQ-UNISIG-SUB026-2020#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Input information "Driver id"
available: SB, SH, FS, LS, SR, OS, NL, UN,  SN
is realized with enabling conditions for button "driver ID" in ERA SRS DMI

The enabling conditions are valid for the main window only. 
The conditions in the dialogue sequences, especially in the Start Up dialogue sequence, are described separately.
#TEST-VAL-SUB026-3785#REF# FCT dependency on M_NVDERUN Effect of M_NVDERUN for availibility of driver choice change driver id

#REQ-UNISIG-SUB026-3286#REF# 4.7.2 #REQ-UNISIG-SUB026-0123:01#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Input information "Train running number"
available: SB, FS, LS, SR, OS, NL, UN, SN
is realized with enabling conditions for button "Train running number" in ERA SRS DMI

The enabling conditions are valid for the main window only. 
The conditions in the dialogue sequences, especially in the Start Up dialogue sequence, are described separately.

#REQ-UNISIG-SUB026-3291:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "ERTMS/ETCS Level"
available: SB, FS, LS, SR, OS, NL, UN, SN
is realized with enabling conditions for button "Level" in ERA SRS DMI

The enabling conditions are valid for the main window only. 
The conditions in the dialogue sequences, especially in the Start Up dialogue sequence, are described separately.

#REQ-UNISIG-SUB026-3293#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Track Adhesion factor"
available: SB, FS, LS, SR, OS, UN, SN
is realized with enabling conditions for button "Adhesion" in ERA SRS DMI
#TEST-VAL-SUB026-4594#REF# FCT dependency on Q_NVDRIVER_ADHES Driver choice change of ahesion factor unavailable if condition 'Q_NVDRIVER_ADHES=1' not fulfilled

#REQ-DESIGN-CR-0442:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "RBC contact information
- Radio network-id
- RBC-id
- RBC phone number"
available: SB, FS, LS, SR, OS, NL, PT
is realized with enabling conditions for the buttons in RBC contact window in ERA SRS DMI

#REQ-UNISIG-SUB026-3294#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Train Integrity"
available: SB, FS, LS, SR, OS, PT
is realized with enabling conditions for the button "Train integrity" in ERA SRS DMI

#REQ-UNISIG-SUB026-3295#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Start"
available: SB, SR, PT
is realized with enabling conditions for the button "Start" in ERA SRS DMI

#REQ-DESIGN-CR-0012#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Override request"
available: SB, SH, FS, LS, SR, OS, UN, PT, SN
is realized with enabling conditions for the button "EoA" in ERA SRS DMI

#REQ-UNISIG-SUB026-3297#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Shunting request"
available: SB, FS, LS, SR, OS, UN, PT, SN
is realized with enabling conditions for the button "Shunting" in ERA SRS DMI

#REQ-UNISIG-SUB026-010402#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "“Continue Shunting on desk closure” request"
available: SH
is realized with enabling conditions for the button "Maintain Shunting" in ERA SRS DMI

#REQ-UNISIG-SUB026-3299#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information ""Exit of Shunting" request"
available: SH
UNISIG clarification:
the classification is only available, not active,  because a second condition "train is standstill" is valid

is realized with enabling conditions for the button "Exit Shunting" in ERA SRS DMI
#TEST-VAL-SUB026-7134#REF# FCT basic function mode transition SR(L1) -> SH[5] -> SB[19]

#REQ-UNISIG-SUB026-3300#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Non Leading request"
available: SB, SH, FS, LS, SR, OS
is realized with enabling conditions for the button "Non-Leading" in ERA SRS DMI

#REQ-UNISIG-SUB026-3054#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn of fixed text information"
available: SB, FS, LS, SR, OS, NL, UN, TR, PT, RV
UNISIG clarification: an ACK should be possible independ on a mode, when a text message is displayed
=> the same realization as Output information "Fixed text information"
realised by: #REQ-DESIGN-CR-0560:02#REF#

#REQ-UNISIG-SUB026-3055#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn of plain text information"
available: SB, FS, LS, SR, OS, NL, UN, TR, PT, RV
UNISIG clarification: an ACK should be possible independ on a mode, when a text message is displayed
=> the same realization as Output information "plain text information"
realised by: #REQ-DESIGN-CR-0560:02#REF#

#REQ-DESIGN-CR-0101:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#REQ-UNISIG-SUB026-0838#REF#
Input Information "Ackn of level transition"
available: SB, FS, LS, SR, OS, UN, TR, SN
TEST APPROACH:
In SH, the ASW shall not manage level transitions (see #REQ-UNISIG-SUB026-010115#REF#).
Level transition orders and conditional level transition orders are rejected in RV (see #REQ-UNISIG-SUB026-3466:01#REF# and
#REQ-DESIGN-CR-0740:03#REF#) and this type of stored information is deleted when entering RV (see #REQ-DESIGN-DATEN-0008:02#REF#).
Hence, modes SH and RV will be omitted.
#TEST-VAL-SUB026-5134#REF# EET CFX00034266 Manuelle Levelwahl Level 1 zu Level 0 erfordert Quittung
#TEST-VAL-SUB026-4C35#REF# FCT FS Stored data: Mode Profile when mode changes to UN/L0, FS/L1
#TEST-VAL-SUB026-4571#REF# FCT LS LS/L2 - STM system speed and distance and STM max speed; LS->SN[56]
#TEST-VAL-SUB026-5095#REF# FCT NL Keine Quittierungsaufforderung bei level transition von L1 nach L0, Mode NL
#TEST-VAL-SUB026-4120#REF# FCT OS Modewechsel: Von OS nach UN wegen [21]
#TEST-VAL-SUB026-5489#REF# FCT PT PT/L2 - immediate level transition order from RBC rejected
#TEST-VAL-SUB026-4533#REF# FCT SB SB/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4557#REF# FCT SN mode transition SN->LS(L2)[71]->TR[16]
#TEST-VAL-SUB026-4482#REF# FCT SR SR/L1 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4635#REF# FCT TR TR->SN[63]
#TEST-VAL-SUB026-5089#REF# FCT UN Acknowledgment request at level transition L0 to NTC
#TEST-VAL-SUB026-5096#REF# EET error expectation No acknowledgement required in SL(transition L1->L0)

#REQ-UNISIG-SUB026-010507#REF# to.4.7.2 #ANA-UNISIG-DriverInput-0001#REF#
If a stored immediate LTO is executed after leaving SH or PS, a acknowledgement of level transition shall be requested in mode TRIP only.
UNISIG clarification:
when obu changes from SH/PS to SB, a SoM is started. Therefore an ACK for LTO is not necessary.
TEST APPROACH:
From mode SH, valid mode transitions are defined to: SB, PS, TR, SF, IS, NL.
From mode PS, valid mode transitions are defined to: SB, SH, SL, SF, IS.
In modes IS, SF the DMI output information ' Acknowledgement of level transition' is not applicable. 
In modes PS and SL, the desk is closed. 
Therefore, the following transitions are verified, in case a LTO/CLTO is received in modes SH and PS, and level acknowledgement is required as
defined in UNISIG SUB026 ch. 5.10.4.4
1) LTO/CLTO received in SH. Mode transition to:
1.1) SB
1.2) TR
1.3) NL
2) LTO/CLTO received in PS. Mode transition to:
2.1) SB
2.2) TR (via SH)
2.3) NL (via SH)
#TEST-VAL-SUB026-7954#REF# FCT 1.1 LT acknowledgement after leaving SH to SB
#TEST-VAL-SUB026-7953#REF# FCT 1.2 LT acknowledgement after leaving SH to TR
#TEST-VAL-SUB026-7960#REF# FCT 1.3 LT acknowledgement after leaving SH to NL
#TEST-VAL-SUB026-7955#REF# FCT 2.1, 2.2 LT acknowledgement after leaving PS to TR (via SB, SH)
#TEST-VAL-SUB026-7961#REF# FCT 2.3 LT acknowledgement after leaving PS to NL (via SB, SH)

#REQ-UNISIG-SUB026-3507#REF# 4.7.2 #ANA-UNISIG-InputData-0018#REF#
Input Information "Ackn of Limited Supervision mode"
available: SB, FS, LS, OS, PT
UNISIG clarification:
the mode dependency is only relevant for the beginning	of the request. 

The driver has to acknowledge a pending request independent if it is still relevant or not.

realize procedure
SoM - S25
PT - S170
LS
realised by: #REQ-UNISIG-SUB026-3515#REF#
realised by: #REQ-UNISIG-SUB026-3524#REF#
realised by: #REQ-UNISIG-SUB026-3697#REF#

#REQ-DESIGN-CR-0051:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-InputData-0018#REF#
Input Information "Ackn of On Sight mode"
available: SB, FS, LS, OS, PT
UNISIG clarification:
the mode dependency is only relevant for the beginning	of the request. 

The driver has to acknowledge a pending request independent if it is still relevant or not.

realize procedure
SoM - S25
PT - S170
OS
realised by: #REQ-UNISIG-SUB026-0275#REF#
realised by: #REQ-UNISIG-SUB026-0280#REF#
realised by: #REQ-UNISIG-SUB026-3695#REF#

#REQ-DESIGN-CR-0128:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-InputData-0018#REF#
Input Information "Ackn of Shunting mode"
available: SB, SH, FS, LS, OS, PT
UNISIG clarification:
the mode dependency is only relevant for the beginning	of the request. 

The driver has to acknowledge a pending request independent if it is still relevant or not.

this ACK correspond with the ACK after receiving a mode profile to SH

realize procedure
SoM - S25
PT - S170
SH initiated by trackside
realised by: #REQ-UNISIG-SUB026-0784:02#REF#
realised by: #REQ-UNISIG-SUB026-0789#REF#
realised by: #REQ-UNISIG-SUB026-3696#REF#

#REQ-UNISIG-SUB026-3588:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn of Staff Resp. mode"
available: SB, PT
UNISIG clarification:
the mode dependency is only relevant for the beginning	of the request. 

The driver has to acknowledge a pending request independent if it is still relevant or not.

realize through procedure
SoM - S24
PT - S160
realised by: #REQ-UNISIG-SUB026-010386#REF#
realised by: #REQ-DESIGN-CR-0136:01#REF#

#REQ-UNISIG-SUB026-3587#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn of Unfitted mode"
available: SB
UNISIG clarification:
the mode dependency is only relevant for the beginning	of the request. 

The driver has to acknowledge a pending request independent if it is still relevant or not.

realize through procedure SoM - S23
realised by: #REQ-UNISIG-SUB026-010385#REF#

#REQ-UNISIG-SUB026-3279#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn of Reversing mode"
available: FS, LS, OS
UNISIG clarification:
the mode dependency is only relevant for the beginning	of the request. 

The driver has to acknowledge a pending request independent if it is still relevant or not.
TEST APPROACH:
RV area and supervision information is only received in modes FS, LS, SR, OS and RV, and deleted when entering any other mode apart from FS, LS,
OS and RV (mode PT can only be entered from TR).
As the acknowledgement of Reversing mode leads to transition to mode RV, the verification focuses on modes FS, LS, SR, OS.
#TEST-VAL-SUB026-4C19#REF# FCT FS Stored data: Reversing Area Information and Reversing Supervision Information when changing to RV/L2
#TEST-VAL-SUB026-4562#REF# FCT LS mode change LS->RV[59]
#TEST-VAL-SUB026-4C23#REF# FCT OS Stored data: Reversing Area Information and Reversing Supervision Information OS/L2
#TEST-VAL-SUB026-4C22#REF# FCT SR Stored data: Reversing Area Information and Reversing Supervision Information SR/L2, FS/L2

#REQ-UNISIG-SUB026-010403#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn of SN mode"
available: SB
UNISIG clarification:
the mode dependency is only relevant for the beginning	of the request. 

The driver has to acknowledge a pending request independent if it is still relevant or not.

realize through procedure SoM - S22
realised by: #REQ-UNISIG-SUB026-010384#REF#

#REQ-UNISIG-SUB026-3302#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Ackn of Train Trip"
available: TR
realize through Procedure Train Trip, S060
realised by: #REQ-DESIGN-CR-0176:01#REF#

#REQ-UNISIG-SUB026-010404#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn for Roll Away Protection"
available: SH, FS, LS, SR, OS, UN, PT, RV
The Ackn is depend on the conditions for releasing the brake allone
realised by: #REQ-UNISIG-SUB026-0622#REF#

#REQ-UNISIG-SUB026-010405#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn for Reverse Movement Protection"
available: FS, LS, SR, OS, PT, RV
The Ackn is depend on the conditions for releasing the brake allone
realised by: #REQ-UNISIG-SUB026-0622#REF#

#REQ-UNISIG-SUB026-010406#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn for Standstill  Supervision"
available: SB
The Ackn is depend on the conditions for releasing the brake allone
realised by: #REQ-UNISIG-SUB026-0622#REF#

#REQ-UNISIG-SUB026-010123#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn for Post Trip distance exceeded"
available: PT
The Ackn is depend on the conditions for releasing the brake allone
realised by: #REQ-UNISIG-SUB026-3548:01#REF#

#REQ-UNISIG-SUB026-010408#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn of Train Data change from source different from the driver"
available: FS, LS, SR, OS, UN, TR, SN
The Ackn is depend on the conditions for releasing the brake allone
realised by: #REQ-UNISIG-SUB026-003427#REF#

#REQ-UNISIG-SUB026-010407#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Ackn for Reversing distance exceeded"
available: RV
The Ackn is depend on the conditions for releasing the brake allone
realised by: #REQ-UNISIG-SUB026-3098#REF#

#REQ-UNISIG-SUB026-3303#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "Track Ahead Free"
available: SB, LS, SR, OS, PT
is part of the TAF function and realizes with the defined mode dependency for this function in 4.5.2
realised by: #REQ-UNISIG-SUB026-1065:01#REF#

#REQ-UNISIG-SUB026-3304#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input information "SR mode speed limit and distance"
available: SR
is realized with enabling conditions for the button "SR speed / distance" in ERA SRS DMI

#REQ-UNISIG-SUB026-010409#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Virtual Balise Cover"
available: SB
is realized with enabling conditions for the buttons "Set VBC" and "Remove VBC" in ERA SRS DMI

#REQ-UNISIG-SUB026-010411#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Input Information "Isolation"
active: all modes

--- FINALISED ---
The Isolation input is defined independent of any mode restriction.
#ANALYSE-VALUNISIG-5279#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-3305:02#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "ERTMS/ETCS mode"
active: SH, FS, LS, SR, OS, NL, UN, TR, PT, IS, SN, RV
available: SB, TR, SF
"available: SB, TR, SF" means:
a desk is open and therefore an active DMI is available

special requirements exists for SF and IS.
other mode dependencies are not necessary
--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
TEST APPROACH:
The indication of the mode other than IS, SF is covered by #REQ-SAS_DMI-003248#REF#.
realised by: #REQ-UNISIG-SUB026-010489#REF#
realised by: #REQ-UNISIG-SUB026-010491#REF#

#REQ-UNISIG-SUB026-3306:02#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "ERTMS/ETCS level"
active: SH, FS, LS, SR, OS, NL, UN, PT, SN, RV
available: SB, TR
"available: SB, TR" means:
a desk is open and therefore an active DMI is available

a mode dependency is not necessary
--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
TEST APPROACH:
A mode dependency is not necessary (ref. column FINALIZED). The scope of the tests outlined here is to verify that the correct level symbols are
displayed according to actual level.
#TEST-VAL-SUB026-4398#REF# FCT L0, L1, L2 Position Report parameters when entering FS(L2)/UN/FS(L1)
#TEST-VAL-SUB026-5713#REF# FCT L3 Acceptance of SR Authorisation + List of Balises in SR mode in L3
#TEST-VAL-SUB026-5089#REF# FCT NTC Acknowledgment request at level transition L0 to NTC

#REQ-UNISIG-SUB026-3308:02#REF# 4.7.2 #REQ-UNISIG-SUB026-0173:01#REF#
#REQ-UNISIG-SUB026-004879#REF#
#REQ-DESIGN-CR-0487#REF#
#REQ-UNISIG-SUB026-001798#REF#
#REQ-UNISIG-SUB026-001814#REF#
#REQ-UNISIG-SUB026-007482#REF#
#REQ-UNISIG-SUB026-3359#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Output information "Train Speed"
active: SH, FS, LS, SR, OS, NL, UN, TR, PT, RV
available: SB, SN
#TEST-VAL-SUB026-4364#REF# FCT FS PR at level change, standstill in FS, determine train speed and location
#TEST-VAL-SUB026-4574#REF# FCT LS PR at level, standstill in LS, determine train speed and location in LS
#TEST-VAL-SUB026-4369#REF# FCT NL PR when establishing a session with RBC, determine train speed and location in NL
#TEST-VAL-SUB026-4365#REF# FCT OS PR at level, standstill in OS, determine train speed and location
#TEST-VAL-SUB026-4372#REF# FCT PT PR when establishing a session with RBC, determine train speed and location in PT
#TEST-VAL-SUB026-4363#REF# FCT RV PR at mode change to RV, PR at standstill in RV, determine train speed and location
#TEST-VAL-SUB026-4367#REF# FCT SB PR at level change, when establishing a session with RBC, determine train speed and location
#TEST-VAL-SUB026-4366#REF# FCT SH no PR at level change, standstill in SH, determine train speed and location in SH
#TEST-VAL-SUB026-4496#REF# FCT SN 4.7.2 SN - permitted/target/release speed, target distance and warning, FS permitted speed and warning
#TEST-VAL-SUB026-4A01#REF# FCT SR PR at level, standstill in SR, determine train speed and location in SR
#TEST-VAL-SUB026-4371#REF# FCT TR PR when establishing a session with RBC, determine train speed and location in TR
#TEST-VAL-SUB026-4000#REF# FCT UN UN/L0 - no supervisory information indicated to the driver MMI except the train speed

#REQ-UNISIG-SUB026-3309#REF# 4.7.2 #REQ-UNISIG-SUB026-0173:01#REF#
#REQ-UNISIG-SUB026-004879#REF#
#REQ-UNISIG-SUB026-001798#REF#
#REQ-UNISIG-SUB026-001814#REF#
#REQ-UNISIG-SUB026-007482#REF#
#REQ-UNISIG-SUB026-3359#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Output information "Permitted Speed"
active: FS
available: SH, LS, SR, OS, RV
TEST APPROACH:
The correct display of information is sufficiently tested by MMI module tests and the test cases outlined to ERA DMI requirements. The test
cases outlined here focus only on the modes where the information is available / displayed and check that the provided values are according to
OBU conditions.
#TEST-VAL-SUB026-4496#REF# FCT FS 4.7.2 SN - permitted/target/release speed, target distance and warning, FS permitted speed and warning
#TEST-VAL-SUB026-4595#REF# FCT LS DMI output warning in LS available, permitted speed in TR, PT, NL not available
#TEST-VAL-SUB026-4141#REF# FCT OS OS - supervised data on MMI in TSM/RSM
#TEST-VAL-SUB026-4562#REF# FCT RV mode change LS->RV[59]
#TEST-VAL-SUB026-5257#REF# FCT SH Indication of permitted speed and acceptance of RBC transition order in SH
#TEST-VAL-SUB026-4841#REF# FCT SR Provision of permitted speed in SR/OS
#TEST-VAL-SUB026-3725#REF# FCT SR override L0->L2 Level transition buffer information evaluation due to train category change

#REQ-UNISIG-SUB026-010413#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "FLOI Speed"
available: FS
TEST APPROACH:
The correct display of information is sufficiently tested by MMI module tests and the test cases outlined to ERA DMI requirements. The test
cases outlined here focus only on the modes where the information is available / displayed and check that the provided values are according to
OBU conditions.
#TEST-VAL-SUB026-5230#REF# FCT basic function Ceiling supervision limits based on MRSP

#REQ-UNISIG-SUB026-3310:01#REF# 4.7.2 #REQ-UNISIG-SUB026-004879#REF#
#REQ-UNISIG-SUB026-001798#REF#
#REQ-UNISIG-SUB026-001814#REF#
#REQ-UNISIG-SUB026-3359#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Output information "Target Speed"
available: FS, SR, LS, OS
TEST APPROACH:
The correct display of information is sufficiently tested by MMI module tests and the test cases outlined to ERA DMI requirements. The test
cases outlined here focus only on the modes where the information is available / displayed and check that the provided values are according to
OBU conditions.
#TEST-VAL-SUB026-5235#REF# FCT FS Display of target speed/distance and release speed in FS
#TEST-VAL-SUB026-4840#REF# FCT LS provision of target speed/distance in RV/LS
#TEST-VAL-SUB026-4141#REF# FCT OS OS - supervised data on MMI in TSM/RSM
#TEST-VAL-SUB026-5236#REF# FCT SR Display of target speed/distance in SR/OS and release speed in OS

#REQ-UNISIG-SUB026-3311:01#REF# 4.7.2 #REQ-UNISIG-SUB026-004879#REF#
#REQ-UNISIG-SUB026-001798#REF#
#REQ-UNISIG-SUB026-001814#REF#
#REQ-UNISIG-SUB026-007482#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Output information "Target Distance"
active: RV
available: FS, SR, OS

remark:
in RV the reverse distance is meant.
UNISIG clarficiation:
the reversing distance is shown as target distance in mode RV
TEST APPROACH:
The correct display of information is sufficiently tested by MMI module tests and the test cases outlined to ERA DMI requirements. The test
cases outlined here focus only on the modes where the information is available / displayed and check that the provided values are according to
OBU conditions.
#TEST-VAL-SUB026-5235#REF# FCT FS Display of target speed/distance and release speed in FS
#TEST-VAL-SUB026-4840#REF# FCT LS, RV provision of target speed/distance in RV/LS
#TEST-VAL-SUB026-4141#REF# FCT OS OS - supervised data on MMI in TSM/RSM
#TEST-VAL-SUB026-5236#REF# FCT SR Display of target speed/distance in SR/OS and release speed in OS

#REQ-UNISIG-SUB026-3312#REF# 4.7.2 #REQ-UNISIG-SUB026-001814#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Output information "Release Speed"
available: FS, LS, OS
TEST APPROACH:
The correct display of information is sufficiently tested by MMI module tests and the test cases outlined to ERA DMI requirements. The test
cases outlined here focus only on the modes where the information is available / displayed and check that the provided values are according to
OBU conditions.
#TEST-VAL-SUB026-5235#REF# FCT FS Display of target speed/distance and release speed in FS
#TEST-VAL-SUB026-4840#REF# FCT LS provision of target speed/distance in RV/LS
#TEST-VAL-SUB026-4141#REF# FCT OS OS - supervised data on MMI in TSM/RSM
#TEST-VAL-SUB026-4533#REF# EET error expectation SB/L2 - STM system speed and distance and STM max speed

#REQ-UNISIG-SUB026-3313:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0015#REF#
Output information "Speed and distance monitoring supervision status"
available: SH, FS, LS, SR, OS, UN, RV
UNISIG clarification:
"Speed and distance monitoring supervision status" doesn't indicated in PT.
TEST APPROACH:
The correct display of information is sufficiently tested by MMI module tests and the test cases outlined to ERA DMI requirements. The test
cases outlined here focus only on the modes where the information is available / displayed and check that the provided values are according to
OBU conditions.
#TEST-VAL-SUB026-4496#REF# FCT FS 4.7.2 SN - permitted/target/release speed, target distance and warning, FS permitted speed and warning
#TEST-VAL-SUB026-4595#REF# FCT LS DMI output warning in LS available, permitted speed in TR, PT, NL not available
#TEST-VAL-SUB026-3751#REF# FCT OS OS mode speed limit V_MAMODE< V_NVONSIGHT
#TEST-VAL-SUB026-4886#REF# FCT RV Speed supervision in RV using ceiling speed given from trackside
#TEST-VAL-SUB026-4A19#REF# FCT SH Determine Most Restrictive Speed Profile, based on Mode SH
#TEST-VAL-SUB026-4842#REF# FCT SR brake intervention when exceeding V_NVSTFF
#TEST-VAL-SUB026-4843#REF# FCT UN brake intervention when exceeding V_NVUNFIT

#REQ-UNISIG-SUB026-3314:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Trip Reason"
available: TR
realizes through 4.4.13.1.3
realised by: #REQ-UNISIG-SUB026-0205#REF#

#REQ-UNISIG-SUB026-3316:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Train Data"
available: SB, FS, LS, SR, OS, UN, TR, PT, SN, RV
UNISIG clarification
is a part of data view and can displayed, when data view is possible and the data is valid.
Exception: SH, NL

if the train changed to SH/NL, the train data are set TBR => train data does'nt displayed in SH/NL, because the are not valid
--- FINALISED ---
The information is a part of data view. Data view is enabled without an enabling condition on the DMI (see ERA SRS DMI).
Therefore the data view is not possible in
- PS, SL (no active DMI)
- SF, IS (a driver input is'nt permitted)
In all other modes the information can be displayed, if the are valid.
#ANALYSE-VALUNISIG-5282#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-3320:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Driver ID"
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV
is a part of data view and can displayed, when data view is possible and the data is valid.
--- FINALISED ---
The information is a part of data view. Data view is enabled without an enabling condition on the DMI (see ERA SRS DMI).
Therefore the data view is not possible in
- PS, SL (no active DMI)
- SF, IS (a driver input is'nt permitted)
In all other modes the information can be displayed, if the are valid.
#ANALYSE-VALUNISIG-5283#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-3319:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Train running number"
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV
is a part of data view and can displayed, when data view is possible and the data is valid.
--- FINALISED ---
The information is a part of data view. Data view is enabled without an enabling condition on the DMI (see ERA SRS DMI).
Therefore the data view is not possible in
- PS, SL (no active DMI)
- SF, IS (a driver input is'nt permitted)
In all other modes the information can be displayed, if the are valid.
#ANALYSE-VALUNISIG-5284#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010414#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "RBC contact information
- Radio network-id
- RBC-id
- RBC phone number"
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV
is a part of data view and can displayed, when data view is possible and the data is valid.
--- FINALISED ---
The information is a part of data view. Data view is enabled without an enabling condition on the DMI (see ERA SRS DMI).
Therefore the data view is not possible in
- PS, SL (no active DMI)
- SF, IS (a driver input is'nt permitted)
In all other modes the information can be displayed, if the are valid.
#ANALYSE-VALUNISIG-5285#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010415#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Virtual Balise Covers"
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV
is a part of data view and can displayed, when data view is possible and the data is valid.
--- FINALISED ---
The information is a part of data view. Data view is enabled without an enabling condition on the DMI (see ERA SRS DMI).
Therefore the data view is not possible in
- PS, SL (no active DMI)
- SF, IS (a driver input is'nt permitted)
In all other modes the information can be displayed, if the are valid.
#ANALYSE-VALUNISIG-5286#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010416#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Brake indication"
available: SB, FS, LS, SR, OS, UN, TR, PT, SN, RV

--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
#ANALYSE-VALUNISIG-5287#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-3056#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Fixed text information"
available: SB, FS, LS, SR, OS, NL, UN, TR, PT, RV
UNISIG clarification:a text message should be displayed only depend on the own conditions and not additional of the current mode
realised by: #REQ-DESIGN-CR-0560:02#REF#

#REQ-UNISIG-SUB026-3057#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Plain text information"
available: SB, FS, LS, SR, OS, NL, UN, TR, PT, RV
UNISIG clarification:a text message should be displayed only depend on the own conditions and not additional of the current mode
realised by: #REQ-DESIGN-CR-0560:02#REF#

#REQ-UNISIG-SUB026-3325#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Reversing allowed"
available: FS, LS, OS

remark: the state "Reversing permitted" is meant
UNISIG clarification:
this output means the state reversing permitted (see ERA SRS DMI - status symbols)
TEST APPROACH:
RV information is buffered in L0/LSTM and rejected in PS, SH, SL, NL and TR. RV information is deleted when entering any other mode than FS, OS,
LS, PT and RV. The test is limited to the modes FS, OS, LS, SB, SR and PT.
#TEST-VAL-SUB026-4562#REF# FCT LS mode change LS->RV[59]
#TEST-VAL-SUB026-4C23#REF# FCT OS Stored data: Reversing Area Information and Reversing Supervision Information OS/L2
#TEST-VAL-SUB026-7055#REF# FCT SB, SR, FS, PT Output information 'Reversing allowed'

#REQ-DESIGN-CR-0479:03#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0016#REF#
Output information
Track condition excluding sound horn, non stopping areas, tunnel stopping areas and big metal masses
  Power control
  Pantograph control
  Air tightness  control
  Radio hole, supervision of safe radio connection stopped
  Brakes control

available: FS, LS, OS, NL, TR, PT
the mode dependency is only relevant for the actual order, not for the planning area (see analysis)

management and display are one
=> is realized with 4.5.2
realised by: #REQ-DESIGN-CR-0481:02#REF#

#REQ-UNISIG-SUB026-010389#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0016#REF#
Output information
Track conditions sound horn, non stopping areas, tunnel stopping areas

available: FS, LS, OS
the mode dependency is only relevant for the actual order, not for the planning area (see analysis)

management and display are one
=> is realized with 4.5.2
realised by: #REQ-UNISIG-SUB026-010388#REF#

#REQ-DESIGN-CR-0598:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Geographical position"
available: SB, FS, LS, SR, OS, NL, UN, TR, PT
management and display	mode dependency are one
=> is realized with 4.5.2 and 3.6.6.1
realised by: #REQ-UNISIG-SUB026-0020:01#REF#
realised by: #REQ-UNISIG-SUB026-1018:02#REF#

#REQ-DESIGN-CR-0034#REF# 4.7.2 #REQ-UNISIG-SUB026-001798#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
Output information "override status"
available: SH, SR, UN,	SN
management and display mode dependency are one
=> is realized with 4.5.2 and 5.8.3.7
realised by: #REQ-DESIGN-CR-0097:02#REF#
realised by: #REQ-DESIGN-CR-0183#REF#

#REQ-UNISIG-SUB026-010417#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "LX status "not protected"
available: FS, LS, OS
management and display mode dependency are one
=> is realized with 4.5.2 and 5.16.1.4
realised by: #REQ-UNISIG-SUB026-1042:02#REF#
realised by: #REQ-UNISIG-SUB026-006662#REF#

#REQ-UNISIG-SUB026-3327#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Shunting refused by RBC"
available: SB, FS, LS, SR, OS, PT
UNISIG clarification:
The procedure "Shunting initiated by Driver" defines the modes and level dependency. The result of the procedure should be indicated
independend of a mode.
=> is realized with A220 in the procedure
realised by: #REQ-UNISIG-SUB026-0994:01#REF#

#REQ-UNISIG-SUB026-3328#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Shunting  request not answered by RBC"
available: SB, FS, LS, SR, OS, PT
UNISIG clarification:
The procedure "Shunting initiated by Driver" defines the modes and level dependency. The result of the procedure should be indicated
independend of a mode.
realised by: #REQ-UNISIG-SUB026-010557#REF#

#REQ-UNISIG-SUB026-3329#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Accepted Emergency Stop(s)"
available: FS, LS, OS, TR, PT
UNISIG clarification: if an emergency stop is active, this should be displayed independent of the current mode
=> is realized with 3.10.2.6

there is only a difference in mode SB (UES is accpeted in SB). But obu changes immediatly to TR, if an UES is accepted in SB.
realised by: #REQ-UNISIG-SUB026-001865#REF#

#REQ-UNISIG-SUB026-3330#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0008#REF#
Output information "Entry in FS/OS"
available: FS, OS
realize through 4.4.9.1.4 and 4.4.12.1.7
realised by: #REQ-UNISIG-SUB026-0178#REF#
realised by: #REQ-UNISIG-SUB026-0201#REF#

#REQ-UNISIG-SUB026-3332#REF# 4.7.2 #REQ-UNISIG-SUB026-0193#REF#
#REQ-UNISIG-SUB026-0735#REF#
#REQ-UNISIG-SUB026-3360#REF#
#REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0011#REF#
Output information "Track Ahead Free request"
active: -
available: SB, LS, SR, OS, PT
realizes through table 4.5.2 line "Manage Track Ahead Free Request"
realised by: #REQ-UNISIG-SUB026-1065:01#REF#

#REQ-UNISIG-SUB026-3331:01#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Level transition announcement"
active: -
available: SB, FS, LS, SR, OS, NL, UN, TR, PT, SN
UNISIG clarification: 
SB is forgotten

the modes corresponds with the modes in the acceptance list 4.8.4. Therefore a separate requirement for a mode dependency  output information
isn't necessary. 
=> is realized with 4.8.4 and 5.10.1.3.
realised by: #REQ-UNISIG-SUB026-3466:01#REF#
realised by: #REQ-UNISIG-SUB026-0816#REF#

#REQ-UNISIG-SUB026-3321:01#REF# 4.7.2
Output information "Adhesion factor "slippery rail""
available: SB, FS, LS, SR, OS, UN, TR, PT, SN, RV
the modes are conformed with the summarized modes from the tables 4.8.4, 4.10 
and the enabling condition for the driver input.

=> is realized with the two tables, the enabling conditions and 3.18.4.6.2.3
realised by: #REQ-UNISIG-SUB026-2023:01#REF#
realised by: #REQ-UNISIG-SUB026-010061#REF#
realised by: #REQ-UNISIG-SUB026-3637:01#REF#
realised by: #REQ-UNISIG-SUB026-3638:01#REF#

#REQ-UNISIG-SUB026-010418#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0017#REF#
Output Information "SR mode proposed"
available: SB, PT
is realized with procedure
SoM - S24
PT - S160
realised by: #REQ-UNISIG-SUB026-010386#REF#
realised by: #REQ-DESIGN-CR-0136:01#REF#

#REQ-UNISIG-SUB026-010419#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0017#REF#
Output Information "OS/LS/SH mode proposed"
available: SB, PT
is realized with OS/LS/SH procedure
realised by: #REQ-UNISIG-SUB026-3696#REF#
realised by: #REQ-UNISIG-SUB026-3695#REF#
realised by: #REQ-UNISIG-SUB026-3697#REF#

#REQ-UNISIG-SUB026-010420#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0017#REF#
Output Information "SN mode proposed"
available: SB
is realized with SoM - S22
realised by: #REQ-UNISIG-SUB026-010384#REF#

#REQ-UNISIG-SUB026-010421#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0017#REF#
Output Information "UN mode proposed"
available: SB
is realized with SoM - S23
realised by: #REQ-UNISIG-SUB026-010385#REF#

#REQ-UNISIG-SUB026-3281#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
#ANA-UNISIG-OutputData-0017#REF#
Output Information "RV mode proposed"
available: FS, LS, OS
is realized with 5.13.1.4

UNISIG clarification:
request for acknowledgement is meant with "mode proposed"
realised by: #REQ-UNISIG-SUB026-0870#REF#

#REQ-UNISIG-SUB026-009509#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output information "Trackside Malfunction"
available: SB, SH, FS, LS, SR, OS, UN, TR, PT, SN, RV
This information means receiving P254 from trackside (3.16.2.4.9)

The information is indicated, if an active DMI is available.
Exception: NL
In PS, SL no DMI is active (no desk is open).
realised by: #REQ-DESIGN-CR-0395#REF#
realised by: #REQ-UNISIG-SUB026-010495#REF#

#REQ-UNISIG-SUB026-010495#REF# 4.7.2 #REQ-UNISIG-SUB026-009509#REF#
The system status message "Trackside Malfunction" shall not be displayed in mode NL.
#TEST-VAL-SUB026-4534#REF# FCT basic function NL/L2 - System Configuration Management, Default Balise Information

#REQ-UNISIG-SUB026-010422#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Notification of Train Data change from source different from the driver"
available: SB, FS, LS, SR, OS, UN, TR, PT, SN
UNISIG clarification
if the procedure is active, the information should be displayed
=> a mode dependency for the indication isn't necessary
=> indication in RV is an error in the specification

=> is 
realized with 4.5.2 and the procedure "Changing Train Data from sources different from the driver" (see 5.17)
realised by: #REQ-UNISIG-SUB026-1068:02#REF#
realised by: #REQ-UNISIG-SUB026-006702#REF#

#REQ-UNISIG-SUB026-010424#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Operated System Version"
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV

--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
#ANALYSE-VALUNISIG-5288#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010423#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Radio Network registration failed"
available: SB, FS, LS, SR, OS, NL, PT
UNISIG clarification: this information is only displayed after a driver input
=> is realized with A29 in SoM and 5.10.3.15.2 b)

#REQ-UNISIG-SUB026-010425#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Safe radio connection indication"
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV

--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
#ANALYSE-VALUNISIG-5292#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010426#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Local Time"
active: SH, FS, LS, SR, OS, NL, UN, PT, RV
available: SB, TR, SN
"available: SB, TR" means:
a desk is open and therefore an active DMI is available

a mode dependency is not necessary
--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
#ANALYSE-VALUNISIG-5289#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010427#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Gradient"
available: FS
is part of the planning area. The relevant information for the planning area are defined in 3.15.10. The mode depenendency is defined in ERA SRS
DMI (see 8.3).
realised by: #REQ-UNISIG-SUB026-007778:01#REF#

#REQ-UNISIG-SUB026-010428#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "MRSP"
available: FS
is part of the planning area. The relevant information for the planning area are defined in 3.15.10. The mode depenendency is defined in ERA SRS
DMI (see 8.3).
realised by: #REQ-UNISIG-SUB026-007778:01#REF#

#REQ-UNISIG-SUB026-010429#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Indication location at MRSP speed (see 3.13.10.4.11)"
available: FS
is part of the planning area. The relevant information for the planning area are defined in 3.15.10. The mode depenendency is defined in ERA SRS
DMI (see 8.3).
realised by: #REQ-UNISIG-SUB026-007778:01#REF#

#REQ-UNISIG-SUB026-010430#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "First target at zero speed"
available: FS
is part of the planning area. The relevant information for the planning area are defined in 3.15.10. The mode depenendency is defined in ERA SRS
DMI (see 8.3).
realised by: #REQ-UNISIG-SUB026-007778:01#REF#

#REQ-UNISIG-SUB026-010432#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Brake reason"
available: SB, SH, FS, LS, SR, OS, UN, PT, SN, RV
UNISIG clarification:
Brakes cannot applied in NL
in TR the Trip Reason is displayed => always the brakes are applied and a DMI is active, the reason is displayed
--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
#ANALYSE-VALUNISIG-5290#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010431#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Trackside not compatible"
available: SB, SH, FS, LS, SR, OS, NL, UN, TR, PT, SN, RV

--- FINALISED ---
The information is displayed, if an active DMI is available.
It is'nt necessary to define a mode dependency for this information.

remark: A special definition exists for the modes SF and IS.
#ANALYSE-VALUNISIG-5291#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010433#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Train is rejected"
available: SB
is realized with SoM procedure A40
realised by: #REQ-DESIGN-CR-0421#REF#

#REQ-UNISIG-SUB026-010434#REF# 4.7.2 #REQ-UNISIG-SUB026-0248:01#REF#
Output Information "Route unsuitability(ies)"
available: FS, LS, OS
management and display are one
=> is realized with 4.5.2 and 3.12.2.4
realised by: #REQ-UNISIG-SUB026-0553:02#REF#
realised by: #REQ-UNISIG-SUB026-1062:01#REF#

Chapter 4.8

#REQ-DESIGN-CR-0621#REF# 4.8.1.3
If a message contains level transition information, any other information in that message shall be evaluated considering the level transition
information.
realised by: #REQ-UNISIG-SUB026-3614#REF#

#REQ-DESIGN-CR-0024:01#REF# 4.8.1.3.1
Information received in the same message as an immediate level transition order or a conditional level transition order that causes a level
transition shall be evaluated first considering the on-board currently operated level, as if a level transition order for further location had
been received (i.e. conditions [1], [2] or [6] of Figure 3, if applied, shall be automatically fulfilled). Then, if relevant, it shall be
immediately extracted from the buffer and re-evaluated according to the new selected level.

#DSC-UNISIG-SUB026-005384#REF#

Figure 3: schematic representation of the filtering of received information:
TEST APPROACH:
Following filter condition have been identified 
1. Information not accepted in the current level, not accepted in the new level 
2. Information not accepted in the current level, accepted in the new level 
3. Information accepted (buffered) in the current level, not accepted in the new level 
4. Information accepted (buffered) in the current level, accepted in the new level 
5. Information accepted in the current level, not accepted in the new level 
6. Information accepted in the current level, accepted in the new level 

Filter condition 1 and 6 do nothing add to #REQ-UNISIG-SUB026-1200:01#REF# and are hence covered by verification of the refinements of
#REQ-UNISIG-SUB026-1200:01#REF#.
Filter condition 3 is not relevant as excluded by the design of the filer table #REQ-UNISIG-SUB026-1200:01#REF#.
The verification focuses on the condition 2, 4 and 5.

Note: Informatinon is not accepted in condition 2 and 5. 
#TEST-VAL-SUB026-4B25#REF# FCT (2) L0->L2, LTO evaluation of P140 received in the same message as an immediate LTO: L0->L2
#TEST-VAL-SUB026-4B24#REF# FCT (2) NTC->L2, LTO evaluation of P140 received in the same message as an immediate LTO: STM->L2
#TEST-VAL-SUB026-4B27#REF# FCT (4) L0->L2, LTO evaluation of P71 received in the same message as an immediate LTO: L0->L2
#TEST-VAL-SUB026-4115#REF# FCT (4) L0[1]->L1, LTO Reception of information valid for level origin in message ordering immediate level transition
#TEST-VAL-SUB026-4407#REF# FCT (4) L1[2]->L2, LTO switch from SR/L1 to FS/L2 - border BG includes L1 MA + MP-OS, level transition buffer includes valid MA + MP-OS
#TEST-VAL-SUB026-4858#REF# FCT (4) L2[1]->L1, LTO level transition L2->L1, L1 MA not covered
#TEST-VAL-SUB026-3430#REF# FCT (4) NTC[1]->L1, LTO Mode transition SR->SN[56]->SH[61]
#TEST-VAL-SUB026-4B26#REF# FCT (4) NTC[2]->L2, LTO evaluation of P71 received in the same message as an immediate LTO: NTC->L2
#TEST-VAL-SUB026-4B28#REF# FCT (5) L1->L0, LTO evaluation of P71 received in the same message as an immediate LTO: L1->L0
#TEST-VAL-SUB026-4861#REF# FCT (5) L1->L2, CLTO Processing of information received in the same message as an conditional level transition order (L1->L2)
#TEST-VAL-SUB026-4142#REF# FCT (5) L1->L2, LTO packet processing if contained in same msg as immediate LvlTransOrder
#TEST-VAL-SUB026-4427#REF# FCT (5) L1->L2, LTO switch from SR/L1 to OS/L2 - border BG includes L1 MA + MP-OS SSP/GP
#TEST-VAL-SUB026-4862#REF# FCT (5) L2->L0, CLTO Processing of information received in the same message as an conditional level transition order (L2->L0)
#TEST-VAL-SUB026-4860#REF# FCT (5) L2->L1, LTO Processing of information received in the same message as an immediate level transition order (L2->L1->L0)
#TEST-VAL-SUB026-4863#REF# FCT (5) L2->NTC, LTO Processing of information received in the same message as an LTO now/ CLTO (L2->NTC->L1)

#REQ-DESIGN-CR-0599#REF# 4.8.1.5
If a message contains infill information, this latter shall be evaluated considering all other non-infill information in that message.
Anmerkung: 
Mit dieser Anforderung wird auch sichergestellt, dass in der selben Message vorhandene Linking Informationen bei der Ermittlung der Location
reference berücksichtigt werden.
#TEST-VAL-SUB026-4979#REF# FCT basic function , CFX00039859 Evaluation order of packets in message containg Infill location reference pkt

#REQ-UNISIG-SUB026-3118#REF# 4.8.1.6
When evaluating trackside information received by radio or when re-evaluating a set of information released from the transition buffer, linking
information, if any, shall be evaluated prior to any other location related information.
realised by: #REQ-UNISIG-SUB026-3620:01#REF#
realised by: #REQ-UNISIG-SUB026-3615#REF#

#REQ-UNISIG-SUB026-0751:01#REF# 4.8.2.1
The following tables shall be applied assuming that:
a)	the information complies with the data consistency checks.(see section 3.16)
b)	the direction for which the information is valid matches the current train orientation, or the balise group crossing direction (for SL,
PS and SH engines).(see section 3.6.3)
c)	In levels 2/3, it is assumed that the “RBC” information which is marked “A” (Accepted) comes from the supervising RBC (see RBC/RBC
handover). If this information is received from the “Accepting” RBC while the “Handing Over” RBC is still responsible, it is stored onboard
until the RBC transition is performed
exception1: the information “Acknowledgement of Train Data”, “Trackside constituent system version”, "Initiation of Communication
Session", "Session Management" and “Acknowledgement of Session Termination" shall be immediately accepted.
exception2: the information “Co-operative shortening of MA” and “Revocation of Emergency Stop” shall be rejected.”
d)	to check exception [4] in 4.8.3, the track description is referred to the LRBG.

--- FINALISED ---
Point d is only a hint not a requirement.
realised by: #REQ-UNISIG-SUB026-3119#REF#
realised by: #REQ-UNISIG-SUB026-3120:01#REF#
realised by: #REQ-UNISIG-SUB026-3121#REF#

#REQ-UNISIG-SUB026-3119#REF# 4.8.2.1.a #REQ-UNISIG-SUB026-0751:01#REF#
The tables 4.8.3 and 4.8.4 shall be applied assuming the information complies with the data consistency checks.(see section 3.16)
realize through 3.16.1.1
realised by: #REQ-UNISIG-SUB026-0106#REF#

#REQ-UNISIG-SUB026-3120:01#REF# 4.8.2.1.b #REQ-UNISIG-SUB026-0751:01#REF#
The tables 4.8.3 and 4.8.4 shall be applied assuming the direction for which the information is valid matches the current train orientation, or
the balise group crossing direction (for SL, PS and SH engines). See section 3.6.3.
realize through 3.6.3.1.3
realised by: #REQ-UNISIG-SUB026-0441:01#REF#

#REQ-UNISIG-SUB026-3121#REF# 4.8.2.1.c #REQ-UNISIG-SUB026-3355#REF#
#REQ-UNISIG-SUB026-0751:01#REF#
The tables 4.8.3 and 4.8.4 shall be applied assuming that:
In levels 2/3, it is assumed that the “RBC” information which is marked “A” (Accepted) comes from the supervising RBC (see RBC/RBC handover). If
this information is received from the “Accepting” RBC while the “Handing Over” RBC is still responsible, it is stored onboard until the RBC
transition is performed
exception1: the information “Acknowledgement of Train Data”, “Trackside constituent system version”, "Session Management" and
“Acknowledgement of Session Termination" shall be immediately accepted.
exception2: the information “Co-operative shortening of MA” and “Revocation of Emergency Stop” shall be rejected.
UNISIG clarification:
"Initiation of Communication Session" is not considered
TEST APPROACH:
Following aspect have been identified:
1.   Supervising RBC - accepted
2.   Accepting RBC:
2.1.  Stored into the transition buffer
2.2.  Immediately accepted:
2.2.1. "Ack. of Train Data"
2.2.2. "Configuration determination"
2.2.3. "Session Management"
2.2.4. "Ack. of Session Termination"
2.3.  Rejected:
2.3.1. "Co-operative shortening of MA"
2.3.2. "Revocation of Emergency Stop"
#TEST-VAL-SUB026-4809#REF# FCT 1 Acceptance of information from supervising RBC
#TEST-VAL-SUB026-4855#REF# FCT 2.1, 2.3.2 Revocation of Emergency Stop from accepting RBC
#TEST-VAL-SUB026-4E90#REF# FCT 2.2.1, 2.2.3, 2.2.4 Handover to RBC2 canceled due to termination of communication session with RBC2
#TEST-VAL-SUB026-4829#REF# FCT 2.2.2 Acceptance of message 32 from accepting RBC
#TEST-VAL-SUB026-4856#REF# FCT 2.3.1 Request to Shorten MA from accepting RBC
#TEST-VAL-SUB026-4857#REF# EET error expectation Message from former accepting RBC

#REQ-UNISIG-SUB026-3575:01#REF# to.4.8.2.1..c #REQ-UNISIG-SUB026-3250#REF#
#ANA-UNISIG-RBCHandover-0002#REF#
#ANA-UNISIG-RBCHandover-0010:01#REF#
Following applies to information received from a not supervising RBC which is not involved in a running RBC/RBC handover:
Only information related to the termination of the communication session (i.e. Termination and Ack of Termination) shall be accepted. All other
messages shall be ignored.

Remark:This applies also for the former "Handing Over" RBC.
aus Sicht der Informationsfilterung ist ein Handover mit Wechsel der Überwachungsführung beendet.
TEST APPROACH:
The following aspects have been identified:
1) former Handing Over RBC
2) not supervising RBC not involved in handover
#TEST-VAL-SUB026-4B06#REF# FCT 1 Message from former Handing Over RBC not accepted
#TEST-VAL-SUB026-4H23#REF# FCT 2 Reception of information from a not supervising RBC which is not involved in a running RBC/RBC transition

#REQ-UNISIG-SUB026-3123#REF# to.4.8.2.1 #ANA-UNISIG-AccInformation-0003#REF#
The table 4.8.3 shall be applied assuming that:
If the Infill Location Reference stored during a level transition announce, all following Infill Information shall be stored too.
clarification to 4.8.4.1.1 (#REQ-UNISIG-SUB026-0755:01#REF#)
TEST APPROACH:
Infill information is given in the packets specified by #REQ-UNISIG-SUB040-001202:01#REF#. The verification focuses on these packets. 
Note1: P133 and P69 are omitted, as Radio Infill and TC 'Station Platforms' are not part of R8.0
The following aspects have been identified:
1 ) P5
2 ) P12
3 ) P21
4 ) P27
5 ) P39
6 ) P40
7 ) P41
8 ) P44
9 ) P49
10) P51
11) P52
12) P65
13) P66
14) P67
15) P68
16) P69 excluded see Note 1
17) P70
18) P71
19) P80
20) P88
21) P133 excluded see Note 1
22) P138
23) P139
#TEST-VAL-SUB026-4433#REF# FCT 1 infill Linking and TSR buffered in level transition buffer
#TEST-VAL-SUB026-4429#REF# FCT 2, 3, 4, 7, 18, 19 , CFX00039859 infill pkt 12, 21, 27, 80, 66, 71, 41 buffered in level transition buffer
#TEST-VAL-SUB026-4E87#REF# FCT 5 infill pkt 39 buffered in level transition buffer
#TEST-VAL-SUB026-4E88#REF# FCT 6 infill pkt 40 buffered in level transition buffer
#TEST-VAL-SUB026-8057#REF# FCT 8 In-fill P44 is used immediately
#TEST-VAL-SUB026-4431#REF# FCT 9 infill pkt80, 49 buffered in level transition buffer
#TEST-VAL-SUB026-4430#REF# FCT 10, 14, 15, 22, 23 infill pkt 51, 68, 67, 138, 139 buffered in level transition buffer
#TEST-VAL-SUB026-4E86#REF# FCT 11, 20 infill pkt 52, 88 buffered in level transition buffer
#TEST-VAL-SUB026-4434#REF# FCT 12, 13 level 1 announced pass BG with non infill TSR, TSR revocation and infill TSR, TSR revocation
#TEST-VAL-SUB026-4432#REF# FCT 17 infill Route Suitability Data buffered in level transition buffe, linking for location reference given in same BG as infill

#REQ-UNISIG-SUB026-005394#REF# 4.8.2.2
Regarding 4.8.2.1 a): In case a balise is missed or a balise telegram cannot be decoded, the information “Inhibition of balise group message
consistency reaction” is only used by the on-board equipment to inhibit the service brake reaction, while the balise group message is rejected.
If all the telegrams from a balise group are correctly read, the information “Inhibition of balise group message consistency reaction”, if
received, shall be ignored by the on-board equipment. Therefore this information need not to be referred to in the following tables.
realised by: #REQ-UNISIG-SUB026-010001#REF#
realised by: #REQ-UNISIG-SUB026-010002#REF#

#REQ-UNISIG-SUB026-010001#REF# to.4.8.2.2 #REQ-UNISIG-SUB026-005394#REF#
The information “Inhibition of balise group message consistency reaction” shall be accepted independent of level and mode.
TEST APPROACH:
The service brake is not applied in case of message consistency error in ETCS mode SL, NL, PT, RV and PS. The reception of P145 has hence no
functional relevance in these modes. The verification for these modes is omitted. 
Following aspects have been identified:
1) Level
1.1) NTC
1.2) L0
1.3) L1
1.4) L2
1.5) L3
2) Mode
2.1) FS
2.2) LS
2.3) OS
2.4) SB
2.5) SH
2.6) SN
2.7) SR
2.8) TR
2.9) UN
#TEST-VAL-SUB026-5858#REF# FCT 1.1, 2.6 Inhibition of balise group message consistency reaction (balise missing)
#TEST-VAL-SUB026-5857#REF# FCT 1.2, 2.9 Inhibition of balise group message consistency reaction (balise missing)
#TEST-VAL-SUB026-5855#REF# FCT 1.3, 2.7 Inhibition of balise group message consistency reaction (balise decoding error)
#TEST-VAL-SUB026-5859#REF# FCT 1.4, 2.1 Inhibition of balise group message consistency reaction in FS
#TEST-VAL-SUB026-5873#REF# FCT 1.5, 2.4 Inhibition of balise group message consistency reaction in L3 and SB
#TEST-VAL-SUB026-5861#REF# FCT 2.2 Inhibition of balise group message consistency reaction in LS
#TEST-VAL-SUB026-5860#REF# FCT 2.3 Inhibition of balise group message consistency reaction in OS
#TEST-VAL-SUB026-5856#REF# FCT 2.5 Inhibition of balise group message consistency reaction (balise decoding error)
#TEST-VAL-SUB026-5874#REF# FCT 2.8 Inhibition of balise group message consistency reaction in TR

#REQ-UNISIG-SUB026-010002#REF# to.4.8.2.2 #REQ-UNISIG-SUB026-005394#REF#
If all the telegrams from a balise group are correctly read, the information “Inhibition of balise group message consistency reaction”, if
received, shall be ignored by the on-board equipment.
#TEST-VAL-SUB026-5861#REF# FCT basic function Inhibition of balise group message consistency reaction in LS

#REQ-UNISIG-SUB026-010435#REF# 4.8.2.3
In case a balise telegram contains the information VBC marker and a country/region identity that both match a stored VBC, the whole balise
telegram is ignored and any further check in relation to this balise telegram is irrelevant (refer to 3.15.9.3 b)). Otherwise the information
VBC marker, if included in a consistent balise group message, shall always be ignored by the ERTMS/ETCS on-board equipment and need not to be
referred to in the following tables.

--- FINALISED ---
The first part is only a reference to 3.15.9.3.
A separate requirement for the not using is'nt necessary.
#ANALYSE-VALUNISIG-5347#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-1200:01#REF# 4.8.3.1.1- #REQ-UNISIG-SUB026-0820#REF#
#REQ-UNISIG-SUB026-0821#REF#
A = Accepted	R = Rejected








[1] exception: stored onboard if an order to switch to L1 at a further location has been received.
[2] exception: stored onboard if an order to switch to L2/3 at a further location has been received.
[3] exception: rejected if Train Data has been sent to the RBC and the “Acknowledgement of Train Data” has not been received yet.
[4] exception: rejected if the SSP and gradient already available on-board or given together with the MA do not cover the full length of the MA.
[5] exception: rejected if emergency stop(s) have been accepted and are not yet revoked or deleted onboard (see mode transitions).
[8] exception: revocable TSRs shall be rejected if information “inhibition of revocable TSRs from balises in L2/3” is stored on-board.
[9] exception: rejected if no level 2/3 transition order is stored onboard.
[10] exception: rejected if the referred LRBG is memorised to have been reported with different “previous LRBG”
[11] exception: rejected if a level transition order is received in the same message, or if a previous level transition order has announced a
level transition still to be executed
[12] exception: rejected if the text message is sent with a request for report of driver acknowledgement with the same text message identifier
as a previously received text message, which the driver has not yet acknowledged
[13] exception: rejected if not received together with an immediate level transition order to L1/2/3
TEST APPROACH:
The filter condition in this requirement and its refinements are realized centrally by the software module packet handler (PH).
The acceptance of information depending on the level and transmission media is covered by PH module verification. The condition reject
information is there by sufficiently covered. Hence the additional VER/VAL test cases outlined here after focus on the processing of accepted
information. The transmission media "From RBC no" can be Balise, Loop and or RIU. The test has to comprise all media defined for a given
information/packet as defined in 7.4 "Transmitted by". 
RIU is not part of R8 refer #REQ-SRS-004408#REF# verification is hence omitted.

Each exception is tested at leased once (equitation class) in order to verify that the condition is properly evaluated.
The appropriated verification is linked to the requirements specifying exception. 
Note: The correct evaluation of the exceptions can not be verified by its own but in correlation with information which depend on the exception
only.
realised by: #REQ-UNISIG-SUB026-010003#REF#
realised by: #REQ-UNISIG-SUB026-010004#REF#
realised by: #REQ-UNISIG-SUB026-010005#REF#
realised by: #REQ-DESIGN-CR-0343:01#REF#
realised by: #REQ-DESIGN-CR-0080#REF#
realised by: #REQ-UNISIG-SUB026-010006#REF#
realised by: #REQ-UNISIG-SUB026-010007#REF#
realised by: #REQ-UNISIG-SUB026-010008#REF#
realised by: #REQ-UNISIG-SUB026-010009#REF#
realised by: #REQ-DESIGN-CR-0738:01#REF#
realised by: #REQ-UNISIG-SUB026-010011#REF#
realised by: #REQ-DESIGN-CR-0444#REF#
realised by: #REQ-DESIGN-CR-0520#REF#
realised by: #REQ-DESIGN-CR-0521#REF#
realised by: #REQ-DESIGN-CR-0081:01#REF#
realised by: #REQ-UNISIG-SUB026-010012#REF#
realised by: #REQ-UNISIG-SUB026-010013#REF#
realised by: #REQ-DESIGN-CR-0344:01#REF#
realised by: #REQ-UNISIG-SUB026-3495#REF#
realised by: #REQ-UNISIG-SUB026-010014#REF#
realised by: #REQ-DESIGN-CR-0345#REF#
realised by: #REQ-UNISIG-SUB026-010015#REF#
realised by: #REQ-UNISIG-SUB026-010016#REF#
realised by: #REQ-DESIGN-CR-0346#REF#
realised by: #REQ-DESIGN-CR-0347#REF#
realised by: #REQ-DESIGN-CR-0348#REF#
realised by: #REQ-UNISIG-SUB026-010017#REF#
realised by: #REQ-UNISIG-SUB026-010018#REF#
realised by: #REQ-UNISIG-SUB026-010019#REF#
realised by: #REQ-DESIGN-CR-0082#REF#
realised by: #REQ-UNISIG-SUB026-010020#REF#
realised by: #REQ-DESIGN-CR-0083:01#REF#
realised by: #REQ-DESIGN-CR-0390#REF#
realised by: #REQ-DESIGN-CR-0084#REF#
realised by: #REQ-UNISIG-SUB026-010021#REF#
realised by: #REQ-UNISIG-SUB026-010022#REF#
realised by: #REQ-UNISIG-SUB026-010023#REF#
realised by: #REQ-UNISIG-SUB026-010025#REF#
realised by: #REQ-UNISIG-SUB026-010026#REF#
realised by: #REQ-UNISIG-SUB026-3481:01#REF#
realised by: #REQ-UNISIG-SUB026-010027#REF#
realised by: #REQ-UNISIG-SUB026-010028#REF#
realised by: #REQ-UNISIG-SUB026-3498#REF#
realised by: #REQ-UNISIG-SUB026-010030#REF#
realised by: #REQ-UNISIG-SUB026-010029#REF#
realised by: #REQ-UNISIG-SUB026-010031#REF#
realised by: #REQ-UNISIG-SUB026-010032#REF#
realised by: #REQ-UNISIG-SUB026-010033#REF#
realised by: #REQ-UNISIG-SUB026-010034#REF#
realised by: #REQ-UNISIG-SUB026-010035#REF#
realised by: #REQ-UNISIG-SUB026-010100#REF#
realised by: #REQ-UNISIG-SUB026-010036#REF#
realised by: #REQ-UNISIG-SUB026-010037#REF#
realised by: #REQ-UNISIG-SUB026-010038#REF#
realised by: #REQ-DESIGN-CR-0078#REF#
realised by: #REQ-DESIGN-CR-0079#REF#
realised by: #REQ-UNISIG-SUB026-010039#REF#
realised by: #REQ-DESIGN-CR-0522#REF#
realised by: #REQ-UNISIG-SUB026-010040#REF#
realised by: #REQ-UNISIG-SUB026-010041#REF#
realised by: #REQ-UNISIG-SUB026-010010#REF#
realised by: #REQ-UNISIG-SUB026-010438#REF#
realised by: #REQ-UNISIG-SUB026-1202#REF#
realised by: #REQ-UNISIG-SUB026-1203#REF#
realised by: #REQ-DESIGN-CR-0367#REF#
realised by: #REQ-DESIGN-CR-0501#REF#
realised by: #REQ-DESIGN-CR-0502#REF#
realised by: #REQ-UNISIG-SUB026-010042#REF#
realised by: #REQ-DESIGN-CR-0523#REF#
realised by: #REQ-UNISIG-SUB026-3223#REF#
realised by: #REQ-UNISIG-SUB026-010043#REF#
realised by: #REQ-UNISIG-SUB026-010044#REF#
realised by: #REQ-UNISIG-SUB026-010439#REF#

#REQ-UNISIG-SUB026-010003#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "National Values" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
#ANALYSE-VALUNISIG-4529#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4D15#REF# FCT BG/L0 Check radio link (only level 2/3); UN
#TEST-VAL-SUB026-4C83#REF# FCT BG/L1 Check radio link (only level 2/3): FS/L1, FS/L2
#TEST-VAL-SUB026-5697#REF# FCT BG/L2 Acceptance of NV from BG in L2
#TEST-VAL-SUB026-5710#REF# FCT BG/L3 Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4D53#REF# FCT BG/NTC Check radio link (only level 2/3): SN/STM
#TEST-VAL-SUB026-5696#REF# FCT RBC/L0[2], RBC/L1[2] Acceptance of NV from RBC in L0/L1
#TEST-VAL-SUB026-4D13#REF# FCT RBC/L2 Check radio link (only level 2/3); TR, PT
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4447#REF# FCT RBC/NTC acceptance NV, RV info in SN from RBC without LTO
#TEST-VAL-SUB026-4446#REF# FCT RBC/NTC[2] acceptance NV, RV info in SN from RBC with LTO

#REQ-UNISIG-SUB026-010004#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Linking" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4530#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4C41#REF# FCT BG/L0 Stored data: Linking information when mode changes to UN/L0, FS/L1
#TEST-VAL-SUB026-4219#REF# FCT BG/L0[1] L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4718#REF# FCT BG/L1 Table 4.5.2 --> Checking linking consistency (FS, OS)
#TEST-VAL-SUB026-4421#REF# FCT BG/L2 accepted information from BG in L2 (pkt P12, 21, 27, 70, 51, 5, 138, 139, 72)
#TEST-VAL-SUB026-4420#REF# FCT BG/L2[1] LTO L1 announced - accepted information from BG in L2 (12, 21, 27, 138, 139, 68, 70, 80, 65, 5)
#TEST-VAL-SUB026-4B37#REF# FCT BG/L3[1] Acceptance of Linking from BG in L3
#TEST-VAL-SUB026-4473#REF# FCT BG/NTC, RBC/NTC SN/STM acceptance pkt5 from RBC/BG - no LTO on board
#TEST-VAL-SUB026-4472#REF# FCT BG/NTC[1] SN/STM acceptance pkt5 from BG - LTO L1 onboard
#TEST-VAL-SUB026-5707#REF# FCT LOOP/L1 in-fill information from LOOP: level transition announcement, linking information
#TEST-VAL-SUB026-4B16#REF# FCT RBC/L0[2] Packet 5 Linking accepted from RBC (in L0) if LTO to L2 at further location received
#TEST-VAL-SUB026-5698#REF# FCT RBC/L1[2], RBC/L2[3] Accepteance of linking information from RBC
#TEST-VAL-SUB026-4C39#REF# FCT RBC/L2 Stored data: Linking information when mode changes to FS/L2, OS/L2
#TEST-VAL-SUB026-4B38#REF# FCT RBC/L3 Acceptance of Linking from RBC in L3
#TEST-VAL-SUB026-4471#REF# FCT RBC/NTC[2] SN/STM acceptance pkt5 from RBC - LTO L2 onboard

#REQ-UNISIG-SUB026-010005#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
#ANA-UNISIG-AccInformation-0005#REF#
acceptance "Signalling Related Spee Restriction" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
not relevant
V_MAIN in P12 is meant

This information is accepted/rejected together with the relevant MA. A separat check is not necessary.

see analysis also
realised by: #REQ-DESIGN-CR-0343:01#REF#

#REQ-DESIGN-CR-0343:01#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
#REQ-DESIGN-CR-0168#REF#
#REQ-UNISIG-SUB026-010005#REF#
acceptance "Movement Authority + (optional) Mode Profile + (optional) List of Balises for SH area" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3][5]
L3: A[3][5]
exception [4] is realized through 3.7.2.3
TEST APPROACH:
MA with shifted location reference (M33) is handled with the same filter criteria for accepted information as the information Paket 15 "Level 2
Movement Authority" (ref. #REQ-UNISIG-SUB026-3336#), therefore a distinction between these 2 information is not necessary. 
Mode profile is accepted together with a MA only. List of balises for SH area is accepted with MP-SH and MA only, so a separate verification for
these information is not necessary.
#ANALYSE-VALUNISIG-4532#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5701#REF# FCT BG/L0[1] Acceptance of MA from BG in L0
#TEST-VAL-SUB026-5702#REF# FCT BG/L1 Acceptance of MA from BG in L1
#TEST-VAL-SUB026-4220#REF# FCT BG/L2[1] L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-5710#REF# FCT BG/L3[1] Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-5704#REF# FCT BG/NTC[1] Acceptance of MA/SSP/GP from BG in NTC
#TEST-VAL-SUB026-5706#REF# FCT LOOP/L1 in-fill information from LOOP MA/MP, P49, AP, ASP
#TEST-VAL-SUB026-5699#REF# FCT RBC/L0[2] Acceptance of movement authority from RBC in L0
#TEST-VAL-SUB026-5700#REF# FCT RBC/L1[2] Acceptance of MA from RBC in L1
#TEST-VAL-SUB026-4B50#REF# FCT RBC/L2 LS/L2 - acceptance of MA, MP, List of Balises for SH Area, GP, SSP, ASP
#TEST-VAL-SUB026-4865#REF# FCT RBC/L2, RBC/L2[3],[5] MA+MP rejected due to outstanding M8 and not yet revoked ES
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3[3] Acceptance of MA data from RBC in L3
#TEST-VAL-SUB026-4760#REF# FCT RBC/NTC[2] Acception of L2-MA, SSP, GP via radio while Level is STM (an transition order to level 2 is given)
#TEST-VAL-SUB026-4772#REF# EET error expectation Acception of 'list of balises for SH area' via radio while Level is STM (no L2 transition order is given)
#TEST-VAL-SUB026-4775#REF# EET error expectation Reception of MA before Acknowledgment of Train Data level transition L2 announced
#TEST-VAL-SUB026-4869#REF# EET error expectation train data change in L2 announcement area has no effect on buffered MA and MP
#TEST-VAL-SUB026-4870#REF# EET error expectation Buffered MA not accepted if train data change not acknowledged by RBC (L0->L2)
#TEST-VAL-SUB026-4871#REF# EET error expectation Buffered MA and MP not accepted if train data change not acknowledged by RBC (L1->L2)

#REQ-UNISIG-SUB040-3004#REF# table.4.8.3.1
If the on-board receives a mode profile (packet 80) without a movement authority (packet 12, 15), obu shall assess it as a data inconsistency.
UNISIG clarification:
an error reaction must be defined
#TEST-VAL-SUB040-0033#REF# FCT P12 A Mode Profile received without a MA shall be considered as a data inconsistency.
#TEST-VAL-SUB026-5926#REF# FCT P15 Mode Profile received without a MA evaluated as message inconsistency

#REQ-DESIGN-CR-0080#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Repositioning Information" depending on level:
not from RBC:
L0: R
LNTC: R
L1: A
L2: R
L3: R

from RBC:
not relevant
#ANALYSE-VALUNISIG-4533#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3764#REF# FCT BG/L1 information from second repositioning BG not taken into account
#TEST-VAL-SUB026-3765#REF# FCT BG/L2 repositioning information not accepted in L2

#REQ-UNISIG-SUB026-010006#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Gradient Profile" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4534#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4219#REF# FCT BG/L0[1] L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-5702#REF# FCT BG/L1 Acceptance of MA from BG in L1
#TEST-VAL-SUB026-4421#REF# FCT BG/L2 accepted information from BG in L2 (pkt P12, 21, 27, 70, 51, 5, 138, 139, 72)
#TEST-VAL-SUB026-4220#REF# FCT BG/L2[1] L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-5710#REF# FCT BG/L3[1] Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4767#REF# FCT BG/NTC Acception of GP via balises while Level is STM (no L1 transition is given)
#TEST-VAL-SUB026-5704#REF# FCT BG/NTC[1] Acceptance of MA/SSP/GP from BG in NTC
#TEST-VAL-SUB026-3606#REF# FCT LOOP/L1 non in-fill information from LOOP neglected
#TEST-VAL-SUB026-5699#REF# FCT RBC/L0[2] Acceptance of movement authority from RBC in L0
#TEST-VAL-SUB026-5700#REF# FCT RBC/L1[2] Acceptance of MA from RBC in L1
#TEST-VAL-SUB026-4318#REF# FCT RBC/L2 PT/L2 acceptence (Q_DIR evaluation) of MA, SSP, GP
#TEST-VAL-SUB026-4865#REF# FCT RBC/L2[3] MA+MP rejected due to outstanding M8 and not yet revoked ES
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3
#TEST-VAL-SUB026-4770#REF# FCT RBC/NTC Acception of GP via radio while Level is STM (no L2 transition order is given)
#TEST-VAL-SUB026-4760#REF# FCT RBC/NTC[2] Acception of L2-MA, SSP, GP via radio while Level is STM (an transition order to level 2 is given)

#REQ-UNISIG-SUB026-010007#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "International SPP" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4535#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4219#REF# FCT BG/L0[1] L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-5702#REF# FCT BG/L1 Acceptance of MA from BG in L1
#TEST-VAL-SUB026-4421#REF# FCT BG/L2 accepted information from BG in L2 (pkt P12, 21, 27, 70, 51, 5, 138, 139, 72)
#TEST-VAL-SUB026-4220#REF# FCT BG/L2[1] L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-5710#REF# FCT BG/L3[1] Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4766#REF# FCT BG/NTC Acception of SSP via balises while Level is STM (no L1 transition is given)
#TEST-VAL-SUB026-5704#REF# FCT BG/NTC[1] Acceptance of MA/SSP/GP from BG in NTC
#TEST-VAL-SUB026-3606#REF# FCT LOOP/L1 non in-fill information from LOOP neglected
#TEST-VAL-SUB026-5699#REF# FCT RBC/L0[2] Acceptance of movement authority from RBC in L0
#TEST-VAL-SUB026-5700#REF# FCT RBC/L1[2] Acceptance of MA from RBC in L1
#TEST-VAL-SUB026-4318#REF# FCT RBC/L2 PT/L2 acceptence (Q_DIR evaluation) of MA, SSP, GP
#TEST-VAL-SUB026-4865#REF# FCT RBC/L2[3] MA+MP rejected due to outstanding M8 and not yet revoked ES
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3
#TEST-VAL-SUB026-4769#REF# FCT RBC/NTC Acception of SSP via radio while Level is STM (no L2 transition order is given)
#TEST-VAL-SUB026-4760#REF# FCT RBC/NTC[2] Acception of L2-MA, SSP, GP via radio while Level is STM (an transition order to level 2 is given)

#REQ-UNISIG-SUB026-010008#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Axle Load speed profile" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4536#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4272#REF# FCT BG/L0[1] Pkt 5, 51, 71 accepted and buffered in UN
#TEST-VAL-SUB026-4679#REF# FCT BG/L1 MA(L1 V_MAIN)/SSP/GP ASP when entering LS
#TEST-VAL-SUB026-4421#REF# FCT BG/L2 accepted information from BG in L2 (pkt P12, 21, 27, 70, 51, 5, 138, 139, 72)
#TEST-VAL-SUB026-4858#REF# FCT BG/L2[1] level transition L2->L1, L1 MA not covered
#TEST-VAL-SUB026-5710#REF# FCT BG/L3[1] Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4F06#REF# FCT BG/NTC Acceptance of ASP in SN/STM
#TEST-VAL-SUB026-4F05#REF# FCT BG/NTC[1] Determine MRSP based on ASP : SN/STM, FS/L1
#TEST-VAL-SUB026-5706#REF# FCT LOOP/L1 in-fill information from LOOP MA/MP, P49, AP, ASP
#TEST-VAL-SUB026-5699#REF# FCT RBC/L0[2] Acceptance of movement authority from RBC in L0
#TEST-VAL-SUB026-5229#REF# FCT RBC/L1[2] target supervision
#TEST-VAL-SUB026-3116#REF# FCT RBC/L2 Effect of Q_FRONT (P27, P51, P65)
#TEST-VAL-SUB026-5721#REF# FCT RBC/L2[3], RBC/L3[3] Information from RBC discarded if filter condition [3] not fulfilled
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3
#TEST-VAL-SUB026-4F08#REF# FCT RBC/NTC Acceptance of ASP in SN/STM
#TEST-VAL-SUB026-4F04#REF# FCT RBC/NTC[2] Determine MRSP based on ASP : SN/STM, FS/L2

#REQ-UNISIG-SUB026-010009#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Level Transition Order" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
#ANALYSE-VALUNISIG-4537#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4219#REF# FCT BG/L0 L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4220#REF# FCT BG/L1, BG/L2 L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-5710#REF# FCT BG/L3 Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4446#REF# FCT BG/NTC acceptance NV, RV info in SN from RBC with LTO
#TEST-VAL-SUB026-5707#REF# FCT LOOP/L1 in-fill information from LOOP: level transition announcement, linking information
#TEST-VAL-SUB026-3330#REF# FCT RBC/L0 MA in level transition buffer, Section timeout before level transition takes place
#TEST-VAL-SUB026-3198#REF# FCT RBC/L1 NVCONTACT supervision, M_NVCONTACT=1 - Apply service brake
#TEST-VAL-SUB026-3586#REF# FCT RBC/L2 OBU establishes communication session due to manual level change L1->L2
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4457#REF# FCT RBC/NTC SN/STM acceptance pkt79 GeoPos - no LTO onboard

#REQ-DESIGN-CR-0738:01#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Conditional Level Transition Order" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
not relevant
exception[11] is realized separate  - see realization of this exception

Testhint:
Packet 46 is'nt in the list of optional packets for RBC messages. Therefore is a separate check not necessary.
#ANALYSE-VALUNISIG-4538#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4216#REF# FCT BG/L0, BG/L1 Accepting Conditional Level Transition Order depending on mode SH, NL, SL, SB, SR, SN
#TEST-VAL-SUB026-3765#REF# FCT BG/L2 repositioning information not accepted in L2
#TEST-VAL-SUB026-5711#REF# FCT BG/L3 Acceptance of P42, P45, P46, P70, P65, P137, P141 from BG in L3
#TEST-VAL-SUB026-4455#REF# FCT BG/NTC SN/STM - acception of Conditional Level Transition Order from BG
#TEST-VAL-SUB026-4215#REF# EET error expectation Accepting Conditional Level Transition Order from RBC

#REQ-UNISIG-SUB026-010011#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Session Management" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
#ANALYSE-VALUNISIG-4540#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3330#REF# FCT BG/L0 MA in level transition buffer, Section timeout before level transition takes place
#TEST-VAL-SUB026-4529#REF# FCT BG/L1 initiation/termination of communication session in SR
#TEST-VAL-SUB026-3659#REF# FCT BG/L2 OBU ignores phone number indicated in pkt42 with NID_RBC=Contact last known RBC
#TEST-VAL-SUB026-5711#REF# FCT BG/L3 Acceptance of P42, P45, P46, P70, P65, P137, P141 from BG in L3
#TEST-VAL-SUB026-4446#REF# FCT BG/NTC acceptance NV, RV info in SN from RBC with LTO
#TEST-VAL-SUB026-5712#REF# FCT RBC/L0 Session termination in L0
#TEST-VAL-SUB026-3850#REF# FCT RBC/L1 Reception of new Radio Network registration during setup of safe connection
#TEST-VAL-SUB026-3019#REF# FCT RBC/L2 Initiation of a communication session by RBC
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4D56#REF# FCT RBC/NTC Acceptance of Radio Network registration: SN/STM

#REQ-DESIGN-CR-0444#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Radio Network registration" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
#ANALYSE-VALUNISIG-4541#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4967#REF# FCT BG/L0 Check table 4.8.4 Information->Radio Network Registration, UN/L0
#TEST-VAL-SUB026-4966#REF# FCT BG/L1 Acceptance of RadioNetwork Registeration in L1 of SH, SL modes
#TEST-VAL-SUB026-4961#REF# FCT BG/L2 Check table sub26_4.8.4 Information->Radio Network Registration(Balise), Mode->FS, Level->2
#TEST-VAL-SUB026-5711#REF# FCT BG/L3 Acceptance of P42, P45, P46, P70, P65, P137, P141 from BG in L3
#TEST-VAL-SUB026-4F09#REF# FCT BG/NTC Acceptance of Radio Network registration: SN/STM
#TEST-VAL-SUB026-4B18#REF# FCT RBC/L0 Acceptance of Radio Network registration sent via RBC in L0
#TEST-VAL-SUB026-4B19#REF# FCT RBC/L1 Acceptance of Radio Network registration sent via RBC in L1
#TEST-VAL-SUB026-3989#REF# FCT RBC/L2 RadioNetworkId in RBC-RBC handover (2 mobiles)
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4D56#REF# FCT RBC/NTC Acceptance of Radio Network registration: SN/STM

#REQ-DESIGN-CR-0520#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "MA Request Parameters" depending on level:
not from RBC:
not relevant

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
#ANALYSE-VALUNISIG-4542#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4895#REF# FCT RBC/L0 Table 4.8.3 - MA request parameter (pkt 57) acceptance in L0
#TEST-VAL-SUB026-4894#REF# FCT RBC/L1 Table 4.8.3 - MA request parameter (pkt 57) acceptance in L1
#TEST-VAL-SUB026-4520#REF# FCT RBC/L2 Movement Authority Request Parameters in SB
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4893#REF# FCT RBC/NTC Table 4.8.3 - MA request parameter (pkt 57) acceptance in STM

#REQ-DESIGN-CR-0521#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Position Report parameters" depending on level:
not from RBC:
not relevant

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
#ANALYSE-VALUNISIG-4543#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4897#REF# FCT RBC/L0 Check table 4.8.3/4.5.2 -> Position report parameters (UN/L0, SN/STM)
#TEST-VAL-SUB026-4896#REF# FCT RBC/L1 Check table 4.8.3/4.5.2 -> Position report parameters (SR/TR/PT/L1, RV/L1)
#TEST-VAL-SUB026-4A07#REF# FCT RBC/L2 Report train position as requested by RBC at Mode SB ,FS ,TR and PT
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4275#REF# FCT RBC/NTC PR parameter - transition SN->FS

#REQ-DESIGN-CR-0081:01#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "SR Authorisation + (optional) List of Balises in SR mode" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A[3]
L3: A[3]
List of Balises in SR mode cannot be send alone, because the list can be only send via RBC and P63 can only used with message SR authorisation
(see 8.4.4.4.1)
#ANALYSE-VALUNISIG-4544#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5492#REF# FCT RBC/L2 D_SR supervision when D_SR updated during active override
#TEST-VAL-SUB026-5713#REF# FCT RBC/L3, RBC/L3[3] Acceptance of SR Authorisation + List of Balises in SR mode in L3
#TEST-VAL-SUB026-5927#REF# EET error expectation Acceptance of P63

#REQ-UNISIG-SUB026-010012#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Stop if in SR mode" depending on level:
not from RBC:
L0: R
LNTC: R
L1: A
L2: A
L3: A

from RBC:
not relevant
#ANALYSE-VALUNISIG-4545#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4223#REF# FCT BG/L1 BMM handling in SR/TR/PT in L1
#TEST-VAL-SUB026-4668#REF# FCT BG/L2 Driver Id and driver Adhesion factor TR/PT
#TEST-VAL-SUB026-5711#REF# FCT BG/L3 Acceptance of P42, P45, P46, P70, P65, P137, P141 from BG in L3

#REQ-UNISIG-SUB026-010013#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "SR distance information from loop" depending on level:
not from RBC:
L0: R
LNTC: R
L1: A
L2: R
L3: R

from RBC:
not relevant
#ANALYSE-VALUNISIG-4546#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7672#REF# FCT L1 Non in-fill pkt 13 from LOOP

#REQ-DESIGN-CR-0344:01#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Temporary Speed Restriction" depending on level:
not from RBC:
L0: A
LNTC: R[1][2]
L1: A
L2: A[8]
L3: A[8]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4547#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3539#REF# FCT BG/L1 Supervision TSR from L1(Balise)/orientation A
#TEST-VAL-SUB026-3786#REF# FCT BG/L2 Storage of TSR for backward movement Q_FRONT=0
#TEST-VAL-SUB026-5818#REF# FCT BG/L2[8] Inhibition of revocable TSRs from balises in L2/3 deleted due to session termination
#TEST-VAL-SUB026-5711#REF# FCT BG/L3 Acceptance of P42, P45, P46, P70, P65, P137, P141 from BG in L3
#TEST-VAL-SUB026-4463#REF# FCT BG/NTC, BG/L0 SN/STM acceptance pkt65/141 - no LTO onboard
#TEST-VAL-SUB026-4464#REF# FCT BG/NTC[1], RBC/NTC SN/STM acceptance pkt65/141 - LTO L1 onboard
#TEST-VAL-SUB026-4465#REF# FCT BG/NTC[2], RBC/NTC[2] SN/STM acceptance pkt65/141 - LTO L2 onboard
#TEST-VAL-SUB026-3607#REF# FCT LOOP/L1 non in-fill information from LOOP apart from pkt 254 neglected
#TEST-VAL-SUB026-4B20#REF# FCT RBC/L0[2] Acceptance of "Temporary Speed Restriction" from RBC (in L0) if LTO to L2 at further location received
#TEST-VAL-SUB026-3728#REF# FCT RBC/L1[2] L1->L2 Level transition buffer information not deleted due change of train length
#TEST-VAL-SUB026-3143#REF# FCT RBC/L2 Two TSRs on board second defines MRDT - MRDT indicated on DMI
#TEST-VAL-SUB026-5721#REF# FCT RBC/L2[3], RBC/L3[3] Information from RBC discarded if filter condition [3] not fulfilled
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3

#REQ-UNISIG-SUB026-3495#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Temporary Speed Restriction Revocation" depending on level:
not from RBC:
L0: A
LNTC: R[1][2]
L1: A
L2: A
L3: A

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4548#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4D31#REF# FCT BG/L0 Delete Revoked TSR: UN
#TEST-VAL-SUB026-8050#REF# FCT BG/L1 TSR and Infill location reference
#TEST-VAL-SUB026-4434#REF# FCT BG/L2 level 1 announced pass BG with non infill TSR, TSR revocation and infill TSR, TSR revocation
#TEST-VAL-SUB026-5710#REF# FCT BG/L3 Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4467#REF# FCT BG/NTC[1], RBC/NTC SN/STM acceptance pkt66 - LTO L1 onboard
#TEST-VAL-SUB026-4466#REF# FCT BG/NTC[2], RBC/NTC[2] SN/STM acceptance pkt66 - LTO L2 onboard
#TEST-VAL-SUB026-3607#REF# FCT LOOP/L1 non in-fill information from LOOP apart from pkt 254 neglected
#TEST-VAL-SUB026-4268#REF# FCT RBC/L0[2] transition UN -> FS(L2)[25] (2 MAs TSR and TSR revocation in transition buffer)
#TEST-VAL-SUB026-4B21#REF# FCT RBC/L1[2] Acceptance of TSR Revocation sent via RBC in L1 if LTO to L2 received
#TEST-VAL-SUB026-3804#REF# FCT RBC/L2 Deletion of stored (fixed distance to keep information on-board) TSR/ASP
#TEST-VAL-SUB026-8109#REF# FCT RBC/L2[3] TSR revocation from RBC in L2 only accepted if there is no response pending to validated train data
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3

#REQ-UNISIG-SUB026-010014#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Inhibtion of revocable TSRs from balises in L2/3" depending on level:
not from RBC:
not relevant

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
#ANALYSE-VALUNISIG-4549#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-8110#REF# FCT RBC/L0 P64, P70 in L0 (no LTO ->L2 onboard)
#TEST-VAL-SUB026-5831#REF# FCT RBC/L0[2] Inhibition of revocable TSRs from balises in L2/3 in L0
#TEST-VAL-SUB026-5817#REF# FCT RBC/L1[2] TSR acceptence after receiving Inhibition of revocable TSRs from balises in L2/3
#TEST-VAL-SUB026-5818#REF# FCT RBC/L2 Inhibition of revocable TSRs from balises in L2/3 deleted due to session termination
#TEST-VAL-SUB026-5833#REF# FCT RBC/L3 Inhibition of revocable TSRs from balises in L2/3 in L3
#TEST-VAL-SUB026-5832#REF# FCT RBC/NTC[2] Inhibition of revocable TSRs from balises in L2/3 in NTC

#REQ-DESIGN-CR-0345#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Default Gradient for TSR" depending on level:
not from RBC:
L0: A
LNTC: R[1][2]
L1: A
L2: A
L3: A

from RBC:
not relevant
#ANALYSE-VALUNISIG-4550#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3749#REF# FCT BG/L0, BG/L1 default gradient for TSR handling UN/LS/L0/L1
#TEST-VAL-SUB026-3748#REF# FCT BG/L2 default gradient for TSR handling SR/FS/L2
#TEST-VAL-SUB026-5711#REF# FCT BG/L3 Acceptance of P42, P45, P46, P70, P65, P137, P141 from BG in L3
#TEST-VAL-SUB026-4463#REF# FCT BG/NTC SN/STM acceptance pkt65/141 - no LTO onboard
#TEST-VAL-SUB026-4464#REF# FCT BG/NTC[1] SN/STM acceptance pkt65/141 - LTO L1 onboard
#TEST-VAL-SUB026-4465#REF# FCT BG/NTC[2] SN/STM acceptance pkt65/141 - LTO L2 onboard

#REQ-UNISIG-SUB026-010015#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Route Suitability Data" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4551#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5969#REF# FCT BG/L0[1] RUS information when entering FS/OS
#TEST-VAL-SUB026-5965#REF# FCT BG/L1 OS - Route Suitability Data processing
#TEST-VAL-SUB026-4421#REF# FCT BG/L2 accepted information from BG in L2 (pkt P12, 21, 27, 70, 51, 5, 138, 139, 72)
#TEST-VAL-SUB026-5966#REF# FCT BG/L2[1] LS - Route Suitability Data processing
#TEST-VAL-SUB026-5711#REF# FCT BG/L3[1] Acceptance of P42, P45, P46, P70, P65, P137, P141 from BG in L3
#TEST-VAL-SUB026-5970#REF# FCT BG/NTC[1] RUS information when entering LS
#TEST-VAL-SUB026-8110#REF# FCT RBC/L0 P64, P70 in L0 (no LTO ->L2 onboard)
#TEST-VAL-SUB026-4B22#REF# FCT RBC/L0[2] Pkt 70(Route Suitability Data) accepted and buffered in UN/L0
#TEST-VAL-SUB026-4B23#REF# FCT RBC/L1[2] Pkt 70(Route Suitability Data) accepted and buffered in L1
#TEST-VAL-SUB026-5964#REF# FCT RBC/L2 FS, SR - Route Suitability Data processing
#TEST-VAL-SUB026-5721#REF# FCT RBC/L2[3], RBC/L3[3] Information from RBC discarded if filter condition [3] not fulfilled
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-5971#REF# FCT RBC/NTC[2] RUS information when entering SH
#TEST-VAL-SUB026-4B35#REF# FCT loop/L1 Acceptance of 'Track Conditions' (P68, P39) and 'Route Suitability Data' (P70) via in-fill by loop in L1

#REQ-UNISIG-SUB026-010016#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Adhesion Factor" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R
L3: R

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
#ANALYSE-VALUNISIG-4552#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4666#REF# FCT BG/L0[1] adhesion factor when entering NL
#TEST-VAL-SUB026-3219#REF# FCT BG/L1 Adhaesionsprofil
#TEST-VAL-SUB026-4D50#REF# FCT BG/NTC, BG/NTC[1] Acceptance of Adhesion Factor data depending on mode: SN/STM (from BG)
#TEST-VAL-SUB026-5706#REF# FCT LOOP/L1 in-fill information from LOOP MA/MP, P49, AP, ASP
#TEST-VAL-SUB026-4B17#REF# FCT RBC/L0[2] Pkt 71(Adhesion Factor) accepted and buffered in UN/L0
#TEST-VAL-SUB026-4424#REF# FCT RBC/L1[2] switch from SR/L1 to FS/L2 - border BG includes L1 MA MP-OS, level transition buffer includes several valid MA with MP
#TEST-VAL-SUB026-4664#REF# FCT RBC/L2 adhesion factor when entering FS, OS
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3
#TEST-VAL-SUB026-4D51#REF# FCT RBC/NTC, RBC/NTC[2] Acceptance of Adhesion Factor data depending on mode: SN/STM (from RBC)

#REQ-DESIGN-CR-0346#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Plain Text Information" depending on level:
not from RBC:
L0: A
LNTC: R[1][2]
L1: A
L2: A
L3: A

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
exception [12] is realized through 3.12.3.5.3
#ANALYSE-VALUNISIG-4553#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4B29#REF# FCT BG/L0, RBC/L0[2] Acceptance of Plain and Fixed Text Messages (P72, P76) based on level and transmission media
#TEST-VAL-SUB026-3002#REF# FCT BG/L1 Direction identification based on single balise group and multiple balise group
#TEST-VAL-SUB026-4543#REF# FCT BG/L2, RBC/L2 acceptance of text message LS/L2
#TEST-VAL-SUB026-5710#REF# FCT BG/L3 Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4437#REF# FCT BG/NTC, BG/NTC[1] text messages from BG in SN/STM
#TEST-VAL-SUB026-4438#REF# FCT BG/NTC[2] SN/STM - level transition to L2 - reception of text message from BG
#TEST-VAL-SUB026-4806#REF# FCT RBC/L1 Acceptance P72 from RBC in FS/L1
#TEST-VAL-SUB026-4805#REF# FCT RBC/L1[2] Acceptance P72/P76 from RBC in FS/L1->L2 (4.8.3[2])
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3
#TEST-VAL-SUB026-4439#REF# FCT RBC/NTC, RBC/NTC[2] SN/STM - level transition to L2 - reception of text message from RBC

#REQ-DESIGN-CR-0347#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Fixed Text Information" depending on level:
not from RBC:
L0: A
LNTC: R[1][2]
L1: A
L2: A
L3: A

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
exception [12] is realized through 3.12.3.5.3
#ANALYSE-VALUNISIG-4554#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4B29#REF# FCT BG/L0, RBC/L0[2] Acceptance of Plain and Fixed Text Messages (P72, P76) based on level and transmission media
#TEST-VAL-SUB026-7536#REF# FCT BG/L1 Variablentest Q_TEXT
#TEST-VAL-SUB026-4543#REF# FCT BG/L2, RBC/L2 acceptance of text message LS/L2
#TEST-VAL-SUB026-5710#REF# FCT BG/L3 Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4437#REF# FCT BG/NTC, BG/NTC[1] text messages from BG in SN/STM
#TEST-VAL-SUB026-4438#REF# FCT BG/NTC[2] SN/STM - level transition to L2 - reception of text message from BG
#TEST-VAL-SUB026-4805#REF# FCT RBC/L1[2] Acceptance P72/P76 from RBC in FS/L1->L2 (4.8.3[2])
#TEST-VAL-SUB026-5708#REF# FCT RBC/L3 Acceptance of MA data from RBC in L3
#TEST-VAL-SUB026-4439#REF# FCT RBC/NTC, RBC/NTC[2] SN/STM - level transition to L2 - reception of text message from RBC

#REQ-DESIGN-CR-0348#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Geographical Position" depending on level:
not from RBC:
L0: A
LNTC: R[1][2]
L1: A
L2: A
L3: A

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
#ANALYSE-VALUNISIG-4555#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3652#REF# FCT BG/L0, RBC/L0[2] Once a track kilometre reference is no longer applicable, it is deleted (No more geographical position calculation) + lnk
#TEST-VAL-SUB026-3653#REF# FCT BG/L1, RBC/L1[2] Once a track kilometre reference is no longer applicable, it is deleted (new track kilometer ref.)
#TEST-VAL-SUB026-4546#REF# FCT BG/L2, RBC/L2 GeoPos in LS/L2; L2 FS->LS[72]
#TEST-VAL-SUB026-4457#REF# FCT BG/NTC, RBC/NTC SN/STM acceptance pkt79 GeoPos - no LTO onboard
#TEST-VAL-SUB026-4460#REF# FCT BG/NTC[1] SN/STM acceptance pkt79 GeoPos - LTO L1 on board
#TEST-VAL-SUB026-4458#REF# FCT BG/NTC[2] SN/STM acceptance pkt79 GeoPos from BG - LTO L2 on board
#TEST-VAL-SUB026-4B39#REF# FCT RBC/L3, BG/L3 Acceptance of 'Geographical Position' in L3
#TEST-VAL-SUB026-4459#REF# FCT RBC/NTC[2] SN/STM acceptance pkt79 GeoPos from RBC - LTO L2 on board

#REQ-UNISIG-SUB026-010017#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "RBC Transition Order" depending on level:
not from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A

from RBC:
L0: R
LNTC: R
L1: R
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4556#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-8241#REF# FCT BG/L2 Mode transition to PT in front of RBC transition border
#TEST-VAL-SUB026-4B45#REF# FCT BG/L3, RBC/L3, RBC/L3[3] FS/L3 acceptance RBC transition order
#TEST-VAL-SUB026-4A74#REF# FCT RBC/L2 Manage RBC Handover; OS
#TEST-VAL-SUB026-4A97#REF# FCT RBC/NTC Acceptance of RBC Transition Order; SN/STM

#REQ-UNISIG-SUB026-010018#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
#REQ-UNISIG-SUB026-010439#REF#
acceptance "Danger for SH information" depending on level:
not from RBC:
L0: A[13]
LNTC: A[13]
L1: A
L2: A
L3: A

from RBC:
not relevant

[13] exception: rejected if not received together with an immediate level transition order to L1/2/3
Rel. 8.0:
exception[13] is new with subset 26, version 3.3.0
#ANALYSE-VALUNISIG-4557#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7952#REF# FCT BG/L0, BG/L0[13] Acceptance of Danger for shunting information: BG/L0
#TEST-VAL-SUB026-4C59#REF# FCT BG/L1 Stored data: List of balises for SH area when mode changes to TR/L1, PT/L1
#TEST-VAL-SUB026-4899#REF# FCT BG/L2 Transition table 4.6.3 - Condition 49
#TEST-VAL-SUB026-5714#REF# FCT BG/L3 Acceptance of Danger for Shunting in L3
#TEST-VAL-SUB026-8111#REF# FCT BG/NTC, BG/NTC[13] Acceptance of Danger for Shunting: level NTC

#REQ-UNISIG-SUB026-010019#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Stop Shunting on desk opening" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
not relevant
The information is generally ignored
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-DESIGN-CR-0082#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Radio Infill Area Information" depending on level:
not from RBC:
L0: R
LNTC: R
L1: A
L2: R[1]
L3: R[1]

from RBC:
not relevant
radio infill isn't realized

#REQ-UNISIG-SUB026-010020#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Session managament with neighbouring RIU" depending on level:
not from RBC:
L0: R
LNTC: R
L1: A
L2: R
L3: R

from RBC:
not relevant

#REQ-DESIGN-CR-0083:01#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "EOLM Information" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
not relevant
#ANALYSE-VALUNISIG-4561#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5705#REF# FCT BG/L0 UN/L0 acceptance EOL information - LTO L1 onboard
#TEST-VAL-SUB026-4470#REF# FCT BG/L1 L1 SR->FS EOL information
#TEST-VAL-SUB026-4698#REF# FCT BG/L2 L2 acceptance of EOL information
#TEST-VAL-SUB026-4B40#REF# FCT BG/L3 FS/L3 acceptance of EOLM and infill location reference LTO-L1 onboard
#TEST-VAL-SUB026-4469#REF# FCT BG/NTC SN/STM acceptance EOL information - LTO L1 onboard

#REQ-DESIGN-CR-0390#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
#ANA-UNISIG-CR0729-0001#REF#
acceptance "Assignment of Co-ordinate system" depending on level:
not from RBC:
not relevant

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
exception [10] is realized through 3.4.2.3.3.8
#ANALYSE-VALUNISIG-4562#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4499#REF# FCT RBC/L0 UN/L0 - acceptance of message 45: Assignment of coordinate system
#TEST-VAL-SUB026-4497#REF# FCT RBC/L1 SR/L1 - acceptance of message 45: Assignment of coordinate system
#TEST-VAL-SUB026-3336#REF# FCT RBC/L2 Assignement of coordinate system via message 45
#TEST-VAL-SUB026-4B41#REF# FCT RBC/L3 SR/L3 - acceptance of 'Assignment of coordinate system'
#TEST-VAL-SUB026-4511#REF# FCT RBC/NTC SN/STM - acceptance of message 45: Assignment of coordinate system

#REQ-DESIGN-CR-0084#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Infill Location Reference" depending on level:
not from RBC:
L0: R
LNTC: R
L1: A
L2: R[1]
L3: R[1]
#ANALYSE-VALUNISIG-4563#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4415#REF# FCT BG/L1 Gap in MA
#TEST-VAL-SUB026-3844#REF# FCT BG/L2[1] Buffered TRIP command overwritten by later buffered infill MA
#TEST-VAL-SUB026-4B40#REF# FCT BG/L3[1] FS/L3 acceptance of EOLM and infill location reference LTO-L1 onboard
#TEST-VAL-SUB026-4697#REF# FCT LOOP/L1 LS acceptance of EOL information

#REQ-UNISIG-SUB026-010630#REF# to.table.4.8.3.1 #ANA-UNISIG-InfillInformation-0001:01#REF#
When infill information should be stored in a LTO buffer and these information includes a LTO, the LTO shall be deleted instead of a buffering.
UNISIG clarification
#TEST-VAL-SUB026-4793#REF# FCT basic function Reception of infill level transion order in L1 announcement area

#REQ-UNISIG-SUB026-010021#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Track Conditions excluding big metal masses" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
TEST APPROACH:
All packets used to send track conditions excluding BMM by trackside are considered.
P69 is omitted, as TC 'Station Platforms' is not part of R8.0
#ANALYSE-VALUNISIG-4564#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7735#REF# FCT P39 - BG/L0[1], BG/L1, RBC/L1[2], BG/L2[1] Acceptance of TC 'Change of traction power' L0 (BG), L1(BG, RBC), L2(BG)
#TEST-VAL-SUB026-7736#REF# FCT P39 - BG/L3[1], RBC/L3 Acceptance of TC 'Change of traction power' L3 (BG, RBC)
#TEST-VAL-SUB026-3845#REF# FCT P39 - RBC/L2 Track Condition Change of Traction System - A.3.4 Reset leads to deletion of change information
#TEST-VAL-SUB026-4B35#REF# FCT P39, P68 - loop/L1 Acceptance of 'Track Conditions' (P68, P39) and 'Route Suitability Data' (P70) via in-fill by loop in L1
#TEST-VAL-SUB026-7728#REF# FCT P40 - BG/L0[1] Acceptance of 'Track Conditions' (P40) from BG in L0
#TEST-VAL-SUB026-7729#REF# FCT P40 - BG/L1 Acceptance of TC 'Change of allowed power consumption' from BG in L1
#TEST-VAL-SUB026-7732#REF# FCT P40 - BG/L2[1] Acceptance of TC 'Change of allowed power consumption' from BG in L2
#TEST-VAL-SUB026-7733#REF# FCT P40 - BG/L3[1] Acceptance of TC 'Change of allowed power consumption' - BG/L3
#TEST-VAL-SUB026-7737#REF# FCT P40 - BG/NTC[1] Acceptance of TC 'Change of allowed power consumption' - SN/NTC
#TEST-VAL-SUB026-7727#REF# FCT P40 - RBC/L0[2] Acceptance of TC 'Allowed power consumption' - RBC/L0
#TEST-VAL-SUB026-7730#REF# FCT P40 - RBC/L1[2] Acceptance of TC 'Allowed power consumption' - RBC/L1
#TEST-VAL-SUB026-7731#REF# FCT P40 - RBC/L2 Acceptance of TC 'Allowed power consumption' - RBC/L2
#TEST-VAL-SUB026-7734#REF# FCT P40 - RBC/L3 Acceptance of TC 'Allowed power consumption' - RBC/L3
#TEST-VAL-SUB026-7738#REF# FCT P40 - RBC/NTC[2] Acceptance of TC 'Allowed power consumption' - RBC/NTC
#TEST-VAL-SUB026-7726#REF# FCT P40 - loop/L1 Acceptance of TC 'Allowed power consumption' - loop/L1
#TEST-VAL-SUB026-4219#REF# FCT P68 - BG/L0[1] L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-3696#REF# FCT P68 - BG/L1, RBC/L1[2] EoA, SVL and TC supervision with broken link chain
#TEST-VAL-SUB026-4220#REF# FCT P68 - BG/L2[1] L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-5710#REF# FCT P68 - BG/L3[1] Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4310#REF# FCT P68 - RBC/L2 TC Excluding Big Metal Masses PT/SR/FS
#TEST-VAL-SUB026-5709#REF# FCT P68 - RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4C91#REF# FCT P68, P39 - BG/NTC, BG/NTC[1] Acceptance of Track Conditions excluding big metal masses (P39, P68) from BG in SN/STM
#TEST-VAL-SUB026-4B31#REF# FCT P68, P39 - RBC/L0[2] acceptance of 'Track Conditions excluding big metal masses' (P68, P39) from BG/L0[2]
#TEST-VAL-SUB026-4C92#REF# FCT P68, P39 - RBC/NTC, RBC/NTC[2] Acceptance of "Track Conditions excluding big metal masses" (P39, P68): SN/STM (from RBC)

#REQ-UNISIG-SUB026-010022#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Track Condition big metal masses" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
not relevant
#ANALYSE-VALUNISIG-4565#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4224#REF# FCT BG/L0, BG/NTC BMM handling in UN/SN
#TEST-VAL-SUB026-4223#REF# FCT BG/L1 BMM handling in SR/TR/PT in L1
#TEST-VAL-SUB026-4222#REF# FCT BG/L2 BMM handling in FS/OS
#TEST-VAL-SUB026-5710#REF# FCT BG/L3 Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3

#REQ-UNISIG-SUB026-010023#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Location Identity (NID_C + NID_BG transmitted in the balise telegrams)" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
not relevant

--- FINALISED ---
The Location Identity isn't a separate information. NID_C + NID_BG are evaluated togehter with the balise consistency checks and the
requirements for location data (see chapter 3.6).
#ANALYSE-VALUNISIG-4527#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010025#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Recognition of exit from Trip mode" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A
#ANALYSE-VALUNISIG-4567#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4212#REF# FCT RBC/L2 unconditional emergency stop message TR, PT - MA accepted after emergency revoked
#TEST-VAL-SUB026-4B42#REF# FCT RBC/L3 FS/L3 - acceptance of messages Unconditional Emergency Stop and Recognition of exit from Trip mode

#REQ-UNISIG-SUB026-010026#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Acknowledgement of Train Data" depending on level:
not from RBC:
not relevant

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
#ANALYSE-VALUNISIG-4568#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4B30#REF# FCT RBC/L0; RBC/L1; RBC/L2 Acceptance of Acknowledgement of Train Data (Message 8) depending on level
#TEST-VAL-SUB026-5709#REF# FCT RBC/L3 Acceptance of P3, P41, P42, P45, P57, P58, P68, P70 from RBC in L3
#TEST-VAL-SUB026-4487#REF# FCT RBC/NTC SN/STM - acceptance msg. 8, 32, 39 - train location when entering SN/STM

#REQ-UNISIG-SUB026-3481:01#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Co-operative shortening of MA + (optional) Mode Profile + (optional) List of Balises for SH area" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A[3][5]
L3: A[3][5]
exception [4] is realized through 3.7.2.3
#ANALYSE-VALUNISIG-4569#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4780#REF# FCT RBC/L0 Request to Shorten MA rejected in L0
#TEST-VAL-SUB026-4781#REF# FCT RBC/L1 Request to Shorten MA rejected in L1
#TEST-VAL-SUB026-3098#REF# FCT RBC/L2 Cooperative shortenting of MA
#TEST-VAL-SUB026-5715#REF# FCT RBC/L3, RBC/L3[3],[5] Acceptance of P254, M9 and P140 in L3
#TEST-VAL-SUB026-4782#REF# FCT RBC/NTC Request to Shorten MA rejected in STM

#REQ-UNISIG-SUB026-010027#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Unconditional Emergency Stop" depending on level:
not from RBC:
not relevant

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
#ANALYSE-VALUNISIG-4570#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4A54#REF# FCT RBC/L0[2] Unconditional Emergency Stop (cond [2]); UN, OS
#TEST-VAL-SUB026-3874#REF# FCT RBC/L1[2] Acceptances of unconditionalEmergencyStop L1 (level transition to L2 announced)
#TEST-VAL-SUB026-4A51#REF# FCT RBC/L2 Unconditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-4B42#REF# FCT RBC/L3 FS/L3 - acceptance of messages Unconditional Emergency Stop and Recognition of exit from Trip mode
#TEST-VAL-SUB026-4C88#REF# FCT RBC/NTC[2], RBC/NTC Manage Unconditional Emergency Stop: SN/STM

#REQ-UNISIG-SUB026-010028#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Conditional Emergency Stop" depending on level:
not from RBC:
not relevant

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A
L3: A
#ANALYSE-VALUNISIG-4571#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4334#REF# FCT RBC/L0[2] processing of Conditional Emergency Stop from level transition buffer
#TEST-VAL-SUB026-4A62#REF# FCT RBC/L1 Conditional Emergency Stop Inactive on L1 (FS)
#TEST-VAL-SUB026-4A64#REF# FCT RBC/L1[2] Conditional Emergency Stop on L1
#TEST-VAL-SUB026-4283#REF# FCT RBC/L2 Conditional Emergency Stop - SR
#TEST-VAL-SUB026-4B43#REF# FCT RBC/L3 FS/L3 - acceptance of Conditional Emergency Stop and Revocation of Emergency Stop
#TEST-VAL-SUB026-4C90#REF# FCT RBC/NTC Manage Conditional Emergency Stop: SN/STM
#TEST-VAL-SUB026-4C89#REF# FCT RBC/NTC[2] Manage Conditional Emergency Stop: SN/STM

#REQ-UNISIG-SUB026-3498#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Revocation of Emergency Stop (Conditional or Unconditional)" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A
TEST APPROACH:
Note: The information 'Revocation of Emergency Stop' is rejected in L0/NTC and UN/SN the verification in black box test is hence not
unambiguous.
#ANALYSE-VALUNISIG-4572#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4868#REF# FCT RBC/L0 (CES) Revocation of Emergency Stop not stored in level transition buffer L0->L2
#TEST-VAL-SUB026-4333#REF# FCT RBC/L0 (UES) processing of Unconditional Emergency Stop from level transition buffer
#TEST-VAL-SUB026-4867#REF# FCT RBC/L1 Revocation of Emergency Stop not stored in level transition buffer L1->L2
#TEST-VAL-SUB026-4A51#REF# FCT RBC/L2 Unconditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-4B43#REF# FCT RBC/L3 FS/L3 - acceptance of Conditional Emergency Stop and Revocation of Emergency Stop
#TEST-VAL-SUB026-4A98#REF# FCT RBC/NTC Revocation of Conditional Emergency Stop; SN/STM

#REQ-UNISIG-SUB026-010030#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "SH refused" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4573#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7966#REF# FCT RBC/L2, RBC/L2[3], RBC/L3, RBC/L3[3] SH Refused accepted only after RBC acknowledges Validated Train Data

#REQ-UNISIG-SUB026-010029#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "SH authorised + (optional) List of Balises for SH area" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4574#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7965#REF# FCT RBC/L2, RBC/L2[3] SH Authorized accepted only after RBC acknowledges Validated Train Data (L2)
#TEST-VAL-SUB026-5716#REF# FCT RBC/L3, RBC/L3[3] Acceptance of M28 in L3

#REQ-UNISIG-SUB026-010031#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Trackside constituent System Version" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
Rel. 8.0.: 
this information conform Configuration Determination (Msg. 32)
#ANALYSE-VALUNISIG-4575#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3209#REF# FCT BG/L0 BG with unsupported M_VERSION in L0
#TEST-VAL-SUB026-3206#REF# FCT BG/L1, BG/L2 BG with unsupported M_VERSION: transition into TR
#TEST-VAL-SUB026-4B46#REF# FCT BG/L3, RBC/L3 FS/L3 acceptance of Trackside constituent System Version
#TEST-VAL-SUB026-4736#REF# FCT BG/NTC SN/STM - PR at every passage of an LRBG compliant balise, System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-7592#REF# FCT RBC/L0 Check of M_VERSION=127 by radio
#TEST-VAL-SUB026-3018#REF# FCT RBC/L1 Connection establishment System Version supported/not supported
#TEST-VAL-SUB026-4829#REF# FCT RBC/L2 Acceptance of message 32 from accepting RBC
#TEST-VAL-SUB026-4489#REF# FCT RBC/NTC SN/STM - no response to PR when passing level transition location (min safe rear end) - reception of message 32 with incompatible version

#REQ-UNISIG-SUB026-010032#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "System Version order" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
not relevant
#ANALYSE-VALUNISIG-4576#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7095#REF# FCT L0 Determining the operated system version of erroneous BG
#TEST-VAL-SUB026-7093#REF# FCT L1 Determining the operated system version, in relation to non-RBC trackside constituents
#TEST-VAL-SUB026-7099#REF# FCT L2 Evaluation of balise message according to received system version order
#TEST-VAL-SUB026-7120#REF# FCT L3 Evaluation of System Version order in OS, TR, PT
#TEST-VAL-SUB026-7096#REF# FCT NTC Determining the operated system version of BG with duplicated balise

#REQ-UNISIG-SUB026-010033#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-003651#REF#
#REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Track Ahead Free Request" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4577#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4D35#REF# FCT RBC/L2 Manage Track Ahead Free request: SR, OS
#TEST-VAL-SUB026-5721#REF# FCT RBC/L2[3], RBC/L3[3] Information from RBC discarded if filter condition [3] not fulfilled
#TEST-VAL-SUB026-4B44#REF# FCT RBC/L3 OS/L3 acceptance TAF request, RV area and RV supervision information

#REQ-UNISIG-SUB026-010034#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Train Running number" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A
#ANALYSE-VALUNISIG-4578#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3766#REF# FCT RBC/L2 Train Running Number from different sources
#TEST-VAL-SUB026-5715#REF# FCT RBC/L3 Acceptance of P254, M9 and P140 in L3

#REQ-UNISIG-SUB026-010035#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Initiation of session" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A
#ANALYSE-VALUNISIG-4579#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3019#REF# FCT RBC/L2 Initiation of a communication session by RBC
#TEST-VAL-SUB026-5723#REF# FCT RBC/L3 Acceptance of Initiation of session in L3

#REQ-UNISIG-SUB026-010100#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Acknowledgement of session termination" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
TEST APPROACH:
RIU is not part of R8.0, so the verification of line "not from RBC" is omitted
#ANALYSE-VALUNISIG-4580#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5712#REF# FCT RBC/L0 Session termination in L0
#TEST-VAL-SUB026-3018#REF# FCT RBC/L1 Connection establishment System Version supported/not supported
#TEST-VAL-SUB026-3019#REF# FCT RBC/L2 Initiation of a communication session by RBC
#TEST-VAL-SUB026-5723#REF# FCT RBC/L3 Acceptance of Initiation of session in L3
#TEST-VAL-SUB026-4487#REF# FCT RBC/NTC SN/STM - acceptance msg. 8, 32, 39 - train location when entering SN/STM

#REQ-UNISIG-SUB026-010036#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Train rejected" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A
#ANALYSE-VALUNISIG-4581#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5527#REF# FCT RBC/L2 SoM - deletion of stored position data on reception of Train Rejected
#TEST-VAL-SUB026-8114#REF# FCT RBC/L3 Acceptance of Train Rejected in L3

#REQ-UNISIG-SUB026-010037#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Train accepted" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A
#ANALYSE-VALUNISIG-4582#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5529#REF# FCT RBC/L2 Variable Q_STATUS is Invalid in PositionReport (RBC accepts)
#TEST-VAL-SUB026-8115#REF# FCT RBC/L3 Acceptance of M41 in L3

#REQ-UNISIG-SUB026-010038#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "SoM Position Report Confirmed by RBC" depending on level:
not from RBC:
not relevant

from RBC:
L0: R
LNTC: R
L1: R
L2: A
L3: A
#ANALYSE-VALUNISIG-4583#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4208#REF# FCT RBC/L2 SoM stored train location confirmed by RBC
#TEST-VAL-SUB026-8116#REF# FCT RBC/L3 Acceptance of M43 in L3

#REQ-DESIGN-CR-0078#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Reversing Area Information" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4584#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4271#REF# FCT BG/L0[1] Pkt 138,139 accepted and buffered in UN
#TEST-VAL-SUB026-3598#REF# FCT BG/L1 New RV information replace the one already available on-board
#TEST-VAL-SUB026-4421#REF# FCT BG/L2 accepted information from BG in L2 (pkt P12, 21, 27, 70, 51, 5, 138, 139, 72)
#TEST-VAL-SUB026-4B33#REF# FCT BG/L2[1] Acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' depending on level
#TEST-VAL-SUB026-4B48#REF# FCT BG/L3[1] Acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' depending on level
#TEST-VAL-SUB026-4452#REF# FCT BG/NTC acceptance NV, RV info in SN from BG without LTO
#TEST-VAL-SUB026-4762#REF# FCT BG/NTC[1] Acception of P138 and P139 via balises while Level is STM (an L1 transition order is given)
#TEST-VAL-SUB026-5718#REF# FCT RBC/L0[2] Acceptance of RV information in L0
#TEST-VAL-SUB026-4B32#REF# FCT RBC/L1[2] Acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' depending on level
#TEST-VAL-SUB026-4C19#REF# FCT RBC/L2 Stored data: Reversing Area Information and Reversing Supervision Information when changing to RV/L2
#TEST-VAL-SUB026-8117#REF# FCT RBC/L2[3] P138/P139 received in L2, pending response to Validated train data
#TEST-VAL-SUB026-4B44#REF# FCT RBC/L3 OS/L3 acceptance TAF request, RV area and RV supervision information
#TEST-VAL-SUB026-4447#REF# FCT RBC/NTC acceptance NV, RV info in SN from RBC without LTO
#TEST-VAL-SUB026-4446#REF# FCT RBC/NTC[2] acceptance NV, RV info in SN from RBC with LTO
#TEST-VAL-SUB026-4453#REF# EET error expectation acceptance NV, V_MAIN, RV info in SN from BG with LTO
#TEST-VAL-SUB026-4B36#REF# FCT loop/L1 acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' via infill by loop in L1

#REQ-DESIGN-CR-0079#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Reversing Supervision Information" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4585#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4271#REF# FCT BG/L0[1] Pkt 138,139 accepted and buffered in UN
#TEST-VAL-SUB026-3598#REF# FCT BG/L1 New RV information replace the one already available on-board
#TEST-VAL-SUB026-4B33#REF# FCT BG/L2[1] Acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' depending on level
#TEST-VAL-SUB026-4B48#REF# FCT BG/L3[1] Acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' depending on level
#TEST-VAL-SUB026-4452#REF# FCT BG/NTC acceptance NV, RV info in SN from BG without LTO
#TEST-VAL-SUB026-4762#REF# FCT BG/NTC[1] Acception of P138 and P139 via balises while Level is STM (an L1 transition order is given)
#TEST-VAL-SUB026-5718#REF# FCT RBC/L0[2] Acceptance of RV information in L0
#TEST-VAL-SUB026-4B32#REF# FCT RBC/L1[2] Acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' depending on level
#TEST-VAL-SUB026-4C19#REF# FCT RBC/L2 Stored data: Reversing Area Information and Reversing Supervision Information when changing to RV/L2
#TEST-VAL-SUB026-8117#REF# FCT RBC/L2[3] P138/P139 received in L2, pending response to Validated train data
#TEST-VAL-SUB026-4B44#REF# FCT RBC/L3 OS/L3 acceptance TAF request, RV area and RV supervision information
#TEST-VAL-SUB026-4446#REF# FCT RBC/NTC[2] acceptance NV, RV info in SN from RBC with LTO
#TEST-VAL-SUB026-4B36#REF# FCT loop/L1 acceptance of 'Reversing Area Information' and 'Reversing Supervision Information' via infill by loop in L1

#REQ-UNISIG-SUB026-010039#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Default Balise/Loop/RIU information" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
not relevant
TEST APPROACH:
RIU is not part of R8.0, so the verification for RIU is omitted
#ANALYSE-VALUNISIG-4586#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4B34#REF# FCT BG/L0 acceptance of 'Default Balise/Loop/RIU information' (P254) depending on level
#TEST-VAL-SUB026-4692#REF# FCT BG/L2, BG/L1 acceptance P254 in FS/OS/SR/SH
#TEST-VAL-SUB026-5715#REF# FCT BG/L3 Acceptance of P254, M9 and P140 in L3
#TEST-VAL-SUB026-4736#REF# FCT BG/NTC SN/STM - PR at every passage of an LRBG compliant balise, System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-3607#REF# FCT LOOP/L1 non in-fill information from LOOP apart from pkt 254 neglected

#REQ-DESIGN-CR-0522#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Track Ahead Free up to level 2/3 transition location" depending on level:
not from RBC:
L0: A[9]
LNTC: A[9]
L1: A[9]
L2: R
L3: R

from RBC:
not relevant
#ANALYSE-VALUNISIG-4587#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4954#REF# FCT BG/L0, BG/L0[9], BG/L1, BG/L1[9] Track Ahead Free up to level 2/3 transition location (pkt 90)
#TEST-VAL-SUB026-4270#REF# FCT BG/NTC, BG/NTC[9] Track Ahead Free up to level 2/3 transition location (pkt 90) STM
#TEST-VAL-SUB026-4953#REF# FCT L2 Rejection of Track Ahead Free up to level 2/3 transition location from balise in L2

#REQ-UNISIG-SUB026-010040#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Permitted Braking Distance Information" depending on level:
not from RBC:
L0: R[1]
LNTC: R[1]
L1: A
L2: R[1]
L3: R[1]

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4588#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-8118#REF# FCT BG/L0, RBC/L0, RBC/L2[3] PBD Information rejected in L0 (no LTO onboard) and in L2 (no response to validated train data)
#TEST-VAL-SUB026-3A67#REF# FCT BG/L0[1] PBD Information - accepted in UN/L0 (from BG), supervised when in LS/L1
#TEST-VAL-SUB026-3A69#REF# FCT BG/L1 SR/L1 - Acceptance of PBD Information from BG
#TEST-VAL-SUB026-3A72#REF# FCT BG/L2[1], RBC/L1[2] acceptance of PBD Information from BG in L2 and from RBC in L1
#TEST-VAL-SUB026-3A73#REF# FCT BG/L3[1], RBC/LNTC[2] acceptance of PBD Information from BG in L3 and from RBC in LNTC
#TEST-VAL-SUB026-3A68#REF# FCT BG/LNTC[1] PBD Information - accepted in SN/NTC (from BG), supervised when in OS/L1
#TEST-VAL-SUB026-3A65#REF# FCT RBC/L0[2] PBD Information accepted in mode UN via RBC/L0[2] and supervised in mode FS
#TEST-VAL-SUB026-3A70#REF# FCT RBC/L2 SB/L2: acceptance of PBD Information from RBC
#TEST-VAL-SUB026-3A96#REF# FCT RBC/L3 PBD information when mode changes to FS, OS, LS
#TEST-VAL-SUB026-3A74#REF# FCT loop/L1 FS/L1: acceptance of PBD Information from loop, deleted when entering mode SR

#REQ-UNISIG-SUB026-010041#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Level Crossing information" depending on level:
not from RBC:
L0: R[1][2]
LNTC: R[1][2]
L1: A
L2: A
L3: A

from RBC:
L0: R[2]
LNTC: R[2]
L1: R[2]
L2: A[3]
L3: A[3]
#ANALYSE-VALUNISIG-4589#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7648#REF# FCT BG/L0[1], BG/L0[2], RBC/L0[2] Acceptance of Level Crossing Information in L0
#TEST-VAL-SUB026-7650#REF# FCT BG/L1, RBC/L1[2] Acceptance of Level Crossing Information in L1
#TEST-VAL-SUB026-7651#REF# FCT BG/L2, RBC/L2 Acceptance of Level Crossing Information in L2
#TEST-VAL-SUB026-7652#REF# FCT BG/L3, RBC/L3 Acceptance of Level Crossing Information in L3
#TEST-VAL-SUB026-7649#REF# FCT BG/NTC[1], BG/NTC[2], RBC/NTC[2] Acceptance of Level Crossing Information in NTC
#TEST-VAL-SUB026-8124#REF# FCT loop/L1 FS/L1: acceptance of LX Information from loop, deleted when entering mode SH

#REQ-UNISIG-SUB026-010010#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Virtual balise Cover order" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A


from RBC:
not relevant
VBC function is not realized

=> P6 is to be ignore

#REQ-UNISIG-SUB026-010438#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
acceptance "Data to be used by applications outside ERTMS/ETCS" depending on level:
not from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A

from RBC:
L0: A
LNTC: A
L1: A
L2: A
L3: A
#ANALYSE-VALUNISIG-5254#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7051#REF# FCT L0, NTC Acceptance of P44 in L0, NTC
#TEST-VAL-SUB026-7050#REF# FCT L1, L2, L3 Acceptance of P44 in L1, L2, L3
#TEST-VAL-SUB040-0060#REF# FCT LOOP/L1 Acceptance of non in-fill P44 from LOOP

#REQ-UNISIG-SUB026-1202#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [1]: stored onboard if an order to switch to L1 at a further location has been  received.
#ANALYSE-VALUNISIG-4590#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4219#REF# FCT L0 L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4420#REF# FCT L2 LTO L1 announced - accepted information from BG in L2 (12, 21, 27, 138, 139, 68, 70, 80, 65, 5)
#TEST-VAL-SUB026-5710#REF# FCT L3 Acceptance of P3, P12, P21, P27, P49, P51 P65, P66, P67, P68 P72, P76 from BG in L3
#TEST-VAL-SUB026-4762#REF# FCT NTC Acception of P138 and P139 via balises while Level is STM (an L1 transition order is given)

#REQ-UNISIG-SUB026-1203#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [2]: stored onboard if an order to switch to L2/3 at a further location has been received.
#ANALYSE-VALUNISIG-4591#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4306#REF# FCT L0->L2 TC Excluding Big Metal Masses FS/UN
#TEST-VAL-SUB026-5717#REF# FCT L0->L3 Buffering of RBC information received in L0 for usage in L3
#TEST-VAL-SUB026-3874#REF# FCT L1->L2 Acceptances of unconditionalEmergencyStop L1 (level transition to L2 announced)
#TEST-VAL-SUB026-5719#REF# FCT L1->L3 Buffering of RBC information received in L1 for usage in L3
#TEST-VAL-SUB026-4760#REF# FCT NTC->L2 Acception of L2-MA, SSP, GP via radio while Level is STM (an transition order to level 2 is given)
#TEST-VAL-SUB026-5720#REF# FCT NTC->L3 Buffering of RBC information received in NTC for usage in L3

#REQ-DESIGN-CR-0367#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [3]:
rejected if Train Data has been sent to the RBC and the “Acknowledgement of Train Data” has not been received yet.
#ANALYSE-VALUNISIG-4592#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5475#REF# EET CFX00040366 Reception of MA from ACC-RBC - changed train data not reported to HO-RBC as no session to HO-RBC exists
#TEST-VAL-SUB026-5476#REF# EET CFX00040366 Reception of MA from ACC-RBC while HO-RBC has not send M8 in response to M129 yet
#TEST-VAL-SUB026-5477#REF# EET CFX00040366 Reception of MA from ACC-RBC - Acknowledgement of Train Data received after MA before supervision change
#TEST-VAL-SUB026-5478#REF# EET CFX00040366 Reception of MA from ACC-RBC - Acknowledgement of Train Data received after supervision change
#TEST-VAL-SUB026-5721#REF# FCT L2, L3 Information from RBC discarded if filter condition [3] not fulfilled
#TEST-VAL-SUB026-4982#REF# EET error expectation MA and MP rejection in L2 on receipt from RBC
#TEST-VAL-SUB026-5996#REF# EET error expectation Evaluation of P44 received with not accepted SH Authorized

#REQ-DESIGN-CR-0501#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [4]:
rejected if the SSP and gradient already available on-board or given together with the MA do not cover the full length of the MA.
exception[4] is conformed with 3.7.2.3 (#REQ-DESIGN-CR-0499#REF#)

The cover of the ma cannot check before all received informations are evaluated. Therefore the check is performed after and not during the
reception of the information.
realised by: #REQ-DESIGN-CR-0499#REF#

#REQ-DESIGN-CR-0502#REF# table.4.8.3.1 #REQ-DESIGN-CR-0320#REF#
#REQ-UNISIG-SUB026-1200:01#REF#
exception [5]:
rejected if emergency stop(s) have been accepted and are not yet revoked or deleted onboard (see mode transitions)
TEST APPROACH:
The following aspects have been identified:
1) dependency on level 
1.1) L2
1.2) L3
2) dependency on Emergency stop (kind, deletion/revocation):
2.1) Conditional Emergency Stop (CES)
2.1.1) CES revocation
2.1.2) CES deletion
2.2) UnConditional Emergency Stop (UCES)
2.2.1) UCES revocation
2.2.2) UCES deletion
#ANALYSE-VALUNISIG-4593#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5028#REF# FCT 1.1, 2.1.2 Emergency stop deleted due to override activation
#TEST-VAL-SUB026-5722#REF# FCT 1.2, 2.1.1 Information from RBC discarded if filter condition [5] not fulfilled
#TEST-VAL-SUB026-4212#REF# FCT 2.2.1 unconditional emergency stop message TR, PT - MA accepted after emergency revoked
#TEST-VAL-SUB026-4282#REF# FCT 2.2.2 unconditional emergency stop message deleted when entering SR
#TEST-VAL-SUB026-4931#REF# EET error expectation Conditional emergency stop after level transition L2->L1->L2
#TEST-VAL-SUB026-4A72#REF# EET error expectation Conditional Emergency Stop trough L1
#TEST-VAL-SUB026-7143#REF# EET error expectation Buffer evaluation sequence CES/MA

#REQ-UNISIG-SUB026-010042#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
#ANA-UNISIG-TSRInhibition-0001#REF#
exception [8]
revocable TSRs shall be rejected if information “inhibition of revocable TSRs from balises in L2/3” is stored on-board

Remark:
The information “inhibition of revocable TSRs from balises in L2/3” shall be used only in the modes, that are defined in 4.5.2 line
"Inhibition of revocable TSRs from balises(only level 2/3)".
TEST APPROACH:
Requirement outlined in 4.5.2 prevails 4.8.3[8] us outlined in the Remark. This aspect is covered by the verification of
#REQ-UNISIG-SUB026-010147#REF#
#ANALYSE-VALUNISIG-4594#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5818#REF# FCT basic function Inhibition of revocable TSRs from balises in L2/3 deleted due to session termination

#REQ-DESIGN-CR-0523#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [9]:
rejected if no level 2/3 transition order is stored onboard.
#ANALYSE-VALUNISIG-4595#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4954#REF# FCT L0, L1 Track Ahead Free up to level 2/3 transition location (pkt 90)
#TEST-VAL-SUB026-4270#REF# FCT NTC Track Ahead Free up to level 2/3 transition location (pkt 90) STM

#REQ-UNISIG-SUB026-3223#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [10]: rejected if the referred LRBG is memorised to have been reported with different “previous LRBG”
exception [10] is realized through 3.4.2.3.3.8 (see #REQ-UNISIG-SUB026-3222#REF#)

It is not relevant, whether the check is realized by the reception of the information or later during the evalution of the information.
realised by: #REQ-UNISIG-SUB026-3222#REF#

#REQ-UNISIG-SUB026-010043#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [11]
rejected if a level transition order is received in the same message, or if a previous level transition order has announced a level transition
still to be executed
It is not relevant, whether the check is realized by the reception of the information or later during the evalution of the information.
realised by: #REQ-DESIGN-CR-0732:01#REF#
realised by: #REQ-UNISIG-SUB026-3245#REF#

#REQ-DESIGN-CR-0732:01#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-010043#REF#
If a conditional level transition order is received together with a normal level transition order, the conditional level transition order shall
be ignored.
In this case a basic diagnostic event shall be created.
#TEST-VAL-SUB026-5537#REF# FCT LTO for current location , CFX00039987 Evaluation priority between LevelTransitionOrder and ConditionalLevelTransitionOrder
#TEST-VAL-SUB026-5538#REF# FCT LTO for further location , CFX00039987 Validity of conditional lvlTransitionOrder sent with lvlTransitionOrder applicable at further pos

#REQ-UNISIG-SUB026-3245#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-010043#REF#
If a conditional level transition order is received during a normal level transition announcement, the conditional level transition order shall
be ignored.
#TEST-VAL-SUB026-5591#REF# FCT basic function CLTO shall be ignored when receiving during LTO announcement

#REQ-UNISIG-SUB026-010044#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [12]
rejected if the text message is sent with a request for report of driver acknowledgement with the same text message identifier as a previously
received text message, which the driver has not yet acknowledged
exception [12] is realized through 3.12.3.5.3 (see #REQ-ESBO_RS026-002266#REF#)
realised by: #REQ-UNISIG-SUB026-002266#REF#

#REQ-UNISIG-SUB026-010439#REF# table.4.8.3.1 #REQ-UNISIG-SUB026-1200:01#REF#
exception [13]
rejected if not received together with an immediate level transition order to L1/2/3
realised by: #REQ-UNISIG-SUB026-010018#REF#

#REQ-UNISIG-SUB026-005419#REF# 4.8.3.2-


[6] exception: stored by ETCS onboard if an order to switch to level NTC X at a further location has been received.
[7] exception: rejected by ETCS onboard if no order to switch to level NTC X at a further location has been received.
realised by: #REQ-UNISIG-SUB026-3493#REF#
realised by: #REQ-UNISIG-SUB026-3494#REF#
realised by: #REQ-UNISIG-SUB026-3491#REF#
realised by: #REQ-UNISIG-SUB026-3492#REF#

#REQ-UNISIG-SUB026-3493#REF# table.4.8.3.2 #REQ-UNISIG-SUB026-005419#REF#
acceptance "STM max speed" from NTC X through STM interface on level:
L0: A[7]
LNTC X: R
LNTC Y: R[6]
L1: A[7]
L2: A[7]
L3: A[7]
TEST APPROACH:
NOTE regarding LNTC X:R: The transition from LNTC X to LNTC X is not possible. However, the OBU ETCS in SN/LNTC X should accept and take into
account ' STM max speed' received from STM X in state HS, from the level transition border until state report DA is received from STM X, too.
#TEST-VAL-SUB026-4483#REF# FCT L0 UN/L0 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4482#REF# FCT L1 SR/L1 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4474#REF# FCT L2 FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-5762#REF# FCT L3 acceptance STM system speed/distance and STM max speed L3[7]
#TEST-VAL-SUB035-5094#REF# FCT LNTC X STM max speed from NTC X when train operating in NTC X
#TEST-VAL-SUB035-0364#REF# FCT LNTC Y[6] Senden V_STMMAX beim Levelwechsel STMx-->STMy(Mode SN)

#REQ-UNISIG-SUB026-3494#REF# table.4.8.3.2 #REQ-UNISIG-SUB026-005419#REF#
acceptance "STM system speed/distance" from NTC X through STM interface on level:
L0: A[7]
LNTC X: R
LNTC Y: R
L1: A[7]
L2: A[7]
L3: A[7]
#TEST-VAL-SUB026-4483#REF# FCT L0 UN/L0 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4482#REF# FCT L1 SR/L1 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4474#REF# FCT L2 FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-5762#REF# FCT L3 acceptance STM system speed/distance and STM max speed L3[7]
#TEST-VAL-SUB035-0367#REF# FCT NTC Senden V_STMSYS/D_STMSYS beim Levelwechsel STMx-->STMy(Mode SN)

#REQ-UNISIG-SUB026-3491#REF# table.4.8.3.2 #REQ-UNISIG-SUB026-005419#REF#
[6] exception: stored by the ETCS onboard  if an order to switch to level NTC X at a further location has been received.
#TEST-VAL-SUB035-0364#REF# FCT basic function Senden V_STMMAX beim Levelwechsel STMx-->STMy(Mode SN)

#REQ-UNISIG-SUB026-3492#REF# table.4.8.3.2 #REQ-UNISIG-SUB026-005419#REF#
[7] exception: rejected by the ETCS onboard  if no order to switch to level NTC X at a further location has been received.
#TEST-VAL-SUB026-4508#REF# FCT L0 acceptance STM system speed/distance and STM max speed L0[7]
#TEST-VAL-SUB026-4507#REF# FCT L1 acceptance STM system speed/distance and STM max speed L1[7]
#TEST-VAL-SUB026-4506#REF# FCT L2 acceptance STM system speed/distance and STM max speed L2[7] and NL/L2
#TEST-VAL-SUB026-5762#REF# FCT L3 acceptance STM system speed/distance and STM max speed L3[7]

#REQ-UNISIG-SUB026-0755:01#REF# 4.8.4.1.1 #REQ-UNISIG-SUB026-3338#REF#
For infill information, only the columns FS and LS apply. In all other modes, infill information is rejected.
#TEST-VAL-SUB026-4827#REF# FCT FS In-fill in FS
#TEST-VAL-SUB026-3732#REF# FCT LS In-fill MA with MP-OS overrides current Mode Profile LS starting with the in-fill reference location
#TEST-VAL-SUB026-4828#REF# EET error expectation In-fill in anderen Modes

#REQ-UNISIG-SUB026-2162:01#REF# table.4.8.4
NR = Not Relevant	A = Accepted	R = Rejected









[1]: for level 2/3: only if following the reception of the information “Recognition of Exit from TR mode” with a more recent time stamp; for
level 1: rejected
[2]: only if a cab is active
[3]: for order to establish a communication session: RBC ID/phone number is stored without establishing the communication session
[4]: only if valid Train Data are stored on-board
[5]: only level transition announcement (i.e., immediate level transition order and conditional level transition order shall be rejected)
[6]: rejected if override is active
[7]: only immediate level transition order and conditional level transition order shall be accepted (i.e., level transition announcement shall
be rejected) and stored for later evaluation (see 4.4.8.1.5)
[8]: only RBC transition order with null distance to execution shall be accepted (i.e., RBC transition announcement shall be rejected) for
storing the RBC ID/phone number (see 4.4.8.1.5.2)

--- FINALISED ---
The modes SF and IS can ignore, because no information from trackside are accepted in these modes.
see #REQ-UNISIG-SUB026-3008#REF# and #REQ-UNISIG-SUB026-3009#REF#.
#REQ-UNISIG-SUB026-3008#REF#, #REQ-UNISIG-SUB026-3009#REF#
------
The mode NP can ignore, because no information can received when the system is powerless.

------
The modes SF and IS are not relevant for the informations "STM max speed" and  "STM system speed/distance" because in these
modes are no level transition order or announcement is possible (see 4.8.3.2)
TEST APPROACH:
The filter condition in this requirement and its refinements are realized centrally by the software module packet handler (PH).
The acceptance of information depending on the mode is covered by PH module verification. The condition reject information is there by
sufficiently covered. Hence the additional VER/VAL test cases outlined here after focus on the processing of accepted information. 
Each exception is tested at leased once (equitation class) in order to verify that the condition is properly evaluated.
realised by: #REQ-UNISIG-SUB026-010047#REF#
realised by: #REQ-UNISIG-SUB026-010048#REF#
realised by: #REQ-UNISIG-SUB026-010049#REF#
realised by: #REQ-UNISIG-SUB026-010050#REF#
realised by: #REQ-DESIGN-CR-0048:02#REF#
realised by: #REQ-UNISIG-SUB026-010051#REF#
realised by: #REQ-UNISIG-SUB026-010052#REF#
realised by: #REQ-UNISIG-SUB026-010053#REF#
realised by: #REQ-UNISIG-SUB026-3228:02#REF#
realised by: #REQ-UNISIG-SUB026-3229:02#REF#
realised by: #REQ-UNISIG-SUB026-3466:01#REF#
realised by: #REQ-DESIGN-CR-0740:03#REF#
realised by: #REQ-DESIGN-CR-0349:01#REF#
realised by: #REQ-DESIGN-CR-0445:01#REF#
realised by: #REQ-UNISIG-SUB026-010055#REF#
realised by: #REQ-DESIGN-CR-0021:01#REF#
realised by: #REQ-UNISIG-SUB026-010057#REF#
realised by: #REQ-UNISIG-SUB026-010056#REF#
realised by: #REQ-UNISIG-SUB026-010058#REF#
realised by: #REQ-DESIGN-CR-0351:02#REF#
realised by: #REQ-DESIGN-CR-0352:02#REF#
realised by: #REQ-UNISIG-SUB026-010059#REF#
realised by: #REQ-DESIGN-CR-0350:02#REF#
realised by: #REQ-UNISIG-SUB026-010060#REF#
realised by: #REQ-UNISIG-SUB026-010061#REF#
realised by: #REQ-UNISIG-SUB026-3058:01#REF#
realised by: #REQ-UNISIG-SUB026-3059:01#REF#
realised by: #REQ-UNISIG-SUB026-3060:01#REF#
realised by: #REQ-UNISIG-SUB026-010062:01#REF#
realised by: #REQ-UNISIG-SUB026-010064#REF#
realised by: #REQ-UNISIG-SUB026-010065#REF#
realised by: #REQ-UNISIG-SUB026-3556:01#REF#
realised by: #REQ-UNISIG-SUB026-010066#REF#
realised by: #REQ-UNISIG-SUB026-3555:01#REF#
realised by: #REQ-UNISIG-SUB026-010067#REF#
realised by: #REQ-UNISIG-SUB026-010068#REF#
realised by: #REQ-UNISIG-SUB026-010069#REF#
realised by: #REQ-UNISIG-SUB026-010070#REF#
realised by: #REQ-UNISIG-SUB026-010071#REF#
realised by: #REQ-UNISIG-SUB026-010072#REF#
realised by: #REQ-UNISIG-SUB026-010073#REF#
realised by: #REQ-DESIGN-CR-0075:03#REF#
realised by: #REQ-UNISIG-SUB026-3496:01#REF#
realised by: #REQ-DESIGN-CR-0040:01#REF#
realised by: #REQ-UNISIG-SUB026-010074#REF#
realised by: #REQ-UNISIG-SUB026-3410:01#REF#
realised by: #REQ-UNISIG-SUB026-010075#REF#
realised by: #REQ-UNISIG-SUB026-010076#REF#
realised by: #REQ-UNISIG-SUB026-010077#REF#
realised by: #REQ-UNISIG-SUB026-010078#REF#
realised by: #REQ-UNISIG-SUB026-010079#REF#
realised by: #REQ-UNISIG-SUB026-010080#REF#
realised by: #REQ-UNISIG-SUB026-010081#REF#
realised by: #REQ-UNISIG-SUB026-010082#REF#
realised by: #REQ-UNISIG-SUB026-010083#REF#
realised by: #REQ-UNISIG-SUB026-010084#REF#
realised by: #REQ-UNISIG-SUB026-010085#REF#
realised by: #REQ-UNISIG-SUB026-010086#REF#
realised by: #REQ-UNISIG-SUB026-010087#REF#
realised by: #REQ-UNISIG-SUB026-010088#REF#
realised by: #REQ-DESIGN-CR-0524:01#REF#
realised by: #REQ-UNISIG-SUB026-010089#REF#
realised by: #REQ-UNISIG-SUB026-010090#REF#
realised by: #REQ-UNISIG-SUB026-010054#REF#
realised by: #REQ-UNISIG-SUB026-010440#REF#
realised by: #REQ-UNISIG-SUB026-1206#REF#
realised by: #REQ-DESIGN-CR-0739#REF#
realised by: #REQ-DESIGN-CR-0353:01#REF#
realised by: #REQ-UNISIG-SUB026-3462#REF#
realised by: #REQ-UNISIG-SUB026-3465:01#REF#
realised by: #REQ-UNISIG-SUB026-010091#REF#
realised by: #REQ-UNISIG-SUB026-010092#REF#
realised by: #REQ-UNISIG-SUB026-010093#REF#

#REQ-UNISIG-SUB026-010047#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "National values" depending on the modes:

accepted: SB[2], PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT[1], SN, RV
rejected: -
#ANALYSE-VALUNISIG-4598#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4D13#REF# FCT FS Check radio link (only level 2/3); TR, PT
#TEST-VAL-SUB026-3752#REF# FCT LS V_MAMODE> V_NVONSIGHT/V_NVLIMSUPERV
#TEST-VAL-SUB026-4D25#REF# FCT NL Acceptance of National Values (T_NVCONTACT) in NL
#TEST-VAL-SUB026-4D14#REF# FCT OS Check radio link (only level 2/3); OS
#TEST-VAL-SUB026-5814#REF# FCT PS Acceptance of NV in PS
#TEST-VAL-SUB026-4D22#REF# FCT PT[1] Acceptance of P3 in PT
#TEST-VAL-SUB026-4D18#REF# FCT RV Check radio link (only level 2/3); RV
#TEST-VAL-SUB026-4D17#REF# FCT SB[2] Check radio link (only level 2/3); SB, SL
#TEST-VAL-SUB026-4D19#REF# FCT SH Check radio link (only level 2/3); SH
#TEST-VAL-SUB026-4D26#REF# FCT SL Acceptance of National Values (T_NVCONTACT) in SL
#TEST-VAL-SUB026-4452#REF# FCT SN acceptance NV, RV info in SN from BG without LTO
#TEST-VAL-SUB026-4D16#REF# FCT SR Check radio link (only level 2/3); SR, NL
#TEST-VAL-SUB026-4D21#REF# FCT TR Check radio link (only level 2/3); TR, PT
#TEST-VAL-SUB026-4D15#REF# FCT UN Check radio link (only level 2/3); UN
#TEST-VAL-SUB026-4320#REF# EET error expectation PT/L1 acceptence of NV

#REQ-UNISIG-SUB026-010048#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Linking" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also; 
acceptance in mode NL is an error
#ANALYSE-VALUNISIG-4599#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4C39#REF# FCT FS, OS Stored data: Linking information when mode changes to FS/L2, OS/L2
#TEST-VAL-SUB026-4559#REF# FCT LS Mode transition LS->TR[17]
#TEST-VAL-SUB026-4C47#REF# FCT PT[4], PT[1][4] Acceptance of Linking information depending on mode PT/L2
#TEST-VAL-SUB026-4C42#REF# FCT SB[2][4] Stored data: Linking information when mode changes to SB/L2
#TEST-VAL-SUB026-4471#REF# FCT SN SN/STM acceptance pkt5 from RBC - LTO L2 onboard
#TEST-VAL-SUB026-4C43#REF# FCT SR Stored data: Linking information when mode changes to SR/L2, FS/L2
#TEST-VAL-SUB026-4219#REF# FCT UN L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4332#REF# EET error expectation PT/L2 acceptance linking information

#REQ-UNISIG-SUB026-010049#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
#ANA-UNISIG-AccInformation-0005#REF#
acceptance "Signalling Related Speed Restriction" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also

This information is accepted/rejected together with the relevant MA. A separat check is not necessary.

see analysis also
realised by: #REQ-UNISIG-SUB026-010050#REF#

#REQ-UNISIG-SUB026-010050#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
#REQ-UNISIG-SUB026-010049#REF#
acceptance "Movement Authority + (optional) Mode Profile + (optional) List of Balises for SH area" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
TEST APPROACH:
The following aspects have been identified:
1) Signalling Related Speed Restriction
(The separate verification via test has been added in order to increase the confidence in this approach)
1.1) SB[2][4]
1.2) FS
1.3) LS
1.4) SR
1.5) OS
1.6) UN
1.7) PT[1][4] (omitted refer Note below)
1.8) SN
2) Movement Authority + (optional) Mode Profile + (optional) List of Balises for SH area
2.1) SB[2][4]
2.2) FS
2.3) LS
2.4) SR
2.5) OS
2.6) UN
2.7) PT[1][4]
2.8) SN

Note: Aspect 1.7 is omitted as the signalling speed restriction is part of the L1 MA which has to be rejected in PT/L1 refer exception [1].
#ANALYSE-VALUNISIG-4601#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4B49#REF# FCT 1.1 Signalling related speed restriction: SB/L1
#TEST-VAL-SUB026-4B47#REF# FCT 1.2, 1.3 Signalling related speed restriction: LS/L1
#TEST-VAL-SUB026-4F01#REF# FCT 1.4, 1.5 Signalling related speed restriction: OS/L1, FS/L1
#TEST-VAL-SUB026-4219#REF# FCT 1.6 L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4740#REF# FCT 1.8 SN/STM - V_MAIN
#TEST-VAL-SUB026-4E10#REF# FCT 2.1 Stored data: MA, GP, SSP when changing to SB/L2
#TEST-VAL-SUB026-4220#REF# FCT 2.2 L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4B50#REF# FCT 2.3 LS/L2 - acceptance of MA, MP, List of Balises for SH Area, GP, SSP, ASP
#TEST-VAL-SUB026-4C30#REF# FCT 2.4 Stored data: Mode Profile when mode changes to SR/L2, FS/L2
#TEST-VAL-SUB026-4C49#REF# FCT 2.5 Stored data: List of balises for SH area when mode changes to FS/L2
#TEST-VAL-SUB026-4274#REF# FCT 2.6 Pkt 80 accepted and buffered in UN
#TEST-VAL-SUB026-4C37#REF# FCT 2.7 Acceptance of Mode Profile data: PT/L2
#TEST-VAL-SUB026-4760#REF# FCT 2.8 Acception of L2-MA, SSP, GP via radio while Level is STM (an transition order to level 2 is given)
#TEST-VAL-SUB026-4105#REF# EET CFX00039615 Listen von BGs im SH-Bereich

#REQ-DESIGN-CR-0048:02#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Repositioning Information" depending on the modes:

accepted: FS, LS, OS
rejected: SB, PS, SH, SR, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4602#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3092#REF# FCT FS In-fill and repositioning
#TEST-VAL-SUB026-3753#REF# FCT LS acceptance of Repositioning Information in LS
#TEST-VAL-SUB026-3774#REF# FCT OS RAMS related supervision functions ended when leaving OS
#TEST-VAL-SUB026-4887#REF# EET error expectation Check table 4.8.4 -> Repositioning Information (SB/L1)

#REQ-UNISIG-SUB026-010051#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Gradient Profile" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4603#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4220#REF# FCT FS L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4B50#REF# FCT LS LS/L2 - acceptance of MA, MP, List of Balises for SH Area, GP, SSP, ASP
#TEST-VAL-SUB026-4C11#REF# FCT OS Stored data: MA, GP, International SSP, Axle load SP when changing to OS/L2, FS/L2
#TEST-VAL-SUB026-4C37#REF# FCT PT[1][4] Acceptance of Mode Profile data: PT/L2
#TEST-VAL-SUB026-4E10#REF# FCT SB[2][4] Stored data: MA, GP, SSP when changing to SB/L2
#TEST-VAL-SUB026-4760#REF# FCT SN Acception of L2-MA, SSP, GP via radio while Level is STM (an transition order to level 2 is given)
#TEST-VAL-SUB026-4E09#REF# FCT SR Stored data: MA, GP, SSP when changing to SR/L2
#TEST-VAL-SUB026-4219#REF# FCT UN L0 information from BG stored onboard if an order to switch to L1 at a further location has been received

#REQ-UNISIG-SUB026-010052#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "International SSP" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4604#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4220#REF# FCT FS L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4B50#REF# FCT LS LS/L2 - acceptance of MA, MP, List of Balises for SH Area, GP, SSP, ASP
#TEST-VAL-SUB026-4C11#REF# FCT OS Stored data: MA, GP, International SSP, Axle load SP when changing to OS/L2, FS/L2
#TEST-VAL-SUB026-4C37#REF# FCT PT[1][4] Acceptance of Mode Profile data: PT/L2
#TEST-VAL-SUB026-4E10#REF# FCT SB[2][4] Stored data: MA, GP, SSP when changing to SB/L2
#TEST-VAL-SUB026-4760#REF# FCT SN Acception of L2-MA, SSP, GP via radio while Level is STM (an transition order to level 2 is given)
#TEST-VAL-SUB026-4E09#REF# FCT SR Stored data: MA, GP, SSP when changing to SR/L2
#TEST-VAL-SUB026-4219#REF# FCT UN L0 information from BG stored onboard if an order to switch to L1 at a further location has been received

#REQ-UNISIG-SUB026-010053#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Axle load speed profile" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4605#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3116#REF# FCT FS Effect of Q_FRONT (P27, P51, P65)
#TEST-VAL-SUB026-4B50#REF# FCT LS LS/L2 - acceptance of MA, MP, List of Balises for SH Area, GP, SSP, ASP
#TEST-VAL-SUB026-4C11#REF# FCT OS Stored data: MA, GP, International SSP, Axle load SP when changing to OS/L2, FS/L2
#TEST-VAL-SUB026-4C18#REF# FCT PT[1][4] Stored data: MA, GP, International SSP, Axle load SP when changing to TR/L2, PT/L2, FS/L2
#TEST-VAL-SUB026-4C14#REF# FCT SB[2][4] Stored data: MA, GP, International SSP, Axle load SP when changing to SB/L2, SL/L2, FS/L2
#TEST-VAL-SUB026-4F04#REF# FCT SN Determine MRSP based on ASP : SN/STM, FS/L2
#TEST-VAL-SUB026-4C12#REF# FCT SR Stored data: MA, GP, International SSP, Axle load SP when changing to SR/L2, FS/L2
#TEST-VAL-SUB026-4C15#REF# FCT UN Stored data: MA, GP, International SSP, Axle load SP when changing to UN/L0, FS/L1

#REQ-UNISIG-SUB026-3228:02#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
#ANA-UNISIG-CR0285-0001#REF#
acceptance "STM max speed" depending on the modes:

accepted: SB, FS, LS, SR, OS, UN, TR, PT, SN
rejected: PS, SH, SL, NL, RV
#TEST-VAL-SUB026-4474#REF# FCT FS FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4481#REF# FCT OS OS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4E00#REF# FCT PT Acceptance of STM max speed and STM system speed/distance: PT/L2 cond [1]
#TEST-VAL-SUB026-4E03#REF# FCT SB Acceptance of STM max speed and STM system speed/distance depending on mode: SB/L2
#TEST-VAL-SUB035-0364#REF# FCT SN Senden V_STMMAX beim Levelwechsel STMx-->STMy(Mode SN)
#TEST-VAL-SUB026-4482#REF# FCT SR SR/L1 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-8121#REF# FCT TR Acceptance of STM max speed and STM system speed/distance: TR
#TEST-VAL-SUB026-4483#REF# FCT UN UN/L0 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4C99#REF# EET error expectation Acceptance of STM max speed and STM system speed/distance: PT/L2

#REQ-UNISIG-SUB026-3229:02#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
#ANA-UNISIG-CR0285-0001#REF#
acceptance "STM system speed/distance" depending on the modes:

accepted: SB, FS, LS, SR, OS, UN, TR, PT
rejected: PS, SH, SL, NL, SN, RV
#TEST-VAL-SUB026-4474#REF# FCT FS FS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4481#REF# FCT OS OS/L2 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4E00#REF# FCT PT Acceptance of STM max speed and STM system speed/distance: PT/L2 cond [1]
#TEST-VAL-SUB026-4E03#REF# FCT SB Acceptance of STM max speed and STM system speed/distance depending on mode: SB/L2
#TEST-VAL-SUB035-0367#REF# FCT SN Senden V_STMSYS/D_STMSYS beim Levelwechsel STMx-->STMy(Mode SN)
#TEST-VAL-SUB026-4482#REF# FCT SR SR/L1 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-8121#REF# FCT TR Acceptance of STM max speed and STM system speed/distance: TR
#TEST-VAL-SUB026-4483#REF# FCT UN UN/L0 - STM system speed and distance and STM max speed
#TEST-VAL-SUB026-4C99#REF# EET error expectation Acceptance of STM max speed and STM system speed/distance: PT/L2

#REQ-UNISIG-SUB026-3466:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
#REQ-UNISIG-SUB026-3331:01#REF#
acceptance "Level Transition Order" depending on the modes:

accepted: SB[2], PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT[1][5], SN
rejected: RV
exception[7] is realized separate  - see realization of this exception
#ANALYSE-VALUNISIG-4606#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4220#REF# FCT FS L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4C67#REF# FCT NL Stored data: Level transition order when mode changes to NL/L2
#TEST-VAL-SUB026-4C65#REF# FCT OS Stored data: Level transition order when mode changes to FS/L1, OS/L2
#TEST-VAL-SUB026-4329#REF# FCT PT[1][5] PT/L2 acceptence (Q_DIR evaluation) of Level Transition Order and Position Report Parameters
#TEST-VAL-SUB026-3874#REF# FCT SB[2] Acceptances of unconditionalEmergencyStop L1 (level transition to L2 announced)
#TEST-VAL-SUB026-5778#REF# FCT SH, SH[7] Evaluation of multiple level transition order in SH
#TEST-VAL-SUB026-4H43#REF# FCT SL Acceptance of P41 (Q_SLEEPSESSION=0) and P42 in SL
#TEST-VAL-SUB026-4452#REF# FCT SN acceptance NV, RV info in SN from BG without LTO
#TEST-VAL-SUB026-4574#REF# FCT SR, LS PR at level, standstill in LS, determine train speed and location in LS
#TEST-VAL-SUB026-4C70#REF# FCT TR Stored data: Level transition order when mode changes to TR/L2, PT/L1
#TEST-VAL-SUB026-4219#REF# FCT UN L0 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4490#REF# EET error expectation PT/L2 - acceptance of LTO from BG
#TEST-VAL-SUB026-5489#REF# EET error expectation PT/L2 - immediate level transition order from RBC rejected

#REQ-DESIGN-CR-0740:03#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
#REQ-UNISIG-SUB026-3465:01#REF#
acceptance "Conditional Level Transition Order" depending on the modes:

accepted: SB[2], PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, SN
rejected: PT, RV
Concerning exception [5] this means, that the CLTO is rejected ever in PT.

exception[7] is realized separate - see realization of this exception
#ANALYSE-VALUNISIG-4607#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5795#REF# FCT FS, OS, TR, SR, SN, UN Processing of conditional level transition order
#TEST-VAL-SUB026-4678#REF# FCT LS Limited Supervision mode speed limit
#TEST-VAL-SUB026-4216#REF# FCT SH, NL, SL, SB, SB[2], SR Accepting Conditional Level Transition Order depending on mode SH, NL, SL, SB, SR, SN

#REQ-DESIGN-CR-0349:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Session Management" depending on the modes:

accepted: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT[1], SN, RV
rejected: ---
exception[3] is realized separate  - see realization of this exception
#ANALYSE-VALUNISIG-4609#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4961#REF# FCT FS Check table sub26_4.8.4 Information->Radio Network Registration(Balise), Mode->FS, Level->2
#TEST-VAL-SUB026-4699#REF# FCT LS Acceptance Radio Network registration in LS
#TEST-VAL-SUB026-3860#REF# FCT NL NL - position report when passing single balise BG, no position report for BG with Q_LINK=0
#TEST-VAL-SUB026-4343#REF# FCT OS OBU establishes communication session and sends PR due to mode change OS->SR
#TEST-VAL-SUB026-5786#REF# FCT PS Evaluation of communication session establishment order in PS
#TEST-VAL-SUB026-5212#REF# FCT PT[1] Acceptance of P42, 57 and P79 in PT
#TEST-VAL-SUB026-4B51#REF# FCT RV RV/L2 - acceptance of Session Management, Initiation of Session and Acknowledgement of Session Termination
#TEST-VAL-SUB026-4969#REF# FCT SB Check table 4.8.4 Information->Radio Network Registration in OS,SB,NL
#TEST-VAL-SUB026-4889#REF# FCT SH Valid session management activity in SH is Termination
#TEST-VAL-SUB026-4007#REF# FCT SL Acceptance of P42 in SL
#TEST-VAL-SUB026-4D56#REF# FCT SN Acceptance of Radio Network registration: SN/STM
#TEST-VAL-SUB026-4529#REF# FCT SR initiation/termination of communication session in SR
#TEST-VAL-SUB026-4967#REF# FCT UN Check table 4.8.4 Information->Radio Network Registration, UN/L0
#TEST-VAL-SUB026-4H24#REF# EET error expectation Acceptance of P42 (order to establish communication session) in SH - P42 received together with P132

#REQ-DESIGN-CR-0445:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Radio Network registration" depending on the modes:

accepted: SB[2], PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT[1], SN, RV
rejected: ---
#ANALYSE-VALUNISIG-4610#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4961#REF# FCT FS Check table sub26_4.8.4 Information->Radio Network Registration(Balise), Mode->FS, Level->2
#TEST-VAL-SUB026-4699#REF# FCT LS Acceptance Radio Network registration in LS
#TEST-VAL-SUB026-4969#REF# FCT OS, SB[2], NL Check table 4.8.4 Information->Radio Network Registration in OS,SB,NL
#TEST-VAL-SUB026-5791#REF# FCT PS Evaluation of P45, system version and session termination order in PS
#TEST-VAL-SUB026-4966#REF# FCT SH, SL Acceptance of RadioNetwork Registeration in L1 of SH, SL modes
#TEST-VAL-SUB026-4D56#REF# FCT SN Acceptance of Radio Network registration: SN/STM
#TEST-VAL-SUB026-4970#REF# FCT SR Check table 4.8.3 Information->Radio Network Registration by Balise in L1/L2
#TEST-VAL-SUB026-4968#REF# FCT TR, PT[1], RV Acceptance of RadioNetwork Registration in modes TR, PT, RV
#TEST-VAL-SUB026-4967#REF# FCT UN Check table 4.8.4 Information->Radio Network Registration, UN/L0
#TEST-VAL-SUB026-4321#REF# EET error expectation PT/L1 acceptence of P72/76/41/42,45,46

#REQ-UNISIG-SUB026-010055#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "MA Request Parameters" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, UN, PT[1], SN
rejected: PS, SH, SL, NL, TR, RV
#ANALYSE-VALUNISIG-4611#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3690#REF# FCT FS New MA Request Parameters after MA request due to deletion of track description
#TEST-VAL-SUB026-4573#REF# FCT LS Movement Authority Request Parameters in LS
#TEST-VAL-SUB026-4522#REF# FCT OS Movement Authority Request Parameters in OS
#TEST-VAL-SUB026-5212#REF# FCT PT[1] Acceptance of P42, 57 and P79 in PT
#TEST-VAL-SUB026-4520#REF# FCT SB[2] Movement Authority Request Parameters in SB
#TEST-VAL-SUB026-4728#REF# FCT SN SN/STM - PR/MA parameter
#TEST-VAL-SUB026-5458#REF# FCT SR Acceptance of Movement Authority Request Parameters in SR
#TEST-VAL-SUB026-4895#REF# FCT UN Table 4.8.3 - MA request parameter (pkt 57) acceptance in L0

#REQ-DESIGN-CR-0021:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Position Report parameters" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, NL, UN, PT[1], SN, RV
rejected: PS, SH, SL, TR
#ANALYSE-VALUNISIG-4612#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4575#REF# FCT LS Position Report parameters when entering / in LS
#TEST-VAL-SUB026-3670#REF# FCT NL position report direction information in pkt0 - nominal BG orientation D_LRBG=0, pkt58 with T_CYCLOC=0
#TEST-VAL-SUB026-4A09#REF# FCT OS Report train position as requested by RBC on Mode OS
#TEST-VAL-SUB026-4329#REF# FCT PT[1] PT/L2 acceptence (Q_DIR evaluation) of Level Transition Order and Position Report Parameters
#TEST-VAL-SUB026-4363#REF# FCT RV PR at mode change to RV, PR at standstill in RV, determine train speed and location
#TEST-VAL-SUB026-4A07#REF# FCT SB[2], FS Report train position as requested by RBC at Mode SB ,FS ,TR and PT
#TEST-VAL-SUB026-4728#REF# FCT SN SN/STM - PR/MA parameter
#TEST-VAL-SUB026-3337#REF# FCT SR Position report, if packet 58 (location dependent) was received with reference LRBG_unknown
#TEST-VAL-SUB026-3668#REF# FCT UN Train Location Information - Assignment of coordinate system

#REQ-UNISIG-SUB026-010057#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "SR Authorisation + (optional) List of Balises in SR mode" depending on the modes:

accepted: SB[2][4], SR, PT[1][4]
rejected: PS, SH, FS, LS, OS, SL, NL, UN, TR, SN, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4613#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5765#REF# FCT PT[1][4] Acceptance of M2 with P63 in PT
#TEST-VAL-SUB026-3869#REF# FCT SB[2][4] Accepting List of Balises in SR Authority in SB
#TEST-VAL-SUB026-4330#REF# FCT SR List of Balises in SR Authority overwritten by new List of Balises in SR Authority

#REQ-UNISIG-SUB026-010056#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Stop if in SR mode" depending on the modes:

accepted: SR
rejected: SB, PS, SH, FS, LS, OS, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4614#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4223#REF# FCT SR BMM handling in SR/TR/PT in L1

#REQ-UNISIG-SUB026-010058#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "SR distance information from loop" depending on the modes:

accepted: SR
rejected: SB, PS, SH, FS, LS, OS, SL, NL, UN, TR, PT, SN, RV
exception [6] is realized through 5.8.3.8
#ANALYSE-VALUNISIG-4615#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7672#REF# FCT SR Non in-fill pkt 13 from LOOP

#REQ-DESIGN-CR-0351:02#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Temporary Speed Restriction" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, TR, PT[1][4], SN
rejected: PS, SH, SL, NL, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4616#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4D20#REF# FCT FS, OS TSR + Delete Revoked TSR; FS, OS
#TEST-VAL-SUB026-4551#REF# FCT LS TSR when entering LS, TSR in LS; OS->LS[70]
#TEST-VAL-SUB026-4464#REF# FCT SN SN/STM acceptance pkt65/141 - LTO L1 onboard
#TEST-VAL-SUB026-4D29#REF# FCT SR, SB[2][4] TSR: SR, NL, SB and Delete Revoked TSR: SR, SB
#TEST-VAL-SUB026-4D34#REF# FCT TR, PT[1] TSR: TR, PT and Delete Revoked TSR: TR, PT
#TEST-VAL-SUB026-4463#REF# FCT UN SN/STM acceptance pkt65/141 - no LTO onboard

#REQ-DESIGN-CR-0352:02#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Temporary Speed Restriction Revocation" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, TR, PT[1][4], SN
rejected: PS, SH, SL, NL, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4617#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4D20#REF# FCT FS, OS TSR + Delete Revoked TSR; FS, OS
#TEST-VAL-SUB026-4551#REF# FCT LS TSR when entering LS, TSR in LS; OS->LS[70]
#TEST-VAL-SUB026-4466#REF# FCT SN SN/STM acceptance pkt66 - LTO L2 onboard
#TEST-VAL-SUB026-4D29#REF# FCT SR, SB[2][4] TSR: SR, NL, SB and Delete Revoked TSR: SR, SB
#TEST-VAL-SUB026-4D34#REF# FCT TR, PT[1][4] TSR: TR, PT and Delete Revoked TSR: TR, PT
#TEST-VAL-SUB026-4D31#REF# FCT UN Delete Revoked TSR: UN
#TEST-VAL-SUB026-4884#REF# EET error expectation Check table 4.8.4 Information->Temporary Speed Restriction Revocation (TR)

#REQ-UNISIG-SUB026-010059#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Inhibition of revocable TSRs from balises in L2/3" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, UN, TR, PT[1], SN
rejected: PS, SH, SL, NL, RV
#ANALYSE-VALUNISIG-4618#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5818#REF# FCT FS Inhibition of revocable TSRs from balises in L2/3 deleted due to session termination
#TEST-VAL-SUB026-5826#REF# FCT LS Inhibition of revocable TSRs from balises in L2/3 in LS
#TEST-VAL-SUB026-5825#REF# FCT OS Inhibition of revocable TSRs from balises in L2/3 in OS
#TEST-VAL-SUB026-5828#REF# FCT PT[1] Inhibition of revocable TSRs from balises in L2/3 in PT
#TEST-VAL-SUB026-5830#REF# FCT SB[2][4] Inhibition of revocable TSRs from balises in L2/3 in SB
#TEST-VAL-SUB026-5832#REF# FCT SN Inhibition of revocable TSRs from balises in L2/3 in NTC
#TEST-VAL-SUB026-5829#REF# FCT SR Inhibition of revocable TSRs from balises in L2/3 in SR
#TEST-VAL-SUB026-5827#REF# FCT TR Inhibition of revocable TSRs from balises in L2/3 in TR
#TEST-VAL-SUB026-5831#REF# FCT UN Inhibition of revocable TSRs from balises in L2/3 in L0

#REQ-DESIGN-CR-0350:02#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Default gradient for TSR" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, TR, PT[1][4], SN
rejected: PS, SH, SL, NL, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4619#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3749#REF# FCT LS, UN default gradient for TSR handling UN/LS/L0/L1
#TEST-VAL-SUB026-4997#REF# FCT OS Check 4.8.4.2 --> Default gradient profile (FS, OS)
#TEST-VAL-SUB026-4B65#REF# FCT PT[1][4] PT/L2 - acceptance of Default Gradient for TSR
#TEST-VAL-SUB026-4D69#REF# FCT SB[2][4] Acceptance of information depending on mode: SB/L2 [P65, P141, M2]
#TEST-VAL-SUB026-4464#REF# FCT SN SN/STM acceptance pkt65/141 - LTO L1 onboard
#TEST-VAL-SUB026-3748#REF# FCT SR, FS default gradient for TSR handling SR/FS/L2
#TEST-VAL-SUB026-4B64#REF# FCT TR TR/L2 - acceptance of Default Gradient for TSR

#REQ-UNISIG-SUB026-010060#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Route Suitability Data" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4620#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5964#REF# FCT FS, SR FS, SR - Route Suitability Data processing
#TEST-VAL-SUB026-5966#REF# FCT LS LS - Route Suitability Data processing
#TEST-VAL-SUB026-5965#REF# FCT OS OS - Route Suitability Data processing
#TEST-VAL-SUB026-5968#REF# FCT PT[1][4] PT - Route Suitability Data processing
#TEST-VAL-SUB026-4D71#REF# FCT SB[2], SB[2][4] Acceptance of Route Suitability information: SB/L2
#TEST-VAL-SUB026-5970#REF# FCT SN RUS information when entering LS
#TEST-VAL-SUB026-5969#REF# FCT UN RUS information when entering FS/OS

#REQ-UNISIG-SUB026-010061#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
#REQ-UNISIG-SUB026-3321:01#REF#
acceptance "Adhesion Factor" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4621#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4664#REF# FCT FS, OS adhesion factor when entering FS, OS
#TEST-VAL-SUB026-4547#REF# FCT LS Adhesions factor from track side in LS, L1 FS->LS[72]
#TEST-VAL-SUB026-4D45#REF# FCT PT[1][4] Adhesion factor when mode changes to: TR, PT
#TEST-VAL-SUB026-4D44#REF# FCT SB[2][4] Adhesion factor when mode changes to: SB
#TEST-VAL-SUB026-4D51#REF# FCT SN Acceptance of Adhesion Factor data depending on mode: SN/STM (from RBC)
#TEST-VAL-SUB026-4D47#REF# FCT SR Adhesion factor when mode changes to: SR/L2, UN/L0
#TEST-VAL-SUB026-4666#REF# FCT UN adhesion factor when entering NL

#REQ-UNISIG-SUB026-3058:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Plain text information" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, NL, UN, TR, PT[1], SN, RV
rejected: PS, SH, SL
#ANALYSE-VALUNISIG-4622#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4377#REF# FCT FS text message FS->OS
#TEST-VAL-SUB026-4543#REF# FCT LS acceptance of text message LS/L2
#TEST-VAL-SUB026-4389#REF# FCT NL acknowledge plain text NL
#TEST-VAL-SUB026-4380#REF# FCT OS text message OS->TR
#TEST-VAL-SUB026-4375#REF# FCT PT[1] text message PT->SR
#TEST-VAL-SUB026-4383#REF# FCT RV text message RV->SB
#TEST-VAL-SUB026-4382#REF# FCT SB[2] text message SB
#TEST-VAL-SUB026-4437#REF# FCT SN, SR text messages from BG in SN/STM
#TEST-VAL-SUB026-4374#REF# FCT TR text message TR->PT
#TEST-VAL-SUB026-4B29#REF# FCT UN Acceptance of Plain and Fixed Text Messages (P72, P76) based on level and transmission media

#REQ-UNISIG-SUB026-3059:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Fixed text information" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, NL, UN, TR, PT[1], SN, RV
rejected: PS, SH, SL
#ANALYSE-VALUNISIG-4623#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4377#REF# FCT FS text message FS->OS
#TEST-VAL-SUB026-4543#REF# FCT LS acceptance of text message LS/L2
#TEST-VAL-SUB026-4389#REF# FCT NL acknowledge plain text NL
#TEST-VAL-SUB026-4380#REF# FCT OS text message OS->TR
#TEST-VAL-SUB026-4375#REF# FCT PT[1] text message PT->SR
#TEST-VAL-SUB026-4383#REF# FCT RV text message RV->SB
#TEST-VAL-SUB026-4382#REF# FCT SB[2] text message SB
#TEST-VAL-SUB026-4437#REF# FCT SN, SR text messages from BG in SN/STM
#TEST-VAL-SUB026-4374#REF# FCT TR text message TR->PT
#TEST-VAL-SUB026-4B29#REF# FCT UN Acceptance of Plain and Fixed Text Messages (P72, P76) based on level and transmission media

#REQ-UNISIG-SUB026-3060:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Geographical Position" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, NL, UN, TR, PT[1], SN
rejected: PS, SH, SL, RV
#ANALYSE-VALUNISIG-4624#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3603#REF# FCT FS Geographical Position Information from BG and Radio with same ref. NID_BG
#TEST-VAL-SUB026-4546#REF# FCT LS GeoPos in LS/L2; L2 FS->LS[72]
#TEST-VAL-SUB026-4B66#REF# FCT NL, TR Acceptance of GeoPos information depending on modes (NL, TR)
#TEST-VAL-SUB026-3654#REF# FCT OS 100km geographical distance calculation
#TEST-VAL-SUB026-5212#REF# FCT PT[1] Acceptance of P42, 57 and P79 in PT
#TEST-VAL-SUB026-3878#REF# FCT SB[2] Effect of closing desk during SoM L1 on GeographicalPosition
#TEST-VAL-SUB026-4460#REF# FCT SN SN/STM acceptance pkt79 GeoPos - LTO L1 on board
#TEST-VAL-SUB026-3653#REF# FCT SR Once a track kilometre reference is no longer applicable, it is deleted (new track kilometer ref.)
#TEST-VAL-SUB026-3652#REF# FCT UN Once a track kilometre reference is no longer applicable, it is deleted (No more geographical position calculation) + lnk

#REQ-UNISIG-SUB026-010062:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "RBC Transition Order" depending on the modes:

accepted: SB[2][4], PS[8], SH[8], FS, LS, SR, OS, SL, NL, TR, PT[1][4]
rejected: UN, SN, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4625#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4A76#REF# FCT FS Manage RBC Handover; FS - Conditional Emergency Stop within RBC transition buffer
#TEST-VAL-SUB026-4B04#REF# FCT LS Manage RBC Handover; LS - Conditional Emergency Stop within RBC transition buffer
#TEST-VAL-SUB026-4A86#REF# FCT NL Manage RBC Handover; NL
#TEST-VAL-SUB026-4A74#REF# FCT OS Manage RBC Handover; OS
#TEST-VAL-SUB026-5787#REF# FCT PS[8] Evaluation of RBC transition order in PS
#TEST-VAL-SUB026-3462#REF# FCT PT[1][4] RBC transition order stored in PT and executed when entering FS
#TEST-VAL-SUB026-4A82#REF# FCT SB[2][4] RBC transition order stored in SB and evaluated when entering FS
#TEST-VAL-SUB026-5785#REF# FCT SH[8] Evaluation of RBC transition order in SH
#TEST-VAL-SUB026-4A89#REF# FCT SL (Q_SLEEPSESSION = 0) Manage RBC Handover; SL - Q_SLEEPSESSION = 0
#TEST-VAL-SUB026-4A84#REF# FCT SL (Q_SLEEPSESSION = 1) Manage RBC Handover; SL
#TEST-VAL-SUB026-4A78#REF# FCT SR Manage RBC Handover; SR
#TEST-VAL-SUB026-4A80#REF# FCT TR Manage RBC Handover; TR

#REQ-UNISIG-SUB026-010064#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Danger for SH information" depending on the modes:

accepted: SH
rejected: SB, PS, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4626#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4C59#REF# FCT SH Stored data: List of balises for SH area when mode changes to TR/L1, PT/L1

#REQ-UNISIG-SUB026-010065#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Stop Shunting on desk opening" depending on the modes:

accepted: PS
rejected: SB, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
The information is generally ignored
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-UNISIG-SUB026-3556:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Radio Infill Area Information" depending on the modes:

accepted: FS, LS, SR, OS
rejected: SB, PS, SH, SL, NL, UN, TR, PT, SN, RV

#REQ-UNISIG-SUB026-010066#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Session Management with neighbouring RIU" depending on the modes:

accepted: FS, LS, SR, OS
rejected: SB, PS, SH, SL, NL, UN, TR, PT, SN, RV

#REQ-UNISIG-SUB026-3555:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "EOLM Information" depending on the modes:

accepted: SH, FS, LS, SR, OS, SL, NL, UN, TR, SN, RV
rejected: SB, PS, PT
#ANALYSE-VALUNISIG-4630#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3105#REF# FCT FS Acceptance of the loop information after passing the EOLM
#TEST-VAL-SUB026-4697#REF# FCT LS LS acceptance of EOL information
#TEST-VAL-SUB026-4B69#REF# FCT NL NL/L1 acceptance of EOLM information
#TEST-VAL-SUB026-4B68#REF# FCT OS OS/L1: acceptance of EOLM information
#TEST-VAL-SUB026-4B72#REF# FCT RV RV/L1 acceptance of EOLM information
#TEST-VAL-SUB026-4B67#REF# FCT SH SH/L1 acceptance of EOLM information
#TEST-VAL-SUB026-4B70#REF# FCT SL SL/L1 acceptance of EOLM information
#TEST-VAL-SUB026-4469#REF# FCT SN SN/STM acceptance EOL information - LTO L1 onboard
#TEST-VAL-SUB026-4470#REF# FCT SR L1 SR->FS EOL information
#TEST-VAL-SUB026-4B71#REF# FCT TR TR/L1 acceptance of EOLM information
#TEST-VAL-SUB026-5705#REF# FCT UN UN/L0 acceptance EOL information - LTO L1 onboard

#REQ-UNISIG-SUB026-010067#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Assignment of Co-ordinate system" depending on the modes:

accepted: SB[2], SR, NL, UN, PT[1], SN
rejected: PS, SH, FS, LS, OS, SL, TR, RV
#ANALYSE-VALUNISIG-4631#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4960#REF# FCT NL, SB[2], UN Assignment of Co-ordinate system is R in SL, but A in NL, UN, SB
#TEST-VAL-SUB026-4958#REF# FCT PT[1] Assignment of Co-ordinate system is R in FS, TR; but A in PT
#TEST-VAL-SUB026-4511#REF# FCT SN SN/STM - acceptance of message 45: Assignment of coordinate system
#TEST-VAL-SUB026-4957#REF# FCT SR Assignment of Co-ordinate system is A in SR; but R in SH

#REQ-UNISIG-SUB026-010068#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Infill Location reference" depending on the modes:

accepted: FS, LS
rejected: SB, PS, SH, SR, OS, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4632#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3655#REF# FCT FS In-fill MA without Mode Profile deletes current Mode Profile starting with the in-fill reference location
#TEST-VAL-SUB026-3014#REF# FCT LS In-fill MA without MP overrides current Mode Profile LS starting with the in-fill reference location

#REQ-UNISIG-SUB026-010069#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Track Conditions excluding sound horn, non stopping areas, tunnel stopping areas and big metal masses" depending on the
modes:

accepted: SB[2][4], FS, LS, SR, OS, NL, UN, TR, PT[1][4], SN
rejected: PS, SH, SL, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
realised by: #REQ-UNISIG-SUB026-010469#REF#

#REQ-UNISIG-SUB026-010469#REF# table.4.8.4 #REQ-UNISIG-SUB026-010069#REF#
#REQ-UNISIG-SUB026-010070#REF#
#ANA-UNISIG-AccInformation-0006#REF#
acceptance "Track Conditions excluding big metal masses" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, NL, UN, TR, PT[1][4], SN
rejected: PS, SH, SL, RV
UNISIG clarification:
exception[4] must be minded in mode PT
TEST APPROACH:
All packets used to send track conditions excluding BMM by trackside are considered.
P69 is omitted, as TC 'Station Platforms' is not part of R8.0
#ANALYSE-VALUNISIG-4633#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4972#REF# FCT P39 - FS, OS, NL Check table 4.5.2, 4.8.4, 4.10 TC Change of traction power (FS/OS/NL)
#TEST-VAL-SUB026-4E08#REF# FCT P39 - LS TC Change of Traction Power in LS/L2
#TEST-VAL-SUB026-4974#REF# FCT P39 - PT[1][4] Check table 4.5.2, 4.8.4, 4.10 Information->TC Change of traction power (TR/PT)
#TEST-VAL-SUB026-7756#REF# FCT P39 - SB[2][4] TC change of traction power retained in SB and manged after transition to FS
#TEST-VAL-SUB026-5572#REF# FCT P39 - SR TC excl. BMM and sound horn, tunnel and non-stop areas retained in SR, but only processed after transition to NL
#TEST-VAL-SUB026-7732#REF# FCT P40 - FS Acceptance of TC 'Change of allowed power consumption' from BG in L2
#TEST-VAL-SUB026-7730#REF# FCT P40 - LS Acceptance of TC 'Allowed power consumption' - RBC/L1
#TEST-VAL-SUB026-7731#REF# FCT P40 - OS, NL Acceptance of TC 'Allowed power consumption' - RBC/L2
#TEST-VAL-SUB026-7739#REF# FCT P40 - SB[2][4] Acceptance of TC 'Allowed power consumption' - SB
#TEST-VAL-SUB026-7737#REF# FCT P40 - SN Acceptance of TC 'Change of allowed power consumption' - SN/NTC
#TEST-VAL-SUB026-7729#REF# FCT P40 - SR Acceptance of TC 'Change of allowed power consumption' from BG in L1
#TEST-VAL-SUB026-7742#REF# FCT P40 - TR, PT[1][4] Acceptance of TC 'Allowed power consumption' - TR, PT
#TEST-VAL-SUB026-7728#REF# FCT P40 - UN Acceptance of 'Track Conditions' (P40) from BG in L0
#TEST-VAL-SUB026-4220#REF# FCT P68 - FS L2 information from BG stored onboard if an order to switch to L1 at a further location has been received
#TEST-VAL-SUB026-4583#REF# FCT P68 - LS TC Excluding Big Metal Masses (P68) FS/LS
#TEST-VAL-SUB026-4B74#REF# FCT P68 - OS, NL acceptance of track conditions excluding BMM (P68) in modes OS, NL
#TEST-VAL-SUB026-4E14#REF# FCT P68 - SB[2][4] Acceptance of track condition (P68): SB
#TEST-VAL-SUB026-4310#REF# FCT P68 - SR, PT[1][4] TC Excluding Big Metal Masses PT/SR/FS
#TEST-VAL-SUB026-4C92#REF# FCT P68, P39 - SN Acceptance of "Track Conditions excluding big metal masses" (P39, P68): SN/STM (from RBC)
#TEST-VAL-SUB026-4B75#REF# FCT P68, P39 - TR Acceptance of track conditions (P68, P39) in mode TR
#TEST-VAL-SUB026-4B31#REF# FCT P68, P39 - UN acceptance of 'Track Conditions excluding big metal masses' (P68, P39) from BG/L0[2]

#REQ-UNISIG-SUB026-010070#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Track Conditions sound horn, non stopping areas, tunnel stopping areas" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
realised by: #REQ-UNISIG-SUB026-010469#REF#

#REQ-UNISIG-SUB026-010071#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Track Condition big metal masses" depending on the modes:

accepted: SB[2][4], PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT[1][4], SN
rejected: RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4635#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4576#REF# FCT LS BMM handling in FS/LS
#TEST-VAL-SUB026-4227#REF# FCT NL BMM handling in SB/NL
#TEST-VAL-SUB026-4222#REF# FCT OS, FS BMM handling in FS/OS
#TEST-VAL-SUB026-5953#REF# FCT PS Evaluation of P67 in PS
#TEST-VAL-SUB026-5915#REF# FCT PT[1][4] Acceptance of P67 in PT/L2
#TEST-VAL-SUB026-4D70#REF# FCT SB[2][4] Acceptance of information depending on mode: SB/L1 [P67]
#TEST-VAL-SUB026-4225#REF# FCT SH BMM handling in SB/SH
#TEST-VAL-SUB026-4228#REF# FCT SL BMM handling in SB/SL
#TEST-VAL-SUB026-4223#REF# FCT SR, TR BMM handling in SR/TR/PT in L1
#TEST-VAL-SUB026-4224#REF# FCT UN, SN BMM handling in UN/SN

#REQ-UNISIG-SUB026-010072#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Location Identity (NID_C + NID_BG)" depending on the modes:

accepted: SB[2], PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
rejected: ---
see realization - a check is'nt necessary
--- FINALISED ---
The Location Identity isn't a separate information. NID_C + NID_BG are evaluated togehter with the balise consistency checks and the
requirements for location data (see chapter 3.6).
#ANALYSE-VALUNISIG-4528#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010073#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Recognition of exit from Trip mode" depending on the modes:

accepted: PT
rejected: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, PT, SN, RV
#ANALYSE-VALUNISIG-4637#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4212#REF# FCT PT unconditional emergency stop message TR, PT - MA accepted after emergency revoked

#REQ-DESIGN-CR-0075:03#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "acceptance "Acknowledgement of Train Data" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, UN, TR, PT, SN, RV
rejected: PS, SH, SL, NL
#ANALYSE-VALUNISIG-4638#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5769#REF# FCT LS, RV Acceptance of M8 depending on mode LS, RV
#TEST-VAL-SUB026-4890#REF# FCT PT Check table 4.8.4 -> Acknowledgement of Train Data (PT)
#TEST-VAL-SUB026-3218#REF# FCT SB[2] Input RBC contact data during SoM
#TEST-VAL-SUB026-4487#REF# FCT SN SN/STM - acceptance msg. 8, 32, 39 - train location when entering SN/STM
#TEST-VAL-SUB026-5713#REF# FCT SR Acceptance of SR Authorisation + List of Balises in SR mode in L3
#TEST-VAL-SUB026-4892#REF# FCT TR Check table 4.8.4 -> Acknowledgement of Train Data (TR)
#TEST-VAL-SUB026-4B30#REF# FCT UN, FS, OS Acceptance of Acknowledgement of Train Data (Message 8) depending on level

#REQ-UNISIG-SUB026-3496:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Co-operative shortening of MA + (optional) Mode Profile + (optional) List of Balises for SH area" depending on the modes:

accepted: FS, LS, OS
rejected: SB, PS, SH, SR, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4639#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3098#REF# FCT FS Cooperative shortenting of MA
#TEST-VAL-SUB026-4693#REF# FCT LS Request To Shorten MA in LS
#TEST-VAL-SUB026-4D02#REF# FCT OS Handle Co-operative MA revocation; OS

#REQ-DESIGN-CR-0040:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Unconditional Emergency Stop" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, UN, SN
rejected: PS, SH, SL, NL, TR, PT, RV
#ANALYSE-VALUNISIG-4640#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4A51#REF# FCT FS Unconditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-4561#REF# FCT LS mode change LS->TR[20]
#TEST-VAL-SUB026-4A53#REF# FCT OS Unconditional Emergency Stop; UN, OS
#TEST-VAL-SUB026-3874#REF# FCT SB[2] Acceptances of unconditionalEmergencyStop L1 (level transition to L2 announced)
#TEST-VAL-SUB026-4C88#REF# FCT SN Manage Unconditional Emergency Stop: SN/STM
#TEST-VAL-SUB026-4282#REF# FCT SR unconditional emergency stop message deleted when entering SR
#TEST-VAL-SUB026-4333#REF# FCT UN processing of Unconditional Emergency Stop from level transition buffer

#REQ-UNISIG-SUB026-010074#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Conditional Emergency Stop" depending on the modes:

accepted: FS, LS, OS, UN, SN
rejected: SB, PS, SH, SR, SL, NL, TR, PT, RV
#ANALYSE-VALUNISIG-4641#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4336#REF# EET CFX00038109 processing of Conditional Emergency Stop from level transition buffer (stop location behind EoA)
#TEST-VAL-SUB026-4696#REF# FCT FS Conditional Emergency Stop and Revocation of Emergency Stop within level transition buffer L1->L2
#TEST-VAL-SUB026-4F14#REF# FCT LS Manage Conditional Emergency Stop; LS
#TEST-VAL-SUB026-4901#REF# FCT OS Stored Conditional Emergency Stop; FS
#TEST-VAL-SUB026-4A98#REF# FCT SN Revocation of Conditional Emergency Stop; SN/STM
#TEST-VAL-SUB026-4334#REF# FCT UN processing of Conditional Emergency Stop from level transition buffer

#REQ-UNISIG-SUB026-3410:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Revocation of Emergency Stop (Conditional or Unconditional)" depending on the modes:

accepted: FS, LS, OS, PT[1]
rejected: SB, PS, SH, SR, SL, NL, UN, TR, SN, RV
TEST APPROACH:
The  reception of an Unconditional emergency stop in modes FS, LS or OS leads to an immediate transition to mode TR.
Therefore, regarding the evaluation of UCES revocation, only mode PT is verified.
The following aspects have been identified:
1) Revocation of Conditional emergency stop
1.1) FS
1.2) LS
1.3) OS
1.4) PT
2) Revocation of Unconditional emergency stop
2.1) PT
#ANALYSE-VALUNISIG-4642#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4696#REF# FCT 1.1 Conditional Emergency Stop and Revocation of Emergency Stop within level transition buffer L1->L2
#TEST-VAL-SUB026-5770#REF# FCT 1.2 Revocation of Emergency Stop in LS
#TEST-VAL-SUB026-4A68#REF# FCT 1.3 Conditional Emergency Stop Revocation; FS, OS
#TEST-VAL-SUB026-3B80#REF# FCT 1.4 Conditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-4A51#REF# FCT 2.1 Unconditional Emergency Stop ; FS->TR->PT->FS
#TEST-VAL-SUB026-4334#REF# EET CFX00038109 processing of Conditional Emergency Stop from level transition buffer
#TEST-VAL-SUB026-4333#REF# EET error expectation processing of Unconditional Emergency Stop from level transition buffer
#TEST-VAL-SUB026-4A98#REF# EET error expectation Revocation of Conditional Emergency Stop; SN/STM

#REQ-UNISIG-SUB026-010075#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "SH refused" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, PT[1]
rejected: PS, SH, SL, NL, UN, TR, SN, RV
#ANALYSE-VALUNISIG-4643#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4578#REF# FCT FS, OS Reception of SH Refused FS/OS
#TEST-VAL-SUB026-5012#REF# FCT PT[1] Shunting initiated by driver (L2, PT) rejected by RBC
#TEST-VAL-SUB026-4B62#REF# FCT SB[2] SB/L2 - Acceptance of SH Refused; related indication on DMI
#TEST-VAL-SUB026-4579#REF# FCT SR, LS Reception of SH Refused SR/LS

#REQ-UNISIG-SUB026-010076#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "SH authorised + (optional) List of Balises for SH area" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, PT[1]
rejected: PS, SH, SL, NL, UN, TR, SN, RV
#ANALYSE-VALUNISIG-4644#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4H08#REF# FCT FS Cyclically MA request stopped when entering SH
#TEST-VAL-SUB026-4565#REF# FCT LS mode change LS->SH[6]
#TEST-VAL-SUB026-4616#REF# FCT OS OS->SH[6]
#TEST-VAL-SUB026-5543#REF# FCT PT[1] PT->SH[6] - degraded situation RBC does not order termination of connection
#TEST-VAL-SUB026-4B62#REF# FCT SB[2] SB/L2 - Acceptance of SH Refused; related indication on DMI
#TEST-VAL-SUB026-5002#REF# FCT SR SR->SH

#REQ-UNISIG-SUB026-010077#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Trackside constituent System version" depending on the modes:

accepted: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
rejected: ---
Rel. 8.0.: 
this information conforms Configuration Determination (Msg. 32)
#ANALYSE-VALUNISIG-4645#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3018#REF# FCT FS Connection establishment System Version supported/not supported
#TEST-VAL-SUB026-4B59#REF# FCT LS, RV Acceptance of Trackside constituent version depending on modes
#TEST-VAL-SUB026-4B61#REF# FCT NL NL/L1 - Acceptance of Trackside constituent version
#TEST-VAL-SUB026-5791#REF# FCT PS Evaluation of P45, system version and session termination order in PS
#TEST-VAL-SUB026-4B63#REF# FCT PT Acceptance of Trackside constituent version in mode PT
#TEST-VAL-SUB026-5426#REF# FCT SB SoM stored level L2, valid RBC data and location, to NL/L2 (E10) - session not open
#TEST-VAL-SUB026-4B58#REF# FCT SN, SL Acceptance of Trackside constituent version depending on modes
#TEST-VAL-SUB026-4B57#REF# FCT SR, OS, SH Acceptance of Trackside constituent version depending on modes
#TEST-VAL-SUB026-4B60#REF# FCT UN, TR Acceptance of Trackside constituent version depending on modes
#TEST-VAL-SUB026-4829#REF# EET error expectation Acceptance of message 32 from accepting RBC

#REQ-UNISIG-SUB026-010078#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "System Version order" depending on the modes:

accepted: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
rejected: ---
#ANALYSE-VALUNISIG-4646#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7097#REF# FCT FS Determining the operated system version, ignored BG
#TEST-VAL-SUB026-7099#REF# FCT LS Evaluation of balise message according to received system version order
#TEST-VAL-SUB026-7106#REF# FCT NL Version number X transmitted by a non-RBC trackside constituent ot supported by OBU
#TEST-VAL-SUB026-7120#REF# FCT OS, TR, PT Evaluation of System Version order in OS, TR, PT
#TEST-VAL-SUB026-7116#REF# FCT PS Determining the operated system version, in relation to non-RBC trackside constituents
#TEST-VAL-SUB026-7121#REF# FCT SB, RV, SL, SH Evaluation of System Version order in SB, RV, SL, SH
#TEST-VAL-SUB026-7096#REF# FCT SN Determining the operated system version of BG with duplicated balise
#TEST-VAL-SUB026-7093#REF# FCT SR Determining the operated system version, in relation to non-RBC trackside constituents
#TEST-VAL-SUB026-7095#REF# FCT UN Determining the operated system version of erroneous BG

#REQ-UNISIG-SUB026-010079#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Track Ahead Free Request" depending on the modes:

accepted: SB[2], LS, SR, OS, PT[1]
rejected: PS, SH, FS, SL, NL, UN, TR, SN, RV
#ANALYSE-VALUNISIG-4647#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4D61#REF# FCT LS Manage Track Ahead Free request: LS
#TEST-VAL-SUB026-4D40#REF# FCT PT[1] Manage Track Ahead Free request: TR, PT
#TEST-VAL-SUB026-4D37#REF# FCT SB Manage Track Ahead Free request: SB, NL
#TEST-VAL-SUB026-4D35#REF# FCT SR, OS Manage Track Ahead Free request: SR, OS

#REQ-UNISIG-SUB026-010080#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Train Running Number" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, NL, TR, PT, RV
rejected: PS, SH, SL, UN, SN
#ANALYSE-VALUNISIG-4648#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3766#REF# FCT FS Train Running Number from different sources
#TEST-VAL-SUB026-4B56#REF# FCT SR, OS, LS, TR, PT, RV, SB[2], NL Acceptance of Train Running Nr. depending on mode

#REQ-UNISIG-SUB026-010081#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Initiation of session" depending on the modes:

accepted: SB, FS, LS, SR, OS, SL, NL, TR, PT, RV
rejected: PS, SH, UN, SN
#ANALYSE-VALUNISIG-4649#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3775#REF# FCT FS T_NVCONTACT supervision M_NVCONTAC=1
#TEST-VAL-SUB026-4B52#REF# FCT LS, OS Acceptance of Acknowledgement of Session Termination and Initiation of Session depending on modes
#TEST-VAL-SUB026-4B51#REF# FCT RV RV/L2 - acceptance of Session Management, Initiation of Session and Acknowledgement of Session Termination
#TEST-VAL-SUB026-4B53#REF# FCT SB, NL Acceptance of Acknowledgement of Session Termination and Initiation of Session depending on modes
#TEST-VAL-SUB026-4B73#REF# FCT SL SL/L2: Acceptance of Acknowledgement of Session Termination and Initiation of Session
#TEST-VAL-SUB026-4B54#REF# FCT SR SR/L2 - Acceptance of Acknowledgement of Session Termination and Initiation of Session
#TEST-VAL-SUB026-4B55#REF# FCT TR, PT Acceptance of Acknowledgement of Session Termination and Initiation of Session depending on modes

#REQ-UNISIG-SUB026-010082#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Acknowledgement of session termination" depending on the modes:

accepted: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
rejected: ---
#ANALYSE-VALUNISIG-4650#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3775#REF# FCT FS T_NVCONTACT supervision M_NVCONTAC=1
#TEST-VAL-SUB026-4B52#REF# FCT LS, OS Acceptance of Acknowledgement of Session Termination and Initiation of Session depending on modes
#TEST-VAL-SUB026-5791#REF# FCT PS Evaluation of P45, system version and session termination order in PS
#TEST-VAL-SUB026-4B51#REF# FCT RV RV/L2 - acceptance of Session Management, Initiation of Session and Acknowledgement of Session Termination
#TEST-VAL-SUB026-4B53#REF# FCT SB, NL Acceptance of Acknowledgement of Session Termination and Initiation of Session depending on modes
#TEST-VAL-SUB026-5814#REF# FCT SH Acceptance of NV in PS
#TEST-VAL-SUB026-4B73#REF# FCT SL SL/L2: Acceptance of Acknowledgement of Session Termination and Initiation of Session
#TEST-VAL-SUB026-4487#REF# FCT SN SN/STM - acceptance msg. 8, 32, 39 - train location when entering SN/STM
#TEST-VAL-SUB026-4B54#REF# FCT SR SR/L2 - Acceptance of Acknowledgement of Session Termination and Initiation of Session
#TEST-VAL-SUB026-4B55#REF# FCT TR, PT Acceptance of Acknowledgement of Session Termination and Initiation of Session depending on modes
#TEST-VAL-SUB026-5712#REF# FCT UN Session termination in L0

#REQ-UNISIG-SUB026-010083#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Train Rejected" depending on the modes:

accepted: SB[2]
rejected: PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4651#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5527#REF# FCT SB[2] SoM - deletion of stored position data on reception of Train Rejected

#REQ-UNISIG-SUB026-010084#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Train Accepted" depending on the modes:

accepted: SB[2]
rejected: PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4652#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5529#REF# FCT SB[2] Variable Q_STATUS is Invalid in PositionReport (RBC accepts)

#REQ-UNISIG-SUB026-010085#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "SoM Position report Conformed by RBC" depending on the modes:

accepted: SB[2]
rejected: PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
#ANALYSE-VALUNISIG-4653#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4208#REF# FCT SB[2] SoM stored train location confirmed by RBC

#REQ-UNISIG-SUB026-010086#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Reversing Area Information" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN, RV
rejected: PS, SH, SL, NL, TR
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4654#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3599#REF# FCT FS New Reversing supervision information replace the one already available on-board
#TEST-VAL-SUB026-4562#REF# FCT LS mode change LS->RV[59]
#TEST-VAL-SUB026-4C24#REF# FCT OS Acceptance of Reversing Area Information and Reversing Supervision Information: OS/L2
#TEST-VAL-SUB026-4C29#REF# FCT PT[1][4] Acceptance of Reversing Area Information and Reversing Supervision Information: PT/L2
#TEST-VAL-SUB026-5730#REF# FCT RV Acceptance of Reversing area information in RV
#TEST-VAL-SUB026-4C26#REF# FCT SB Stored data: Reversing Area Information and Reversing Supervision Information when mode changes: SB/L2, FS/L2
#TEST-VAL-SUB026-4446#REF# FCT SN acceptance NV, RV info in SN from RBC with LTO
#TEST-VAL-SUB026-4C22#REF# FCT SR Stored data: Reversing Area Information and Reversing Supervision Information SR/L2, FS/L2
#TEST-VAL-SUB026-4C27#REF# FCT UN Stored data: Reversing Area Information and Reversing Supervision Information when changing to UN/L0, FS/L1, RV/L1

#REQ-UNISIG-SUB026-010087#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Reversing Supervision Information" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN, RV
rejected: PS, SH, SL, NL, TR
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4655#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3599#REF# FCT FS New Reversing supervision information replace the one already available on-board
#TEST-VAL-SUB026-4562#REF# FCT LS mode change LS->RV[59]
#TEST-VAL-SUB026-4C24#REF# FCT OS Acceptance of Reversing Area Information and Reversing Supervision Information: OS/L2
#TEST-VAL-SUB026-4C29#REF# FCT PT[1][4] Acceptance of Reversing Area Information and Reversing Supervision Information: PT/L2
#TEST-VAL-SUB026-5742#REF# FCT RV Reception of new Reversing Supervision Information in RV
#TEST-VAL-SUB026-4C26#REF# FCT SB Stored data: Reversing Area Information and Reversing Supervision Information when mode changes: SB/L2, FS/L2
#TEST-VAL-SUB026-4446#REF# FCT SN acceptance NV, RV info in SN from RBC with LTO
#TEST-VAL-SUB026-4C22#REF# FCT SR Stored data: Reversing Area Information and Reversing Supervision Information SR/L2, FS/L2
#TEST-VAL-SUB026-4C27#REF# FCT UN Stored data: Reversing Area Information and Reversing Supervision Information when changing to UN/L0, FS/L1, RV/L1

#REQ-UNISIG-SUB026-010088#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Default Balise/Loop/RIU Information" depending on the modes:

accepted: SB[2], PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
rejected: ---
#ANALYSE-VALUNISIG-4656#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4692#REF# FCT FS, OS, SR, SH acceptance P254 in FS/OS/SR/SH
#TEST-VAL-SUB026-4691#REF# FCT LS LS System Configuration Management, Default Balise Information, OBU supports M_VERSION = 0x20
#TEST-VAL-SUB026-4534#REF# FCT NL NL/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-5790#REF# FCT PS Evaluation of P254 in PS
#TEST-VAL-SUB026-4538#REF# FCT PT PT/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4535#REF# FCT RV RV/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4536#REF# FCT SB[2] SB/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-5789#REF# FCT SL Evaluation of P254 in SL
#TEST-VAL-SUB026-4736#REF# FCT SN SN/STM - PR at every passage of an LRBG compliant balise, System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4537#REF# FCT TR TR/L2 - System Configuration Management, Default Balise Information
#TEST-VAL-SUB026-4B34#REF# FCT UN acceptance of 'Default Balise/Loop/RIU information' (P254) depending on level

#REQ-DESIGN-CR-0524:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Track Ahead Free up to level 2/3 transition location" depending on the modes:

accepted: SB[2], FS, LS, SR, OS, UN, TR, PT, SN
rejected: PS, SH, SL, NL, RV
#ANALYSE-VALUNISIG-4657#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4954#REF# FCT FS, UN Track Ahead Free up to level 2/3 transition location (pkt 90)
#TEST-VAL-SUB026-4B00#REF# FCT LS Check table 4.5.2/4.8.4 Information->Track ahead free up to leve l2/3 transition location, Mode LS
#TEST-VAL-SUB026-4998#REF# FCT SB[2], SR, OS Check table 4.5.2/4.8.4 Information->Track ahead free upto level2/3 transition location, Mode-> SB/SR/OS
#TEST-VAL-SUB026-4270#REF# FCT SN Track Ahead Free up to level 2/3 transition location (pkt 90) STM
#TEST-VAL-SUB026-4999#REF# FCT TR, PT Check table 4.5.2/4.8.4 Information->Track ahead free upto level2/3 transition location, Mode-> TR/PT

#REQ-UNISIG-SUB026-010089#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Permitted Braking Distance Information" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
#ANALYSE-VALUNISIG-4658#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4B95#REF# FCT FS test variable D_PBD
#TEST-VAL-SUB026-4B96#REF# FCT LS test variable D_PBDSR
#TEST-VAL-SUB026-4B97#REF# FCT OS test variable G_PBDSR
#TEST-VAL-SUB026-3A71#REF# FCT PT[1][4] PT/L2: acceptance and supervision of PBD Information from RBC
#TEST-VAL-SUB026-3A70#REF# FCT SB[2][4] SB/L2: acceptance of PBD Information from RBC
#TEST-VAL-SUB026-3A68#REF# FCT SN PBD Information - accepted in SN/NTC (from BG), supervised when in OS/L1
#TEST-VAL-SUB026-3A69#REF# FCT SR SR/L1 - Acceptance of PBD Information from BG
#TEST-VAL-SUB026-3A65#REF# FCT UN PBD Information accepted in mode UN via RBC/L0[2] and supervised in mode FS

#REQ-UNISIG-SUB026-010090#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Level Crossing information" depending on the modes:

accepted: SB[2][4], FS, LS, SR, OS, UN, PT[1][4], SN
rejected: PS, SH, SL, NL, TR, RV
UNISIG clarification:
exception[4] must be minded in mode PT also
TEST APPROACH:
The transition from modes PS, SH, SL, NL and RV is possible through modes where Level Crossing 
information is deleted.
Hence the verification for modes PS, SH, SL, NL and RV is omitted.
#ANALYSE-VALUNISIG-4659#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7646#REF# FCT FS LX not protected message displayed on the DMI
#TEST-VAL-SUB026-7651#REF# FCT LS Acceptance of Level Crossing Information in L2
#TEST-VAL-SUB026-7652#REF# FCT OS Acceptance of Level Crossing Information in L3
#TEST-VAL-SUB026-7653#REF# FCT PT[1][4] Acceptance of Level Crossing Information in PT
#TEST-VAL-SUB026-7647#REF# FCT SB[2][4] Level crossing information deleted when mode changes to SB and when desk is closed during SoM
#TEST-VAL-SUB026-7649#REF# FCT SN Acceptance of Level Crossing Information in NTC
#TEST-VAL-SUB026-7650#REF# FCT SR Acceptance of Level Crossing Information in L1
#TEST-VAL-SUB026-7648#REF# FCT UN Acceptance of Level Crossing Information in L0

#REQ-UNISIG-SUB026-010054#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Virtual Balise Cover order" depending on the modes:

accepted: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
rejected: ---
VBC function is not realized

=> P6 is to be ignore

#REQ-UNISIG-SUB026-010440#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
acceptance "Data to be used by applications outside ERTMS/ETCS" depending on the modes:

accepted: SB, PS, SH, FS, LS, SR, OS, SL, NL, UN, TR, PT, SN, RV
rejected: ---
TEST APPROACH:
There is no mode dependency defined for forwarding P44 information. Only one example test case is provided here. 
#ANALYSE-VALUNISIG-5264#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7025#REF# FCT basic function Evaluation of P44 received with not accepted SH Authorized

#REQ-UNISIG-SUB026-1206#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [1]:	for level 2/3 : only if following the reception of the information “Recognition of Exit from TR mode” with a more recent time
stamp. For level 1: rejected
#ANALYSE-VALUNISIG-4660#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4319#REF# FCT BG/L1 PT/L1 acceptence of MA, MP, LTO
#TEST-VAL-SUB026-5726#REF# FCT BG/L2 Accepted information depending on mode exception [1] valid for BG messages in PT/L2
#TEST-VAL-SUB026-5725#REF# FCT RBC/L1 , CFX00124224 Accepted information depending on mode exception [1] valid for RBC messages in PT/L1
#TEST-VAL-SUB026-5724#REF# FCT RBC/L2 Accepted information depending on mode exception [1] valid for RBC messages in PT/L2
#TEST-VAL-SUB026-4161#REF# EET error expectation Reading P12 with TRIP order in PT

#REQ-DESIGN-CR-0739#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [2]: only if a cab is active
#ANALYSE-VALUNISIG-4661#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5816#REF# FCT basic function Evaluation of 4.8.4 condition 2

#REQ-DESIGN-CR-0353:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [3]: "for order to establish a communication session: RBC ID/phone number is stored without establishing the communication
session"
exception [3] is realized through 4.8.1.5.1 and 4.4.20.1.12
realised by: #REQ-UNISIG-SUB026-004827#REF#
realised by: #REQ-UNISIG-SUB026-005264#REF#

#REQ-UNISIG-SUB026-3462#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [4]: "only if valid Train Data are stored on-board"
#ANALYSE-VALUNISIG-4662#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4B11#REF# FCT PT Acceptance of information depending on mode: PT; exception[4]
#TEST-VAL-SUB026-4D68#REF# FCT SB Acceptance of information depending on mode: SB/L2 [P5, P15, P21, P27]

#REQ-UNISIG-SUB026-3465:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [5]: "only level transition announcement (i.e., “immediate” level transition order and conditional level transition order shall
be rejected)"
realised by: #REQ-DESIGN-CR-0740:03#REF#
realised by: #REQ-UNISIG-SUB026-007832:01#REF#

#REQ-UNISIG-SUB026-007832:01#REF# table.4.8.4 #REQ-UNISIG-SUB026-3465:01#REF#
exception [5]: "only level transition announcement (i.e., “immediate” level transition order shall be rejected)"

Remark:
”immediate” level transition order shall be rejected" must be interpreted as "level transition order with D_LEVELTR=now or 0 shall be
rejected.
UNISIG clarification:
D_LEVELTR=0 is interpreted also as immediate
#ANALYSE-VALUNISIG-4663#REF# FCT The filter conditions are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5489#REF# FCT basic function PT/L2 - immediate level transition order from RBC rejected

#REQ-UNISIG-SUB026-010091#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [6]: "rejected if override is active"
exception [6] is realized through 5.8.3.8
realised by: #REQ-UNISIG-SUB026-005982#REF#

#REQ-UNISIG-SUB026-010092#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [7]: "only immediate level transition order and conditional level transition order shall be accepted (i.e., level transition
announcement shall be rejected) and stored for later evaluation (see 4.4.8.1.5)"
exception [7] is realized through 4.4.8.1.5 and 4.4.20.1.11
realised by: #REQ-UNISIG-SUB026-0169:01#REF#
realised by: #REQ-UNISIG-SUB026-005262#REF#

#REQ-UNISIG-SUB026-010093#REF# table.4.8.4 #REQ-UNISIG-SUB026-2162:01#REF#
exception [8]: "only RBC transition order with null distance to execution shall be accepted (i.e., RBC transition announcement shall be
rejected) for storing the RBC ID/phone number (see 4.4.8.1.5.2)"
#TEST-VAL-SUB026-5787#REF# FCT PS Evaluation of RBC transition order in PS
#TEST-VAL-SUB026-5785#REF# FCT SH Evaluation of RBC transition order in SH

#REQ-DESIGN-CR-0548:01#REF# 4.8.5.1
If an order to switch to level NTC, 1, 2 or 3 at a further location has been received, the ERTMS/ETCS onboard equipment shall be able to store
in a transition buffer (see figure 3, first filter) three sets of information obtained from three filtered messages.
#TEST-VAL-SUB026-4909#REF# FCT LTO L1 Buffering of BG messages in level 1 announcement area (L0->L1)
#TEST-VAL-SUB026-4918#REF# FCT LTO L2 Validating circular buffer concept used during Level transition
#TEST-VAL-SUB035-5093#REF# FCT LTO L3 Buffer handling when LTO at a further location is received
#TEST-VAL-SUB035-0364#REF# FCT LTO NTC Senden V_STMMAX beim Levelwechsel STMx-->STMy(Mode SN)

#REQ-DESIGN-CR-0546:01#REF# 4.8.5.2
If a RBC transition order has been received and the Handing Over RBC is still the supervising one, the ERTMS/ETCS onboard equipment shall be
able to store in a transition buffer (see figure 3, second filter) three sets of information obtained from three filtered messages from the
Accepting RBC.
#TEST-VAL-SUB026-4916#REF# FCT basic function Validating filter 1,2 are only applied to buffer msgs recv during RBC-RBC handover

#REQ-DESIGN-CR-0550#REF# 4.8.5.3
In case three sets of information are already stored in the transition buffer, any new set to be stored shall replace the oldest one currently
stored.
is valid for LTO and HO
#TEST-VAL-SUB026-4918#REF# FCT LTO 4 MSG Validating circular buffer concept used during Level transition
#TEST-VAL-SUB026-4153#REF# FCT LTO 5 MSG Level transition handling - 5 messages during level transitiion received
#TEST-VAL-SUB026-4003#REF# FCT LTO 6 MSG Circular buffer handling Level transition L1
#TEST-VAL-SUB026-4915#REF# FCT RTO 4 MSG Validating circular buffer concept used during RBC-RBC handover
#TEST-VAL-SUB026-4155#REF# FCT RTO 5 MSG RBC transition - 5 messages from accepting RBC received
#TEST-VAL-SUB026-4154#REF# FCT RTO 6 MSG RBC transition - 6 messages from accepting RBC received
#TEST-VAL-SUB026-4308#REF# EET error expectation test circular buffer transition buffer handling

#REQ-UNISIG-SUB026-3483:01#REF# 4.8.5.4
The sets of information stored in the transition buffer shall be deleted:
a)	in case the level transition order is deleted or overwritten by another level transition order for a different level, OR
b)	in case the RBC transition order is deleted or overwritten by an order to switch to another Accepting RBC, OR
c)	in case the communication session with the RBC that provided the stored information is terminated
#TEST-VAL-SUB026-5990#REF# FCT a) LTO deleted LTO buffer deleted due to deletion of LTO
#TEST-VAL-SUB026-5991#REF# FCT a) LTO overwritten LTO buffer deleted due to level transition order for a different level
#TEST-VAL-SUB026-5989#REF# FCT b) RTO deleted RTO buffer deleted due to deletion of RTO
#TEST-VAL-SUB026-8210#REF# ECT b) RTO overwritten Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID (border not passed)
#TEST-VAL-SUB026-5992#REF# FCT c) LTO LTO buffer deleted due termination of session with the RBC that provided the stored information
#TEST-VAL-SUB026-4E90#REF# ECT c) RTO Handover to RBC2 canceled due to termination of communication session with RBC2
#TEST-VAL-SUB035-0405#REF# EET error expectation Delete STM-System speed and STM-Max speed on receipt of new LTA in SN/LSTM

#REQ-UNISIG-SUB026-3484#REF# 4.8.5.5 #REQ-DESIGN-CR-0168#REF#
#REQ-UNISIG-SUB026-3528#REF#
At the same time the level transition is performed or at the same time the Accepting RBC becomes the supervising one, the sets of information
stored in the transition buffer shall be released and re-evaluated in the sequence they have been received.
TEST APPROACH:
Following aspects have been identified:
For LTO and RTO 
1) new received information overwrites previously received information of same kind
2) new received information is added to previously received information of same kind - non profile data
3) new received information is added to previously received information of same kind - profile data (continuous and non continuous)
4) information sets with different data, not influencing each other
5) information sets with different data, influencing each other

For NTCx to NTCy LTO transition buffer only:
6) special case: three STM_MAX_SPEEDs in the transition buffer
#TEST-VAL-SUB026-4424#REF# FCT 1) LTO switch from SR/L1 to FS/L2 - border BG includes L1 MA MP-OS, level transition buffer includes several valid MA with MP
#TEST-VAL-SUB026-4426#REF# FCT 1) RTO RBC transition with mode change FS->OS, 3 different MAs in transition buffer
#TEST-VAL-SUB026-4E93#REF# FCT 2) LTO Validating order of msg evaluation from RBC handover buffer
#TEST-VAL-SUB026-4E92#REF# FCT 2) RTO Validating order of msg evaluation from RBC handover buffer
#TEST-VAL-SUB026-4268#REF# FCT 3) LTO transition UN -> FS(L2)[25] (2 MAs TSR and TSR revocation in transition buffer)
#TEST-VAL-SUB026-4E91#REF# FCT 3) RTO Validating order of msg evaluation from RBC handover buffer
#TEST-VAL-SUB026-4003#REF# FCT 4) LTO Circular buffer handling Level transition L1
#TEST-VAL-SUB026-4915#REF# FCT 4) RTO Validating circular buffer concept used during RBC-RBC handover
#TEST-VAL-SUB026-4154#REF# FCT 5) LTO RBC transition - 6 messages from accepting RBC received
#TEST-VAL-SUB026-4913#REF# FCT 5) RTO Validating order of messages evaluation from RBC handover buffer
#TEST-VAL-SUB035-0364#REF# FCT 6) Senden V_STMMAX beim Levelwechsel STMx-->STMy(Mode SN)
#TEST-VAL-SUB026-8041#REF# EET CFX00035081 level transition und Infill Daten
#TEST-VAL-SUB026-4156#REF# EET error expectation RBC transition - 2 messages from accepting RBC received
#TEST-VAL-SUB026-4866#REF# EET error expectation MP rejected if MA not covered by SSP/GP (L2->L1)
#TEST-VAL-SUB026-5671#REF# EET error expectation Profile evaluation out of level transition buffer (selective shortening of profile information)

#REQ-UNISIG-SUB026-3485#REF# 4.8.5.6
This sequential re-evaluation of all the released information shall be a prerequisite to any use by the on-board equipment (e.g. it will lead
neither to an intermediate change of mode nor to a change of information displayed to the driver) and shall obey the following principles:
a)	Starting from the information currently used by on-board at the moment the level/RBC transition is effective, the ERTMS/ETCS on-board
equipment shall determine the new information for train supervision, by performing sequential updates from the information released from the
transition buffer, if accepted.
b)	For each information update related to a re-evaluated set of information, the same rules shall apply as to information update related to
new information accepted outside a level/RBC transition context.
c)	The information resulting from this sequential update shall then be used by the ERTMS/ETCS on-board equipment.

--- FINALISED ---
Der Ablauf der Auswertung der Informationen aus den Transitionbuffern ist in den Abläufen #DSC-ACT-Perform-LevelTransition-0001#REF# und
#DSC-ACT-Perform-RBCTransition-0001#REF# bechrieben (siehe /ESBO_UNISIG_ANA/). Punkt b wird dadurch erreicht, dass die Informationen aus dem
Buffer nach der Dekodierung analog einer normalen Information behandelt werden.
Somit muss lediglich die Anforderung bestehen bleiben, dass  die Informationen aus dem Transition Buffer analog den Filterkriterien einer
"normalen" Information zu behandeln sind.
realised by: #REQ-UNISIG-SUB026-3741#REF#
realised by: #REQ-UNISIG-SUB026-3627#REF#
realised by: #REQ-UNISIG-SUB026-3628#REF#

#REQ-UNISIG-SUB026-3741#REF# 4.8.5.6 #REQ-UNISIG-SUB026-3485#REF#
If a transition buffer is evaluated, the sets of information and each information shall be evaluated with the same level and mode rules as a
"normal" received message/information.
TEST APPROACH:
The following aspects have been identified:
1) basic function
1.1) LTO
1.1.1) evaluation according to the mode
1.1.2) evaluation according to the level
1.2) RTO
1.2.1) evaluation according to the mode
1.2.2) evaluation according to the level
2) Evaluation of A3.4 during buffer procession
2.1) buffer type
2.1.1) LTO
2.1.2) RTO
2.2) A3.4 conditions valid for buffer processing
2.2.1) A3.4 b)
2.2.2) A3.4 c)
2.2.3) A3.4 d)
2.2.4) A3.4 e)
2.2.5) A3.4 n)
#TEST-VAL-SUB026-4E94#REF# FCT 1.1.1 Evaluation from LTO buffer according to the correct mode
#TEST-VAL-SUB026-4E95#REF# FCT 1.1.2 Evaluation from LTO buffer according to the correct level
#TEST-VAL-SUB026-4E96#REF# FCT 1.2.1 Evaluation from RBC handover buffer according to the correct mode
#TEST-VAL-SUB026-4E97#REF# FCT 1.2.2 Evaluation from RBC handover buffer according to the correct level
#TEST-VAL-SUB026-7149#REF# FCT 2.1.1; 2.2.1 Evaluation of A3.4 b) during LTO buffer processing
#TEST-VAL-SUB026-7150#REF# FCT 2.1.2 Evaluation of A3.4 b) during RTO buffer processing
#TEST-VAL-SUB026-7161#REF# FCT 2.2.2 Evaluation of A3.4 c) during buffer processing
#TEST-VAL-SUB026-7163#REF# FCT 2.2.3 Evaluation of A3.4 d) during buffer processing
#TEST-VAL-SUB026-7162#REF# FCT 2.2.4 Evaluation of A3.4 e) during buffer processing
#TEST-VAL-SUB026-7164#REF# FCT 2.2.5 Evaluation of A3.4 n) during buffer processing
#TEST-VAL-SUB026-7140#REF# EET error expectation SR/L1 level transition buffer L2 holds MA and CES
#TEST-VAL-SUB026-7152#REF# EET error expectation Evaluation of shorten MA during buffer processing
#TEST-VAL-SUB026-8257#REF# EET error expectation Evaluation of A3.4 MA shorten condition for buffered text messages (shorten MA extended by buffered MA)
#TEST-VAL-SUB026-8298#REF# EET error expectation Information in transition buffer after shortening trigger not effected by shorten envent

#REQ-UNISIG-SUB026-3486:01#REF# 4.8.5.7
Accepting re-evaluated Conditional Emergency Stop information according to table 4.8.3 implies that the accepted Conditional Emergency Stop
information may be accepted or rejected in a further step (see clause 3.10.2.2) depending on the given stop location. This decision, based on
the comparison between the min safe front end position of the train at the time the message was received and the given stop location, shall be
considered part of the evaluation process as it affects the further re-evaluation of information stored in the transition buffer (see clause
3.10.2.4).
realised by: #REQ-UNISIG-SUB026-3624:01#REF#
realised by: #REQ-UNISIG-SUB026-3626#REF#

#REQ-UNISIG-SUB026-3610#REF# zu.4.8.5 #ANA-UNISIG-Preprocessing-Message-0002#REF#
Präzisierung zur Aufzeichnung streckenseitig empfangener Informationen:
Die notwendige JRU-Aufzeichnung bei Empfang von Streckennachrichten (Ereignisse „Telegram from Balise“, „Message from Euro-Loop“, „Message from
RIU“, „Message from RBC“) hat unter folgenden Bedingungen zu erfolgen:
∙	Die Aufzeichnung soll sofort bei Empfang, noch vor der Konsis­tenz­prüfung der Nachricht erfolgen
∙	Die Aufzeichnung soll die aktuellen Zustände (Mode, Level, Ortsbezug, Zeitstempel) zum Zeitpunkt des Empfangs beinhalten
notwendige Festlegung für die Reihenfolge der Bearbeitungsschritte bei Auswertung einer Message
#TEST-VAL-SUB026-4799#REF# FCT BG JRU recordes error reaction after error indication (BG message)
#TEST-VAL-SUB026-4811#REF# FCT LOOP JRU recording of LOOP error and RADIO error
#TEST-VAL-SUB026-4810#REF# FCT RBC JRU recording of RBC messages and radio errors

#REQ-UNISIG-SUB026-3611#REF# zu.4.8.5 #ANA-UNISIG-Preprocessing-Message-0003#REF#
Präzisierung zur Aufzeichnung von aufgetretenen Fehlern bei Empfang streckenseitiger Informationen:
Die notwendige JRU-Aufzeichnung von meldepflichtigen Konsistenzfehlern bei Empfang von Streckennachrichten (Ereignisse „Balise Group Error“,
„Radio Error“) soll sofort bei Erkennen des Fehlers und mit den aktuellen Zuständen (Mode, Level, Ortsbezug, Zeitstempel) und vor dem Auslösen
einer eventuellen Fehlerreaktion erfolgen.
notwendige Festlegung für die Reihenfolge der Bearbeitungsschritte bei Auswertung einer Message bzw. Transition Buffers

Hinweis an Design und VAL:
Die Registrierung des Errors erfolgt somit vor den Ereignissen "Bremse ausgelöst" und "Modewechsel nach Trip"
#TEST-VAL-SUB026-4799#REF# FCT BG JRU recordes error reaction after error indication (BG message)
#TEST-VAL-SUB026-4811#REF# FCT LOOP JRU recording of LOOP error and RADIO error
#TEST-VAL-SUB026-4810#REF# FCT RBC JRU recording of RBC messages and radio errors
#TEST-VAL-SUB026-4852#REF# EET error expectation JRU recording of erronous RBC messages

#REQ-UNISIG-SUB026-3613#REF# zu.4.8.5 #ANA-UNISIG-EvaluateMessage-0001#REF#
Die Auswertung einer streckenseitigen Message soll entsprechend #DSC-ACT-Process-Message-0001#REF# erfolgen.
TEST APPROACH:
The verification focuses on the functional aspect only.
The following aspects have been identified 
1) message evaluation has to take place before buffer evaluation
2) interims mode from message evaluation has to be used for buffer evaluation 
3) LTO buffer has to be evaluated before RTO buffer
4) only the resulting mode after buffer processing has to be announced to DMI, JRU and RBC

Aspect 3) - LTO has to be evaluated before RTO - is covered by #REQ-UNISIG-SUB026-3619#REF#. 
The verification of this requirement is limited to aspect 1, 2 and 4.
#TEST-VAL-SUB026-5994#REF# FCT 1 RTO message evaluation takes place before buffer evaluation
#TEST-VAL-SUB026-4025#REF# FCT 1, 2 Level transition L1->L2 Trip information from border BG, MA, adhesion factor and text message within transition buffer
#TEST-VAL-SUB026-4407#REF# FCT 2, 4interim modes not published to DMI/JRU/RBC switch from SR/L1 to FS/L2 - border BG includes L1 MA + MP-OS, level transition buffer includes valid MA + MP-OS
#TEST-VAL-SUB026-4424#REF# FCT 4 switch from SR/L1 to FS/L2 - border BG includes L1 MA MP-OS, level transition buffer includes several valid MA with MP
#TEST-VAL-SUB026-4016#REF# EET error expectation Trip information and TC from border BG at STM -> L1 transition
#TEST-VAL-SUB026-7165#REF# EET error expectation Evaluation of trip order from LT(L1->L2) border BG

#REQ-UNISIG-SUB026-3614#REF# zu.4.8.5 #REQ-DESIGN-CR-0621#REF#
#ANA-UNISIG-EvaluateMessage-0002#REF#
Präzisierung zu 4.8.1.3:
Bei der Auswertung einer Message ist zuerst, wenn vorhanden, eine Level Transition Order auszuwerten. Der sich aus der Level Transition Order
ergebende neue Ziellevel  muss dann bei der Auswertung der anderen Informationen dieser Message berücksichtigt werden.
#TEST-VAL-SUB026-8048#REF# EET CFX00036846, CFX00037497 Acceptability of optional packet 41 with radioMsg 28
#TEST-VAL-SUB026-4152#REF# ECT basic function Information evaluation independent of packet order, level transition order is evaluated first

#REQ-UNISIG-SUB026-008022:01#REF# zu.4.8.5 #ANA-UNISIG-InfillInformation-0001:01#REF#
If a level transition order is contained in infill information, the level transition order shall be used only after evaluation the infill
information.

exception: a level transition order in infill information to be buffered - see #REQ-UNISIG-SUB026-010630#REF#
TEST APPROACH:
The following aspects have been identified:
1) infill LTO relevant for current level
2) infill LTO relevant for the announced level (buffered)
#TEST-VAL-SUB026-8281#REF# FCT 1 Evaluation of infill LTO
#TEST-VAL-SUB026-4793#REF# FCT 2 Reception of infill level transion order in L1 announcement area
#TEST-VAL-SUB026-8282#REF# EET error expectation Evaluation of infill LTO
#TEST-VAL-SUB026-8283#REF# EET error expectation Evaluation of infill LTO

#REQ-UNISIG-SUB026-3124#REF# to.4.8.5 #REQ-UNISIG-SUB026-0035#REF#
#REQ-UNISIG-SUB026-0501#REF#
#ANA-UNISIG-AccInformation-0003#REF#
If infill information are accepted but the announce balise group from the infill location reference ist not a part of the current linking
information on board, all infill information shall be ignored.
An error reaction shall not be triggered.
TEST APPROACH:
Following aspects have been identified:
1. Linking information for Infill location reference BG not available
1.1 Loop
1.2 BG
2. Infill location reference BG already passed
3. Position of infill location reference BG already passed (BG not passed)
#TEST-VAL-SUB026-4146#REF# FCT 1.1 Loop infill location reference ist not known on board, all infill informations ignored
#TEST-VAL-SUB026-3091#REF# FCT 1.2 Acceptance of Infill MA from BG
#TEST-VAL-SUB026-3255#REF# FCT 2 Loop Infill Information received after passing infill location BG
#TEST-VAL-SUB026-3256#REF# FCT 3 Loop Infill Information received after passing infill location reference
#TEST-VAL-SUB026-4145#REF# EET error expectation Processing of Infill informations when linking information updated in same BG as infill information
#TEST-VAL-SUB026-4418#REF# EET error expectation BG with non in-fill and in-fill information - linking information for in-fill ref. BG not available
#TEST-VAL-SUB026-4783#REF# EET error expectation Infill informations ignored if infill location reference unknown

#REQ-UNISIG-SUB026-3606#REF# zu.4.8.5 #ANA-UNISIG-EvaluateMessage-0012#REF#
Die Streckenprofile SSP und GDP müssen nach der Überprüfung der Filterbedingungen entsprechend 4.8 in der Applikation vor einer MA ausgewertet
werden. Dies gilt sowohl für die Auswertung einer empfangenen streckenseitigen Message als auch für die Auswertung eines "set of
information" aus dem Level- bzw. RBC-Transition-Buffer.
#TEST-VAL-SUB026-4785#REF# FCT LTO buffer SSP/GP evaluated before MA (level buffer)
#TEST-VAL-SUB026-4786#REF# FCT RTO buffer SSP/GP evaluated before MA (RBC transition buffer)
#TEST-VAL-SUB026-4784#REF# FCT message/infill SSP/GP evaluated before MA (message/infill)

#REQ-UNISIG-SUB026-3336#REF# zu.4.8.5 #ANA-UNISIG-EvaluateMessage-0006#REF#
If received the information "MA with shifted location reference", this information shall be handled with the same filter criteria for
accepted information as the information Paket 15 "Level 2 Movement Authority".
TEST APPROACH:
The following aspects have been identified:
1) dependency on the level: #REQ-DESIGN-CR-0343:01#REF# "from RBC" only
1.1) L0[2]
1.2) LNTC[2]
1.3) L1[2]
1.4) L2[3][5]
1.5) L3[3][5]
2) dependency on the mode: #REQ-UNISIG-SUB026-010050#REF#
2.1) SB[2][4]
2.2) PS
2.3) SH
2.4) FS
2.5) LS
2.6) SR
2.7) OS
2.8) SL
2.9) NL
2.10) UN
2.11) TR
2.12) PT[1][4]
2.13) SN
2.14) RV
3) transition buffers
3.1) LTO
3.2) RTO

Aspect 1 and 2 are evaluated for accepted information only. The case rejected information is covered sufficiently by module test. The
verification for  PS, SH, SL, NL, TR and RV is hence omitted. 
#TEST-VAL-SUB026-3373#REF# FCT 1.1; 2.10 Backward reference without error, no balise beween L2 announcment and transition location
#TEST-VAL-SUB026-4H58#REF# FCT 1.2; 2.13 Acception of MA with shifted location reference in levle STM (an transition order to level 2 is given)
#TEST-VAL-SUB026-4H60#REF# FCT 1.3; 2.7 Acception of MA with shifted location reference in level L1 (an transition order to level 2 is given)
#TEST-VAL-SUB026-4H62#REF# FCT 1.4; 2.4 MA with shifted location reference rejected due to outstanding M8 and not yet revoked ES
#TEST-VAL-SUB026-4H63#REF# FCT 1.5 MA with shifted location reference rejected in L3 due to outstanding M8 and not yet revoked ES
#TEST-VAL-SUB026-4851#REF# FCT 2.1 MA with Shifted Location Reference and MP-OS
#TEST-VAL-SUB026-4F20#REF# FCT 2.5 Acceptance of "MA with shifted location reference"; LS
#TEST-VAL-SUB026-3684#REF# FCT 2.6 RBC sends MA with a shifted reference location, estimated front end is outside the received MA
#TEST-VAL-SUB026-3295#REF# FCT 2.12 Message 33 in PT
#TEST-VAL-SUB026-4H13#REF# FCT 3.1 Processing of MA with a shifted reference location from level transition buffer, estimated front end is outside of MA
#TEST-VAL-SUB026-4H66#REF# FCT 3.2 MA with shifted location reference from RTO transition buffer
#TEST-VAL-SUB026-4H57#REF# EET error expectation MA with shifted location reference rejected if no level2 transition order stored onboard
#TEST-VAL-SUB026-4H59#REF# EET error expectation Acception of MA with shifted location reference in level STM (no transition order to level 2 is given)
#TEST-VAL-SUB026-4H61#REF# EET error expectation Acception of MA with shifted location reference in level L1 (no transition order to level 2 is given)
#TEST-VAL-SUB026-4H64#REF# EET error expectation MA with shifted location reference accepted in LS/L3

#REQ-UNISIG-SUB026-3619#REF# zu.4.8.5 #ANA-UNISIG-EvaluateMessage-0010#REF#
Bei gleichzeitigem Empfang einer LTO und einer RTO in einer Nachricht bzw. nach vollständiger Auswertung eines Transition Buffers ist die LTO
vor der RTO auszuwerten.
TEST APPROACH:
The requirement is not relevant for level transition from L0/L1/STM as RBC transition order is not accepted in L0/L1/STM and not valid infill
information.
The requirement is not relevant for the level transition buffer as buffering of RBC transition order due to level transition announcement is not
defined.
Following aspects have been identified:
1) LTO and RTO in same message
2) LTO and RTO in RBC transition buffer
#TEST-VAL-SUB026-4788#REF# FCT 1 LTO (L2->L1) and RTO in one message (no connection to accepting RBC established yet)
#TEST-VAL-SUB026-4790#REF# FCT 2 RBC transition order and level transition order within rbc transition buffer
#TEST-VAL-SUB026-4787#REF# EET error expectation LTO (L2->L1) and RTO in one message (connection to accepting RBC already established due to former RTO)

#REQ-UNISIG-SUB026-3620:01#REF# zu.4.8.5 #REQ-UNISIG-SUB026-3118#REF#
#ANA-UNISIG-EvaluateMessage-0011:01#REF#
Bei der Auswertung einer empfangenen streckenseitigen Nachricht entsprechend #DSC-TBL-Process-Message-0001#REF# sind bei Abarbeitung der
einzelnen Schritte die Konkretisierungen #DSC-TBL-Evaluation-Sequence-0001#REF# und #DSC-TBL-Evaluation-Sequence-0002#REF# zu berücksichtigen.
TEST APPROACH:
The aspect target level has to be evaluated first is covered by #REQ-UNISIG-SUB026-3614#REF#.
The aspect LTO has to be processed before RTO is covered by #REQ-UNISIG-SUB026-3619#REF#.
The aspect handling of optional packets of message 28 is covered by #REQ-UNISIG-SUB026-3618:01#REF#.
The aspect evaluation of SSP/GP has to be executed before MA evaluation is covered by #REQ-UNISIG-SUB026-3606#REF#.
The verification focuses on the remaining aspects (#DSC-TBL-Evaluation-Sequence-0002#REF#)
1) linking information has to be evaluated before any other information
1.1) location adjustment
1.2) infill location reference
2) level transition announcement has to be evaluated after other information
#TEST-VAL-SUB026-4821#REF# FCT 1.1; 2 P5/P80/P41 with in RBC transition buffer - transition point shifted by BG with P131 D_RBCTR=0
#TEST-VAL-SUB026-3844#REF# FCT 1.2 Buffered TRIP command overwritten by later buffered infill MA

#REQ-UNISIG-SUB026-3621#REF# zu.4.8.5 #ANA-UNISIG-EvaluateTransitionBuffer-0002#REF#
Sind in einem Transitionbuffer mehrere LTO bzw. RTO gespeichert, soll nach vollständig ausgewertetem Buffer die jeweilige letzte erhaltene
akzeptierte Order ausgeführt werden.
TEST APPROACH:
The requirement is relevant only for RTO buffer, LTO and RTO cannot be buffered in the LTO buffer.
#TEST-VAL-SUB026-4793#REF# EET CFX00039859 Reception of infill level transion order in L1 announcement area
#TEST-VAL-SUB026-4791#REF# FCT LTO Several level transition order within rbc transition buffer
#TEST-VAL-SUB026-4792#REF# FCT RTO Several RBC transition order within rbc transition buffer

#REQ-UNISIG-SUB026-3615#REF# zu.4.8.5 #REQ-UNISIG-SUB026-3118#REF#
#ANA-UNISIG-EvaluateTransitionBuffer-0001#REF#
Bei der Auswertung der „Sets of Information“ eines Transitionbuffers sind die einzelnen Informationen inkl. der Reihenfolge der Bearbeitung
analog der Auswertung in einer Message (siehe #DSC-TBL-Evaluation-Sequence-0002#REF#) vorzunehmen.
Insbesondere die Linking Informationen sind vor allen anderen Informationen auszuwerten.
TEST APPROACH:
Test focus is to verify that linking information is evaluated before the evaluation of all information only as the further sequence has no
functional relevance.
Following aspects have been identified
1) MA, SSP, GP
2) MP
3) Level announcement
4) Infill location reference
#TEST-VAL-SUB026-4655#REF# FCT 1 level transition buffer - linking information evaluated before SSP/GP
#TEST-VAL-SUB026-5727#REF# FCT 2; 3 MA with MP and level transition announcement in RBC transition buffer evaluated after linking information
#TEST-VAL-SUB026-4657#REF# FCT 4 Level transition buffer - Linking information for in-fill location reference in same BG as in-fill MA
#TEST-VAL-SUB026-3686#REF# EET error expectation SR/L1->FS/L2 - linking information and MA with Shifted Location Reference in transition buffer

#REQ-UNISIG-SUB026-3622#REF# zu.4.8.5 #ANA-UNISIG-EvaluateTransitionBuffer-0003#REF#
Akzeptierte Profildaten aus einem „set of information“ aus dem Transition Buffer sollen unmittelbar bei Auswertung des „set of information“ zur
Aktualisierung der durch das Fahrzeug gespeicherten Profildaten genutzt werden
TEST APPROACH:
The following aspects have been identified, for both LTO and RTO transition buffers:
1) sequential evaluation of profile data leads to rejection of information;
1.1) LTO
1.2) RTO
2) sequential evaluation of profile data leads to acceptance of information.
2.1) LTO
2.2) RTO
#TEST-VAL-SUB026-4798#REF# FCT 1.1 Processing of level transition buffer - SSP/GP covering buffered MA buffered after MA
#TEST-VAL-SUB026-4820#REF# FCT 1.2 RBC transition MA request timer running - MA within RBC transition buffer not valid
#TEST-VAL-SUB026-4794#REF# FCT 2.1 Processing of level transition buffer - accepted profile data do directly update the used profile on board
#TEST-VAL-SUB026-4H67#REF# FCT 2.2 RBC transition - MA within RBC transition buffer valid
#TEST-VAL-SUB026-8292#REF# EET error expectation Evaluation of buffered profile information

#REQ-UNISIG-SUB026-3623:01#REF# zu.4.8.5 #ANA-UNISIG-EvaluateTransitionBuffer-0005:01#REF#
Bei der Auswertung eines Transition Buffers ist eine in einem „set of information“ enthaltene Movement authority nur dann zu akzeptieren, wenn
sie durch die aktualisierten Profile SSP und GDP vollständig abgedeckt ist (siehe Anforderung 3.7.2.3).
Bei gegebener Abdeckung wird die an Bord gespeicherte movement authority überschrieben.
Hinweis: Die in der MA enthaltene Information „signalling related speed restriction“ ist davon ausgenommen.
TEST APPROACH:
The following aspects have been identified:
1) MA not entirely covered at the moment of evaluation of its "information set";
1.1) L1 LTO
1.2) L2 LTO
1.3) RTO
2) MA entirely covered at the moment of evaluation of its "information set", but not entirely covered anymore after the evaluation of a
subsequent "information set"
2.1) L1 LTO
2.2) L2 LTO
2.3) RTO
Exception:
3) Signalling related speed restriction = 0 (Trip order) in LTO buffer
4) Signalling related speed restriction > 0 in LTO buffer
#TEST-VAL-SUB026-4148#REF# FCT 1.1 Level transition UN/L0 ->L1 - MA in level transition buffer not completely covered by GP
#TEST-VAL-SUB026-4147#REF# FCT 1.2 Level transition FS/L1 -> FS/L2 - MA in level transition buffer not covererd SSP/GP
#TEST-VAL-SUB026-4150#REF# FCT 1.3 RBC transition - MA in transition buffer not covered SSP/GP stored on board
#TEST-VAL-SUB026-4H68#REF# FCT 2.1 Level transition UN/L0 ->L1 - MA in level transition buffer not completely covered by GP
#TEST-VAL-SUB026-4149#REF# FCT 2.2 Level transition SN/STM ->L2 - level transition buffer includes two MAs, second MA comes with SSP which does not cover any of the MAs
#TEST-VAL-SUB026-5993#REF# FCT 2.3 RTO buffered MA entirely covered at the moment of evaluation, but not covered at the end of the buffer processing
#TEST-VAL-SUB026-4H69#REF# FCT 3 Level transition UN/L0 ->L1 - Trip order in LTO buffer
#TEST-VAL-SUB026-4H76#REF# FCT 4 Level transition UN/L0 ->L1 - MA in LTO buffer
#TEST-VAL-SUB026-4151#REF# EET error expectation RBC transition - transition buffer includes two MAs, second MA comes with GP which does not cover any of the MAs
#TEST-VAL-SUB026-4796#REF# EET error expectation RBC transition MA request timer running - MA within RBC transition buffer not valid

#REQ-UNISIG-SUB026-3607#REF# zu.4.8.5 #ANA-UNISIG-EvaluateTransitionBuffer-0007#REF#
Präzisierung zu Subset 026, Kap. 3.8.2.4:
Bei der Auswertung eines Transition Buffers ist das zyklische Senden eines MA-Request erst zu stoppen, wenn nach der vollständigen
Buffer­auswertung eine neue gültige MA vorhanden ist.
TEST APPROACH:
The acceptance/processing of the MA from/in the transition buffer was tested for both LTO and RTO buffers (previous requirements). The
requirement has to do with the result of the buffer processing and not with the processing itself, hence the verification of this requirement
will focus only on the RTO buffer, since the LTO buffer falls in the same equivalence class. The following aspects have been identified:
1) valid MA in the transition buffer;
2) invalid MA in the transition buffer;
3) valid MA becomes invalid due to processing of subsequent "information set" in the transition buffer.
#TEST-VAL-SUB026-4795#REF# FCT 1 RBC transition MA request timer running - valid MA within RBC transition buffer
#TEST-VAL-SUB026-4796#REF# FCT 2 RBC transition MA request timer running - MA within RBC transition buffer not valid
#TEST-VAL-SUB026-4797#REF# FCT 3 RBC transition MA request timer running - valid MA within RBC transition buffer becomes invalid due to later buffered SSP
#TEST-VAL-SUB026-8293#REF# EET error expectation MA request during RBC/RBC Handover (buffered MA deleted due to new profile data)

#REQ-UNISIG-SUB026-3624:01#REF# to.4.8.5 #REQ-UNISIG-SUB026-3486:01#REF#
#ANA-UNISIG-EvaluateTransitionBuffer-0008#REF#
Enthält ein „set of information“ bei der sequentiellen Auswertung eines Transition Buffers eine Conditional Emergency Stop Information, so ist
die Akzeptanzprüfung dieses Conditional Emergency sofort gegen die Fahrzeugposition zum Zeitpunkt des Empfanges des Conditional Emergency Stop
auszuführen und bei Akzeptanz die gespeicherte MA entsprechend zu kürzen.

Anmerkung: Mit Zeitpunkt des Empfangs ist der Zeitpunkt des Eintrages in den Buffer gemeint.
TEST APPROACH:
The following aspects have been identified for transition buffers:
1) CES location in rear of min safe front end at the time of receipt
1.1) LTO
1.2) RTO
2) CES location in front of min safe front end at the time of receipt but in rear of min safe front end at the time of the buffer evaluation
2.1) LTO
2.2) RTO
3) CES location in front of min safe front end at the time of the buffer evaluation
3.1) LTO
3.2) RTO
#TEST-VAL-SUB026-4H93#REF# FCT 1.1 LTO transition - buffered CES with location in rear of min safe front end
#TEST-VAL-SUB026-4H92#REF# FCT 1.2 RBC transition - buffered CES with location in rear of min safe front end
#TEST-VAL-SUB026-4E99#REF# FCT 2.1 LTO transition - buffered CES with location in front of min safe front end but in rear of min safe front end at LTO
#TEST-VAL-SUB026-4022#REF# FCT 2.2 RBC transition - buffered CES with location in front of min safe front end but in rear of min safe front end at RTO
#TEST-VAL-SUB026-4E98#REF# FCT 3.1 LTO transition - buffered CES with location in front of min safe front end and LTO location
#TEST-VAL-SUB026-4018#REF# FCT 3.2 RBC transition - buffered CES with location in front of min safe front end and RTO location
#TEST-VAL-SUB026-7166#REF# EET error expectation Replacement of CES within transtion buffer

#REQ-UNISIG-SUB026-008628#REF# to.4.8.5
A Conditional Emergency Stop Message shall be rejected, if a Conditional Emergency Stop Message is evaluated and no ma is on board.
UNISIG clarification:
this case is theoretical and is only possible during evaluation the level transition buffer after change to L2), but is necessary to define a
reaction.
#TEST-VAL-SUB026-7138#REF# FCT basic function Processing CES if no MA stored on board

#REQ-UNISIG-SUB026-3625#REF# to.4.8.5 #ANA-UNISIG-EvaluateTransitionBuffer-0009#REF#
Enthält ein „set of information“ bei der sequentiellen Auswertung eines Transition Buffers eine Unconditional Emergency Stop Information, so ist
der Modewechsel nach Train Trip erst bei der Bestimmung des Modes entsprechend des Ablaufes #DSC-TBL-Evaluation-Sequence-0001#REF# nach der
vollständigen Bufferverarbeitung auszuführen.
see note 4.8.5.7.1
#TEST-VAL-SUB026-4A58#REF# EET CFX00037984 Acceptance Unconditional Emergency Stop L0[2], transition buffer includes MA+MP-SH
#TEST-VAL-SUB026-8296#REF# FCT LTO buffer Mode evaluation for UCES from LTO buffer
#TEST-VAL-SUB026-4H47#REF# FCT RTO buffer Evaluation of different information sets and UES in the RBC transition buffer

#REQ-UNISIG-SUB026-3626#REF# to.4.8.5 #REQ-UNISIG-SUB026-3486:01#REF#
#ANA-UNISIG-EvaluateTransitionBuffer-0010#REF#
Wurde bei der sequentiellen Auswertung der „set of information“ eines Transition Buffers ein Emergency Stop akzeptiert, muss dies sofort bei den
Prüfungen der Filterkriterien der folgenden „set of information“ berücksichtigt werden.
Entsprechend der Exception[5] für 4.8.3 und Figure 3 sind damit in den folgenden „set of information“ MAs inklusive anhängiger Modeprofile zu
verwerfen.
#TEST-VAL-SUB026-4409#REF# FCT LTO buffer switch from SR/L1 to TR/L2 - border BG includes L1 MA + MP-OS - LT buffer includes CES, L2 MA SSP/GP, CES
#TEST-VAL-SUB026-4824#REF# FCT RTO buffer RBC transition - buffered emergency stop blocks later buffered MA/MP

#REQ-UNISIG-SUB026-3627#REF# zu.4.8.5 #REQ-UNISIG-SUB026-3485#REF#
#ANA-UNISIG-PerformLevelTransition-0001#REF#
Eine Level Transition ist entsprechend des Ablaufes #DSC-ACT-Perform-LevelTransition-0001#REF# umzusetzen.
TEST APPROACH:
The following aspects have been identified:
1) transition when processing a message containing an LTO
2) transition when processing a transition buffer containing an LTO
3) transition when passing an LTO transition border
4) driver manual level transition;
5) infill LTO in LTO buffer
NOTE: aspect 2) is relevant only for RTO transition buffer, LTO cannot be buffered in an LTO transition buffer.
#TEST-VAL-SUB026-4268#REF# FCT 1 transition UN -> FS(L2)[25] (2 MAs TSR and TSR revocation in transition buffer)
#TEST-VAL-SUB026-4791#REF# FCT 2 Several level transition order within rbc transition buffer
#TEST-VAL-SUB026-4428#REF# FCT 3 L2/FS -> L1/OS level transition - message from the border balise group is not receive
#TEST-VAL-SUB026-5815#REF# FCT 4 PR due to level transition in SN
#TEST-VAL-SUB026-4793#REF# FCT 5 Reception of infill level transion order in L1 announcement area
#TEST-VAL-SUB026-4663#REF# EET error expectation transition SR/L1 -> L2, transition buffer includes MA and CES
#TEST-VAL-SUB026-4825#REF# EET error expectation Infill level transition order versus level transition order from in fill reference BG

#REQ-UNISIG-SUB026-3628#REF# zu.4.8.5 #REQ-UNISIG-SUB026-3485#REF#
#ANA-UNISIG-PerformRBCTransition-0001#REF#
Eine RBC Transition ist entsprechend des Ablaufes #DSC-ACT-Perform-RBCTransition-0001#REF# umzusetzen.
TEST APPROACH:
Following aspects have been identified:
1) pass announced RBC transition border
2) receive RBC transition order for current location
3) RBC transition order within RBC transition buffer
Note: The aspect RBC transition order within RBC transition buffer (3) defines a track side error refer #REQ-DESIGN-CR-0111#REF#.
#TEST-VAL-SUB026-4913#REF# FCT 1 Validating order of messages evaluation from RBC handover buffer
#TEST-VAL-SUB026-4426#REF# FCT 2 RBC transition with mode change FS->OS, 3 different MAs in transition buffer
#TEST-VAL-SUB026-4792#REF# FCT 3 Several RBC transition order within rbc transition buffer

#REQ-UNISIG-SUB026-3629#REF# zu.4.8.5 #ANA-UNISIG-PerformTransition-0001#REF#
Während der Auswertung des Transition Buffers muss die ASW sicherstellen, dass kein anderes Ereignis (z.B. Override durch Tf, Passieren EoA mit
min safe front end) zu einem Mode-/Levelwechsel führt.
TEST APPROACH:
The concurrent stimulation of buffer processing in Override can not be realized in the integration test environment. The Test focuses on the EoA
supervision  
#TEST-VAL-SUB026-4822#REF# FCT basic function Location event passing EoA not processed during level transition buffer evaluation
#TEST-VAL-SUB026-4823#REF# EET error expectation Location event passing EoA processed after level transition buffer evaluation

#REQ-UNISIG-SUB026-3631#REF# zu.4.8.5 #ANA-UNISIG-PerformTransition-0003#REF#
Liegen bei einem Levelwechsel neben den Informationen aus dem Transition Buffer weitere Ereignisse, die Auswirkungen auf die Bestimmung des
Modes haben an, so sind diese erst in der Modebestimmung nach der vollständigen Auswertung des Transition Buffers einzubeziehen.
Remark:
the mode transition from UN/SN to SR is higher prior then to FS/LS/OS. 
Therefore an actual Override overruled a movement authority in the transition buffer
=> 
- the transition buffer is evaluated complete
- when override is active, the mode changes to SR and the evaluated data are handled by 4.10

Is the same case, when the EB is commanded by NTC.
TEST APPROACH:
Following #ANA-UNISIG-PerformTransition-0003#REF#, these aspects have been identified:
1) evaluations of transitions UN/SN to FS/OS/LS/SH with lower priority than transitions UN/SN to SR;
1.1) SN->SH(p7) vs. SN->SR(p4)
1.2) UN->FS(p7) vs. UN->SR(p4)
1.3) UN->LS(p7) vs. UN->SR(p4)
1.4) UN->OS(p7) vs. UN->SR(p4)
2) EB commanded by NTC;
3) handling of buffered Conditional Emergency Stop when override is active;
4) handling of buffered Unconditional Emergency Stop when override is active.
#TEST-VAL-SUB026-5417#REF# FCT 1.1 Override in SN -> LTO (L1) - MA + MP (SH) -> SR
#TEST-VAL-SUB026-4256#REF# FCT 1.2 UN override active - transition to L2 (L2 MA available)
#TEST-VAL-SUB026-4H70#REF# FCT 1.3 UN override active - pass BG LTO(L1) now + MA, SSP, GP, MP (LS now) -> SR(L1)[44]
#TEST-VAL-SUB026-4261#REF# FCT 1.4 UN override active - pass BG LTO(L1) now + MA, SSP, GP, MP (OS now) -> SR(L1)[44]
#TEST-VAL-SUB026-4494#REF# FCT 2 SN/STM (EB applied) - transition to L1
#TEST-VAL-SUB026-4776#REF# FCT 3 Level transition L0->L2 transition buffer includes MA/SSP/GP and Conditional Emergency Stop
#TEST-VAL-SUB026-5801#REF# FCT 4 Override active when switching to L2 with unconditional emergency stop within transition buffer
#TEST-VAL-SUB026-7167#REF# EET error expectation Processing of BG with LTO L1, Stop in if in SR and trip order in SR/L2

#REQ-UNISIG-SUB026-3633:01#REF# zu.4.8.5 #REQ-UNISIG-SUB026-001267#REF#
#ANA-UNISIG-PublishResults-0001:01#REF#
Abweichend zu der sofortigen Ausgabe von Informationen an die Kommunikationspartner als Folge einer laufenden Überwachung soll die Ausgabe als
Folge der Verarbeitung einer Streckennachricht/Transition Buffers
- erst nach Abschluss der Nachrichtenverarbeitung erfolgen
- resultierende Zustände (Mode, Level) nach der Verarbeitung enthalten
- Startzeitpunkt der Nachrichtenverarbeitung enthalten
TEST APPROACH:
The requirement aspect "Startzeitpunkt der Nachrichtenverarbeitung enthalten" is valid for information which has an immediate effect like LTO or
ES only. The result of information which has to be processed like changed SSP (result new MRSP, brake curve violation, brake intervention) have
to include the time and location according to the availability of the processing result.
The test focuses on the output of the final state (mode/level) of the message and buffer processing.
Following aspects have been identified:
1) message processing
2) buffer processing 
2.1) pass border BG
2.2) pass transition location
3) combined message and buffer processing  
#TEST-VAL-SUB026-8297#REF# FCT 1 Transition from SR/L1 to OS/L2 due to message processing
#TEST-VAL-SUB026-4424#REF# FCT 2.1 switch from SR/L1 to FS/L2 - border BG includes L1 MA MP-OS, level transition buffer includes several valid MA with MP
#TEST-VAL-SUB026-4417#REF# FCT 2.2 UN->TR(L2) - LT buffer includes MA+Linking and ES
#TEST-VAL-SUB026-4407#REF# FCT 3 switch from SR/L1 to FS/L2 - border BG includes L1 MA + MP-OS, level transition buffer includes valid MA + MP-OS
#TEST-VAL-SUB026-4408#REF# EET error expectation switch from SR/L1 to TR/L2 - border BG includes L1 MA + MP-OS - LT buffer includes MA, UES, MA+TC
#TEST-VAL-SUB026-4409#REF# EET error expectation switch from SR/L1 to TR/L2 - border BG includes L1 MA + MP-OS - LT buffer includes CES, L2 MA SSP/GP, CES
#TEST-VAL-SUB026-4410#REF# EET error expectation switch from SR/L1 to OS/L2 - border BG includes L1 MA - LT buffer includes CES, L2 MA + MP-OS SSP/GP, CES
#TEST-VAL-SUB026-4416#REF# EET error expectation UN->TR(L2) - LT buffer includes MA/SSP/GP, UES, MA/SSP/GP
#TEST-VAL-SUB026-4425#REF# EET error expectation switch from FS/L1 to FS/L2 - border BG includes L1 MA + MP-OS, level transition buffer includes valid MA
#TEST-VAL-SUB026-4427#REF# EET error expectation switch from SR/L1 to OS/L2 - border BG includes L1 MA + MP-OS SSP/GP
#TEST-VAL-SUB026-4831#REF# EET error expectation JRU recording of level transition buffer processing
#TEST-VAL-SUB026-4412#REF# EET errror expectation Stop if in Staff Responsible in level transition L1->L2 border BG

#REQ-UNISIG-SUB026-3634#REF# zu.4.8.5 #REQ-UNISIG-SUB026-001267#REF#
#ANA-UNISIG-PublishResults-0003#REF#
Bei Eintreten eines oder mehrerer Ereignisse zum Senden eines Positionreports soll die Ausgabe einer expliziten Position Report Message (M136,
M157) erfolgen, unabhängig davon, dass eventuell zusätzlich zu sendende Radio-Nachrichten bereits ein Position Report-Paket enthalten.
TEST APPROACH:
Beside from M136, M157 message M129, M130, M132, M137, M138, M147, M149, M150, M153 and 158 include Packet 0 or 1.
Only M129 (session establishment), M147(mode change to TR) and M150(mode change to SB) occur in combination with a position report trigger. 
The verification is limited to scenarios with these messages.

Discussion for M157
SoM Position Report (M157) is used in SoM before reaching S10 only.
M150 indicates the end of a mission. A mission is started at the and of the SoM procedure only. 
In SoM M129 is send in S11 (beyond S10).
The reception of M147 in SoM terminates the SoM procedure.

The requirement is hence tested for M132 and M129, M147 and M150 only.
The following aspects have been identified:
1) M129
2) M132
3) M150
#TEST-VAL-SUB026-4813#REF# FCT 1, 2, 3 PR message send even if other concurrent message includes a position report
#TEST-VAL-SUB026-4814#REF# EET error expectation Multiple conditional emergency stop messages within level transition buffer
#TEST-VAL-SUB026-5988#REF# EET error expectation Break of SoM by UES in D33

#REQ-UNISIG-SUB026-3635#REF# zu.4.8.5 #ANA-UNISIG-PublishResults-0004#REF#
Die Ausgabe der Emergency Stop Quittung (M147, Acknowledgement of Emergency Stop) soll erst nach vollständiger Verarbeitung der Message bzw. des
Transition Buffers erfolgen.
Dabei ist zu jeder Emergency-Stop ID genau eine Quittungs-Nachricht zu senden.

Bei Vorhandensein mehrerer Emergency Stops mit der selben ID im Transition Buffer, ist für diese ID ein „accepted“ zu senden, wenn mindestens
eine dieser Messages akzeptiert wurde.
TEST APPROACH:
The verification focuses on the transition buffer evaluation only. The acknowledgment of a single emergency stop message is covered by
#REQ-UNISIG-SUB026-0505#REF#. 
The following aspects have been identified, for both LTO and RTO transition buffers:
1) multiple CES - different IDs (accepted and rejected)
1.1) LTO
1.2) RTO
2) multiple CES - same IDs (accepted and rejected)
2.1) LTO
2.2) RTO
3) multiple UES - different IDs
3.1) LTO
3.2) RTO
4) multiple UES - same IDs
4.1) LTO
4.2) RTO
5) CES + UES - different IDs
5.1) LTO
5.2) RTO
6) CES + UES - same IDs
6.1) LTO
6.2) RTO
#TEST-VAL-SUB026-4814#REF# FCT 1.1 Multiple conditional emergency stop messages within level transition buffer
#TEST-VAL-SUB026-4H48#REF# FCT 1.2 Multiple conditional emergency stop messages within RBC transition buffer
#TEST-VAL-SUB026-4816#REF# FCT 2.1 Multiple conditional emergency stop messages with same ID within level transition buffer
#TEST-VAL-SUB026-4817#REF# FCT 2.2 Multiple unconditional emergency stop messages within RBC transition buffer
#TEST-VAL-SUB026-4H49#REF# FCT 3.1 Multiple unconditional emergency stop messages within level transition buffer
#TEST-VAL-SUB026-4H51#REF# FCT 3.2 Multiple unconditional emergency stop messages within RBC transition buffer - different IDs
#TEST-VAL-SUB026-4H50#REF# FCT 4.1 Multiple unconditional emergency stop messages within level transition buffer
#TEST-VAL-SUB026-4H52#REF# FCT 4.2 Multiple unconditional emergency stop messages within RBC transition buffer - same ID
#TEST-VAL-SUB026-4815#REF# FCT 5.1 Multiple conditional/unconditional emergency stop messages within level transition buffer
#TEST-VAL-SUB026-4H55#REF# FCT 5.2 Conditional and unconditional emergency stop messages within RBC transition buffer - different ID
#TEST-VAL-SUB026-4H54#REF# FCT 6.1 Conditional and unconditional emergency stop messages within level transition buffer - same ID
#TEST-VAL-SUB026-4H56#REF# FCT 6.2 Conditional and unconditional emergency stop messages within RBC transition buffer - same ID

#REQ-UNISIG-SUB026-005477#REF# to.4.8.5 #ANA-UNISIG-PerformTransition-0005#REF#
The start and end condition regarding modes of text messages shall be checked after every message and buffer evaluation.
TEST APPROACH:
The following aspects have been identified:
1) message evaluation
2) buffer evaluation
#TEST-VAL-SUB026-4424#REF# FCT 1 switch from SR/L1 to FS/L2 - border BG includes L1 MA MP-OS, level transition buffer includes several valid MA with MP
#TEST-VAL-SUB026-4407#REF# FCT 2 switch from SR/L1 to FS/L2 - border BG includes L1 MA + MP-OS, level transition buffer includes valid MA + MP-OS

Chapter 4.9

#REQ-DESIGN-CR-0440#REF# 4.9.1.3
In case of entering level 1, MA Request Parameters, Position Report Parameters and Track Ahead Free Request shall be deleted.
realised by: #REQ-DESIGN-CR-0533:01#REF#
realised by: #REQ-UNISIG-SUB026-3110#REF#

#REQ-DESIGN-CR-0533:01#REF# to.4.9.1.3 #REQ-DESIGN-CR-0440#REF#
When leaving Level 2/3 to Level 0/1/STM, MA-Request- and  Position Request-Parameter shall be deleted.
UNISIG clarification:
"In case of entering level 1" ignore the change from level 2/3 to level 0/NTC.
In this cases the information has to be deleted also.
TEST APPROACH:
Levels 2 and 3 are considered as one equivalence class.
#TEST-VAL-SUB026-4422#REF# EET CFX00037965 Movement Authority Request Parameters when entering FS(L2)/UN
#TEST-VAL-SUB026-4077#REF# FCT L0 MA request and position report parameter when entering L0
#TEST-VAL-SyAnfSpezCR-0003#REF# FCT L1 MAR- und PR-Parameter werden bei Transition nach L1 gelöscht
#TEST-VAL-SUB026-4948#REF# FCT STM PR/MA parameter when entering STM

#REQ-UNISIG-SUB026-3110#REF# to.4.9.1.3 #REQ-DESIGN-CR-0440#REF#
When leaving Level 2/3 to Level 0/1/STM, a Track Ahead Free Request shall be deleted.
UNISIG clarification:
"In case of entering level 1" ignore the change from level 2/3 to level 0/NTC.
In this cases the information has to be deleted also.
TEST APPROACH:
Level 2 and 3 are considered as one equivalence class
#TEST-VAL-SUB026-4927#REF# FCT L0/1 Track Ahead Free Request - moving into L0/L1
#TEST-VAL-SUB026-4289#REF# FCT STM Track Ahead Free Request - transition to STM

#REQ-UNISIG-SUB026-3112#REF# to.4.9.1.3 #ANA-UNISIG-RBCHandover-0014#REF#
When leaving Level 2/3 to Level 0/1/STM, a RBC/RBC handover shall be terminated.
UNISIG clarification:
a RBC Handover has to be deleted also, when the train leaves L2/3 without a mode change.
TEST APPROACH:
Level 2 and 3 are considered as one equivalence class
#TEST-VAL-SUB026-8245#REF# FCT L0 Mode transition to UN in front of RBC transition border
#TEST-VAL-SUB026-4F18#REF# FCT L1 RBC/RBC handover terminated when entering L1
#TEST-VAL-SUB026-8247#REF# FCT NTC Mode transition to SN in front of RBC transition border

#REQ-UNISIG-SUB026-005486#REF# 4.9.1.3.1
In case of entering level 0, NTC or 1, the information “Inhibition of revocable TSRs from balises in L2/3” shall be deleted.
TEST APPROACH:
Level 2 and 3 are considered as one equivalence class
#TEST-VAL-SUB026-5831#REF# FCT L0 Inhibition of revocable TSRs from balises in L2/3 in L0
#TEST-VAL-SUB026-5834#REF# FCT L1 Inhibition of revocable TSRs from balises in L2/3 when entering L1
#TEST-VAL-SUB026-5832#REF# FCT NTC Inhibition of revocable TSRs from balises in L2/3 in NTC

Chapter 4.10

#REQ-UNISIG-SUB026-0762:01#REF# 4.10.1.3
Depending on which mode is entered, the action shall be one of the following:
a)	data is deleted,
b)	data is to be revalidated,
c)	data is reset (set to default values)
d)	data status is unchanged,
e)	not relevant (the action on the data cannot be determined. This concerns the entry in SF and IS modes)




[1]: exception: “U” when coming from SH

[2]: exception: “U” when coming from PS
realised by: #REQ-UNISIG-SUB026-010244#REF#
realised by: #REQ-DESIGN-DATEN-0001:02#REF#
realised by: #REQ-UNISIG-SUB026-010240#REF#
realised by: #REQ-DESIGN-DATEN-0002:02#REF#
realised by: #REQ-DESIGN-DATEN-0003:02#REF#
realised by: #REQ-DESIGN-DATEN-0004:02#REF#
realised by: #REQ-DESIGN-DATEN-0005:02#REF#
realised by: #REQ-DESIGN-DATEN-0006:02#REF#
realised by: #REQ-UNISIG-SUB026-3142:01#REF#
realised by: #REQ-UNISIG-SUB026-3143:01#REF#
realised by: #REQ-DESIGN-DATEN-0008:02#REF#
realised by: #REQ-UNISIG-SUB026-010241#REF#
realised by: #REQ-DESIGN-DATEN-0009:02#REF#
realised by: #REQ-DESIGN-DATEN-0010:02#REF#
realised by: #REQ-DESIGN-DATEN-0011:02#REF#
realised by: #REQ-DESIGN-CR-0359:02#REF#
realised by: #REQ-DESIGN-CR-0354:02#REF#
realised by: #REQ-UNISIG-SUB026-010148#REF#
realised by: #REQ-DESIGN-CR-0512:02#REF#
realised by: #REQ-DESIGN-DATEN-0015:02#REF#
realised by: #REQ-DESIGN-DATEN-0016:02#REF#
realised by: #REQ-UNISIG-SUB026-3637:01#REF#
realised by: #REQ-UNISIG-SUB026-3638:01#REF#
realised by: #REQ-DESIGN-CR-0356:02#REF#
realised by: #REQ-DESIGN-CR-0357:02#REF#
realised by: #REQ-DESIGN-CR-0125:02#REF#
realised by: #REQ-DESIGN-DATEN-0021:01#REF#
realised by: #REQ-DESIGN-DATEN-0022:02#REF#
realised by: #REQ-UNISIG-SUB026-010628#REF#
realised by: #REQ-UNISIG-SUB026-3145:02#REF#
realised by: #REQ-DESIGN-DATEN-0024:03#REF#
realised by: #REQ-DESIGN-CR-0477:02#REF#
realised by: #REQ-UNISIG-SUB026-3278#REF#
realised by: #REQ-UNISIG-SUB026-010444#REF#
realised by: #REQ-DESIGN-CR-0478:02#REF#
realised by: #REQ-DESIGN-CR-0503:02#REF#
realised by: #REQ-DESIGN-CR-0504:02#REF#
realised by: #REQ-DESIGN-DATEN-0029:01#REF#
realised by: #REQ-DESIGN-CR-0569:01#REF#
realised by: #REQ-DESIGN-DATEN-0030:02#REF#
realised by: #REQ-UNISIG-SUB026-3728:01#REF#
realised by: #REQ-UNISIG-SUB026-010246#REF#
realised by: #REQ-DESIGN-CR-0067:02#REF#
realised by: #REQ-DESIGN-DATEN-0032:02#REF#
realised by: #REQ-UNISIG-SUB026-010249#REF#
realised by: #REQ-DESIGN-DATEN-0033:02#REF#
realised by: #REQ-UNISIG-SUB026-3732#REF#
realised by: #REQ-DESIGN-DATEN-0034:02#REF#
realised by: #REQ-DESIGN-CR-0358:02#REF#
realised by: #REQ-DESIGN-DATEN-0037:02#REF#
realised by: #REQ-DESIGN-CR-0471:03#REF#
realised by: #REQ-UNISIG-SUB026-010114#REF#
realised by: #REQ-UNISIG-SUB026-010446#REF#
realised by: #REQ-UNISIG-SUB026-010623#REF#
realised by: #REQ-UNISIG-SUB026-010447#REF#
realised by: #REQ-UNISIG-SUB026-010448#REF#
realised by: #REQ-UNISIG-SUB026-010449#REF#

#REQ-UNISIG-SUB026-010244#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
The mode No Power is'nt realized in the application software (see realization of #REQ-UNISIG-SUB026-004698#REF#).
The information, which are not deleted in NP, have to be remained over No Power.
The following information shall be stored remanent:
- current valid national values
- EOLM information
- Train Position
- ERTMS/ETCS Level
- table of priority of trackside supported level
- radio network ID
- RBC-ID/Phone Number
- operated system version
- virtual balise covers
- language used to display information to the driver

Remark: The state of the remanent stored information after power on is defined in chapter 4.11.
NVs and operated system version are realized direct with requirements in chapter 3
realised by: #REQ-UNISIG-SUB026-003993#REF#
realised by: #REQ-DESIGN-CR-0044#REF#
realised by: #REQ-UNISIG-SUB026-3162:02#REF#
realised by: #REQ-DESIGN-DATEN-0031:02#REF#
realised by: #REQ-DESIGN-CR-0446:02#REF#
realised by: #REQ-UNISIG-SUB026-010250#REF#
realised by: #REQ-UNISIG-SUB026-010453#REF#
realised by: #REQ-UNISIG-SUB026-010454#REF#
realised by: #REQ-UNISIG-SUB026-010441#REF#
realised by: #REQ-UNISIG-SUB026-010443#REF#
realised by: #REQ-UNISIG-SUB026-010242#REF#
realised by: #REQ-UNISIG-SUB026-010243#REF#
realised by: #REQ-UNISIG-SUB026-010245#REF#
realised by: #REQ-UNISIG-SUB026-010248#REF#
realised by: #REQ-UNISIG-SUB026-010247#REF#

#REQ-UNISIG-SUB026-3162:02#REF# table.4.10 #REQ-UNISIG-SUB026-010244#REF#
#ANA-UNISIG-TLD-0011:01#REF#
The train position information shall be stored remanent when
- the train changes to standstill
AND
- the train is not in mode SF or IS.

The stored train location data shall be used as initial value after power on.
TEST APPROACH:
The following aspects have been identified:
1) Mode dependency
1.1) SB
1.2) PS
1.3) SH
1.4) FS
1.5) LS
1.6) SR
1.7) OS
1.8) SL
1.9) NL
1.10) UN
1.11) TR
1.12) PT
1.13) SF
1.14) IS
1.15) SN
1.16) RV
2) CAB dependency
2.1) stored cab A position - cab A opened
2.2) stored cab A position - cab B opened
2.3) stored cab B position - cab A opened
2.4) stored cab B position - cab B opened
#TEST-VAL-SUB026-4778#REF# FCT 1.1 Remanent stored train location information deleted when the train leaves standstill and train is not in mode SB
#TEST-VAL-SUB026-4366#REF# FCT 1.3 no PR at level change, standstill in SH, determine train speed and location in SH
#TEST-VAL-SUB026-3667#REF# FCT 1.4, 1.11 Train Location Information - list of LRBGs (N_TOTAL =0)
#TEST-VAL-SUB026-4H19#REF# FCT 1.5, 1.6, 1.7 Remanent stored train location in FS, OS, LS, SH, SR
#TEST-VAL-SUB026-4H21#REF# FCT 1.8, 1.16 Remanent stored train location in RV, SL
#TEST-VAL-SUB026-4H20#REF# FCT 1.9, 1.12 Remanent stored train location in TR, PT, NL
#TEST-VAL-SUB026-3668#REF# FCT 1.10 Train Location Information - Assignment of coordinate system
#TEST-VAL-SUB026-3716#REF# FCT 1.13 Processing Radio/BG message in SF
#TEST-VAL-SUB026-4570#REF# FCT 1.14 mode transition LS->IS[1], processing Radio/BG message in IS
#TEST-VAL-SUB026-4H22#REF# FCT 1.15 Remanent stored train location in UN, SN
#TEST-VAL-SUB026-4208#REF# FCT 2.1 , CFX00031759 SoM stored train location confirmed by RBC
#TEST-VAL-SUB026-5892#REF# FCT 2.2 SoM sored train location confirmed by RBC
#TEST-VAL-SUB026-5891#REF# FCT 2.3 SoM stored train location confirmed by RBC
#TEST-VAL-SUB026-5893#REF# FCT 2.4 SoM sored train location confirmed by RBC
#TEST-VAL-SUB026-4209#REF# EET CFX00031759 train location information stored remanent at standstill
#TEST-VAL-SUB026-4211#REF# EET CFX00031759 SoM location invalid - set to unknown when leaving SB

#REQ-UNISIG-SUB026-3163:01#REF# table.4.10 #ANA-UNISIG-TLD-0011:01#REF#
The remanent stored train location information shall be deleted when
- the train leaves standstill
AND
- the train is not in mode SB.
#TEST-VAL-SUB026-4H19#REF# FCT FS, OS, LS, SH, SR Remanent stored train location in FS, OS, LS, SH, SR
#TEST-VAL-SUB026-4H21#REF# FCT RV, SL Remanent stored train location in RV, SL
#TEST-VAL-SUB026-4778#REF# FCT SB Remanent stored train location information deleted when the train leaves standstill and train is not in mode SB
#TEST-VAL-SUB026-4H20#REF# FCT TR, PT, NL Remanent stored train location in TR, PT, NL
#TEST-VAL-SUB026-4H22#REF# FCT UN, SN Remanent stored train location in UN, SN

#REQ-DESIGN-DATEN-0039:01#REF# table.4.10 #ANA-UNISIG-TLD-0004#REF#
The list of reported LRBGs to the RBC as a part of train position information shall not be stored remanent.
#TEST-SWHWINT-SWVAL-FKT-0007#REF# EET error expectation Liste der gemeldeten LRBGs an das RBC werden nicht remanent gespeichert

#REQ-DESIGN-DATEN-0031:02#REF# table.4.10 #REQ-UNISIG-SUB026-010244#REF#
The current ERTMS/ETCS level shall be stored remanent.
The stored ERTMS/ETCS level shall be used as initial value after power on.
#TEST-VAL-SUB026-4F63#REF# FCT basic function Remanent storage of ETCS level
#TEST-SWHWINT-SWVAL-FKT-0006#REF# EET error expectation Löschen der Table of priority (NP)

#REQ-UNISIG-SUB026-3251:01#REF# table.4.10
If Level STM is stored remanent the current stm id shall be stored remanent also.
UNISIG clarification:
the current active stm is also relevant  in level stm
#TEST-VAL-SUB026-4F63#REF# FCT basic function Remanent storage of ETCS level
#TEST-SWHWINT-SWVAL-FKT-0006#REF# EET error expectation Löschen der Table of priority (NP)

#REQ-DESIGN-CR-0446:02#REF# table.4.10 #REQ-DESIGN-CR-0433#REF#
#REQ-UNISIG-SUB026-010244#REF#
The current Radio Network ID shall be stored remanent.
The stored Radio Network ID shall be used as initial value after power on.
TEST APPROACH:
The following aspects have been identified:
1) basic software functionality 
2) software hardware integration
#TEST-VAL-SUB026-7940#REF# FCT 1 Remanent storage of Radio network ID
#TEST-VAL-SUB026-3983#REF# EET error expectation OBU establishes session with same RBC but new network
#TEST-SWHWINT-salsa-0006#REF# FCT 2 CR07 – Beibehaltung der eingegebenen DMI MN-Id

#REQ-UNISIG-SUB026-010250#REF# table.4.10 #REQ-UNISIG-SUB026-010244#REF#
The current RBC ID/Phone Number shall be stored remanent.
The stored RBC ID/Phone Number shall be used as initial value after power on.
#TEST-VAL-SUB026-7940#REF# FCT basic function Remanent storage of Radio network ID
#TEST-VAL-SUB026-7942#REF# EET error expectation Remanent RBC ID/phone number remain unchanged when entering L1/L2

#REQ-UNISIG-SUB026-010453#REF# table.4.10 #REQ-UNISIG-SUB026-010244#REF#
The last received EOLM Information shall be stored remanent.
The stored EOLM Information shall be used as initial value after power on.
"Cold movement detection" function is not realized => the remanent storage isn't necessary
--- FINALISED ---
As no "Cold Movement Detection" function is realized, the remanent stored information EOLM and table of priority are set to unknown
after power on (see 4.11.).
Therefore it is not necessary to store the information EOLM and table of priority remanent.
#ANALYSE-VALUNISIG-5294#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010454#REF# table.4.10 #REQ-UNISIG-SUB026-010244#REF#
The last received table of priority of trackside supported level shall be stored remanent.
The stored  table of priority of trackside supported level shall be used as initial value after power on.
"Cold movement detection" function is not realized => the remanent storage isn't necessary
--- FINALISED ---
As no "Cold Movement Detection" function is realized, the remanent stored information EOLM and table of priority are set to unknown
after power on (see 4.11.).
Therefore it is not necessary to store the information EOLM and table of priority remanent.
#ANALYSE-VALUNISIG-5295#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010441#REF# table.4.10 #REQ-UNISIG-SUB026-010244#REF#
The current known Virtual Balise Covers shall be stored remanent.
The stored Virtual Balise Covers shall be used as initial value after power on.
VBC function is not realized

=> no driver input, no P6 => a VBC doesn't exists

#REQ-UNISIG-SUB026-010443#REF# table.4.10 #REQ-UNISIG-SUB026-010244#REF#
The current language used to display information to the driver shall be stored remanent.
The language used to display information to the driver shall be used as initial value after power on.

--- FINALISED ---
The language, used to display information to the driver, is managed in the DMI. The EVC only activates/deactivates the button for the language
selection.

In ERA SRS DMI isn't define a mode dependency for the Language. The remanent storage is required in the SRS DMI (see /SRS_DMI/,
SRS_DMI_BL3-597).
#ANALYSE-VALUNISIG-5297#REF# FCT The DMI is in charge of language management refer #REQ-SRS_DMI-000565#REF#. The ASW provides a storage function refer #REQ-FFFIS_MMI-006168#REF#, #REQFFFIS_MMI-008849#REF#. The requirement has to be covered by [ESBO_SyValBer].

#REQ-DESIGN-DATEN-0001:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'National values currently applicable' shall remain unchanged, when mode is changed.
realized with 3.18.2.7
--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
#TEST-VAL-SUB026-3727#REF# FCT LS L1->L2 Level transition buffer information evaluation due to axle load change
#TEST-VAL-SUB026-4D16#REF# FCT NL Check radio link (only level 2/3); SR, NL
#TEST-VAL-SUB026-4D23#REF# FCT OS T_NVCONTACT after mode changes to OS
#TEST-VAL-SUB026-3B04#REF# FCT PS NV not yet applicable remain unchanged at modes transitions (PS)
#TEST-VAL-SUB026-4D27#REF# FCT RV Stored National Values when mode changes to RV, SB, FS
#TEST-VAL-SUB026-4D28#REF# FCT SH, SB, FS Stored Data for National Values; SH, SB, FS
#TEST-VAL-SUB026-4435#REF# FCT SL NV when entering SL, SB, SR, SH
#TEST-VAL-SUB026-4436#REF# FCT SN, TR, PT, SR, UN NV when entering SN, UN, TR, PT
#TEST-SWHWINT-SWVAL-FKT-0001#REF# FCT NP / IS / SF Nicht löschen der National Values (NP, IS, SF)

#REQ-UNISIG-SUB026-010240#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored not yet applicable National Values shall remain unchanged, when mode is changed.
realize through 3.18.2.9
--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
TEST APPROACH:
The deletion of the 'Not yet applicable National Values' when entering IS, SF has no functional relevance as these modes can be left via NP only
. The test for the mode IS and SF is omitted
#TEST-VAL-SUB026-3B03#REF# FCT LS, NL, SL, SB, UN, SR NV not yet applicable remain unchanged at modes transitions (LS, NL, SL, SB, UN, SR)
#TEST-VAL-SUB026-3B04#REF# FCT PS NV not yet applicable remain unchanged at modes transitions (PS)
#TEST-VAL-SUB026-3B05#REF# FCT RV NV not yet applicable remain unchanged at mode transition to RV
#TEST-VAL-SUB026-5931#REF# FCT SH Stored not yet applicable National Values when entering SH
#TEST-VAL-SUB026-3B02#REF# FCT SN, TR, PT, FS, OS NV not yet applicable remain unchanged at modes transitions (SN, TR, PT, FS, OS)

#REQ-DESIGN-DATEN-0002:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'linking' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The ETCS mode PS can be accessed via SH only, linking information is deleted when entering SH and new linking information is not accepted.
The ETCS mode PT can be accessed via TR only, linking information is deleted when entering TR and new linking information is not accepted.
The ETCS mode SL can be accessed via SB only. Although linking information is accepted in SB (only if a desk is open), when closing the desk,
the linking information is deleted (A3.6. cond.[k]). 
The verification for the ETCS modes PS, PT and SL is hence omitted
#TEST-VAL-SUB026-4951#REF# EET CFX00034017 Nach Linkreaktion wird erwartete Balise wieder akzeptiert.
#TEST-VAL-SUB026-4950#REF# EET CFX00035121 Nach Linkreaktion wird erwartete Balise wieder akzeptiert.
#TEST-VAL-SUB026-4C39#REF# FCT FS, OS Stored data: Linking information when mode changes to FS/L2, OS/L2
#TEST-VAL-SUB026-4558#REF# FCT LS linking information when entering LS, L2 LS->SB[28]->LS[70]->TR[66] ->PT->LS[70]
#TEST-VAL-SUB026-4C44#REF# FCT NL Stored data: Linking information when mode changes to NL/L2
#TEST-VAL-SUB026-4C45#REF# FCT RV Stored data: Linking information when mode changes to RV/L2
#TEST-VAL-SUB026-4C42#REF# FCT SB Stored data: Linking information when mode changes to SB/L2
#TEST-VAL-SUB026-4C40#REF# FCT SH Stored data: Linking information when mode changes to SH/L1
#TEST-VAL-SUB026-4713#REF# FCT SN Linking information when entering SN
#TEST-VAL-SUB026-4C43#REF# FCT SR Stored data: Linking information when mode changes to SR/L2, FS/L2
#TEST-VAL-SUB026-4417#REF# FCT TR UN->TR(L2) - LT buffer includes MA+Linking and ES
#TEST-VAL-SUB026-4C41#REF# FCT UN Stored data: Linking information when mode changes to UN/L0, FS/L1

#REQ-DESIGN-DATEN-0003:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Movement Authority' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
Movement authority has a meaning in the ETCS mode FS, LS, OS only.
These modes can be entered after receiving valid MA only. A new MA replaces an older MA.
The verification is limitted only to modes FS, LS, OS, UN and SN.
#TEST-VAL-SUB026-4679#REF# FCT LS MA(L1 V_MAIN)/SSP/GP ASP when entering LS
#TEST-VAL-SUB026-4C11#REF# FCT OS, FS Stored data: MA, GP, International SSP, Axle load SP when changing to OS/L2, FS/L2
#TEST-VAL-SUB026-4848#REF# FCT SN MA when entering SN
#TEST-VAL-SUB026-4847#REF# FCT UN MA when entering UN

#REQ-DESIGN-DATEN-0004:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Gradient Profile' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The Gradient Profile is used in FS, OS and LS.
A transition from ETCS mode SL, NL, SH, PS, PT and RV to FS, LS or OS is possible via modes where the Gradient Profile is deleted only.
The verification for the ETCS modes SL, NL, SH, PS, PT (new information rejected in TR) and RV is hence omitted.
#TEST-VAL-SUB026-4679#REF# FCT LS MA(L1 V_MAIN)/SSP/GP ASP when entering LS
#TEST-VAL-SUB026-4C11#REF# FCT OS, FS Stored data: MA, GP, International SSP, Axle load SP when changing to OS/L2, FS/L2
#TEST-VAL-SUB026-4E10#REF# FCT SB Stored data: MA, GP, SSP when changing to SB/L2
#TEST-VAL-SUB026-4E13#REF# FCT SN Stored data: MA, GP, SSP when changing to SN/STM
#TEST-VAL-SUB026-4E09#REF# FCT SR Stored data: MA, GP, SSP when changing to SR/L2
#TEST-VAL-SUB026-4E11#REF# FCT TR Stored data: MA, GP, SSP when changing to TR,PT/L2
#TEST-VAL-SUB026-4E12#REF# FCT UN Stored data: MA, GP, SSP when changing to UN/L0

#REQ-DESIGN-DATEN-0005:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'International SSP' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS mode SL, PS and PT is possible via modes where the International SSP is deleted and not accepted. The verification for
the ETCS modes SL, PS and PT is hence omitted.
From modes SH, NL and RV, the transition to a mode where the information is managed is possible only via modes where information is deleted.
However, the verification for these modes is provided here, to check that in these modes the information is not considered at all. 
#TEST-VAL-SUB026-4679#REF# FCT LS MA(L1 V_MAIN)/SSP/GP ASP when entering LS
#TEST-VAL-SUB026-4C16#REF# FCT NL Stored data: MA, GP, International SSP, Axle load SP when changing to NL/L2
#TEST-VAL-SUB026-4C11#REF# FCT OS, FS Stored data: MA, GP, International SSP, Axle load SP when changing to OS/L2, FS/L2
#TEST-VAL-SUB026-4C17#REF# FCT RV Stored data: MA, GP, International SSP, Axle load SP when changing to RV/L2
#TEST-VAL-SUB026-4E10#REF# FCT SB Stored data: MA, GP, SSP when changing to SB/L2
#TEST-VAL-SUB026-4C13#REF# FCT SH Stored data: MA, GP, International SSP, Axle load SP when changing to SH/L1, FS/L1
#TEST-VAL-SUB026-4E13#REF# FCT SN Stored data: MA, GP, SSP when changing to SN/STM
#TEST-VAL-SUB026-4E09#REF# FCT SR Stored data: MA, GP, SSP when changing to SR/L2
#TEST-VAL-SUB026-4E11#REF# FCT TR Stored data: MA, GP, SSP when changing to TR,PT/L2
#TEST-VAL-SUB026-4E12#REF# FCT UN Stored data: MA, GP, SSP when changing to UN/L0

#REQ-DESIGN-DATEN-0006:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Axle load speed profile' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS mode SL, PS and PT is possible via modes where the Axle load speed profile is deleted and not accepted. The verification
for the ETCS modes SL, PS and PT is hence omitted.
From modes SH, NL and RV, the transition to a mode where the information is managed is possible only via modes where information is deleted.
However, the verification for these modes is provided here, to ensure that in these modes the information is not considered at all. 
#TEST-VAL-SUB026-4679#REF# FCT LS MA(L1 V_MAIN)/SSP/GP ASP when entering LS
#TEST-VAL-SUB026-4C16#REF# FCT NL Stored data: MA, GP, International SSP, Axle load SP when changing to NL/L2
#TEST-VAL-SUB026-4C11#REF# FCT OS, FS Stored data: MA, GP, International SSP, Axle load SP when changing to OS/L2, FS/L2
#TEST-VAL-SUB026-4C17#REF# FCT RV Stored data: MA, GP, International SSP, Axle load SP when changing to RV/L2
#TEST-VAL-SUB026-4C14#REF# FCT SB Stored data: MA, GP, International SSP, Axle load SP when changing to SB/L2, SL/L2, FS/L2
#TEST-VAL-SUB026-4C13#REF# FCT SH Stored data: MA, GP, International SSP, Axle load SP when changing to SH/L1, FS/L1
#TEST-VAL-SUB026-4742#REF# FCT SN Axel load Speed Profile transition to SN
#TEST-VAL-SUB026-4C12#REF# FCT SR Stored data: MA, GP, International SSP, Axle load SP when changing to SR/L2, FS/L2
#TEST-VAL-SUB026-4C18#REF# FCT TR Stored data: MA, GP, International SSP, Axle load SP when changing to TR/L2, PT/L2, FS/L2
#TEST-VAL-SUB026-4C15#REF# FCT UN Stored data: MA, GP, International SSP, Axle load SP when changing to UN/L0, FS/L1

#REQ-UNISIG-SUB026-3142:01#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'STM max speed' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A level transition order to STM is deleted when entering SB, SH, PS, SR, SL, NL, UN, RV and a new level transition order deletes the stored "STM
max speed" refer #REQ-UNISIG-SUB035-009209#REF#. The verification for the ETCS modes SB, SH, PS, SR, SL, NL, UN and RV is hence omitted. 
#TEST-VAL-SUB026-4C94#REF# FCT FS Stored data: STM max speed and STM system speed/distance when entering FS
#TEST-VAL-SUB026-4A45#REF# FCT LS Stored data: STM max speed and STM system speed/distance when entering LS
#TEST-VAL-SUB026-4C93#REF# FCT OS Stored data: STM max speed and STM system speed/distance when entering OS
#TEST-VAL-SUB026-4C98#REF# FCT PT Acceptance of STM max speed and STM system speed/distance: TR
#TEST-VAL-SUB026-4E02#REF# FCT SN Stored data: STM max speed and STM system speed/distance when mode changes to SN/STM
#TEST-VAL-SUB026-4C97#REF# FCT TR Stored data: STM max speed and STM system speed/distance when entering TR/PT/L2
#TEST-VAL-SUB026-4509#REF# EET error expectaion STM system speed/distance and STM max speed when entering NL
#TEST-VAL-SUB026-4C95#REF# EET error expectation Stored data: STM max speed and STM system speed/distance when entering SR
#TEST-VAL-SUB026-4E01#REF# FCT error expectation Stored data: STM max speed and STM system speed/distance when mode changes to SB/L2

#REQ-UNISIG-SUB026-3143:01#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'STM system speed/distance' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A level transition order to STM is deleted when entering SB, SH, PS, SR, SL, NL, UN, RV and a new level transition order deletes the stored "STM
max speed" refer #REQ-UNISIG-SUB035-009209#REF#. The verification for the ETCS modes SB, SH, PS, SR, SL, NL, UN and RV is hence omitted. 
#TEST-VAL-SUB026-4C94#REF# FCT FS Stored data: STM max speed and STM system speed/distance when entering FS
#TEST-VAL-SUB026-4A45#REF# FCT LS Stored data: STM max speed and STM system speed/distance when entering LS
#TEST-VAL-SUB026-4C93#REF# FCT OS Stored data: STM max speed and STM system speed/distance when entering OS
#TEST-VAL-SUB026-4C98#REF# FCT PT Acceptance of STM max speed and STM system speed/distance: TR
#TEST-VAL-SUB026-4E02#REF# FCT SN Stored data: STM max speed and STM system speed/distance when mode changes to SN/STM
#TEST-VAL-SUB026-4C97#REF# FCT TR Stored data: STM max speed and STM system speed/distance when entering TR/PT/L2
#TEST-VAL-SUB026-4510#REF# EET error expectation SL - acceptance STM system speed/distance and STM max speed
#TEST-VAL-SUB026-4C95#REF# EET error expectation Stored data: STM max speed and STM system speed/distance when entering SR

#REQ-DESIGN-DATEN-0008:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information "Level Transition Order" shall be deleted when entering the mode

SB[1][2], SH[2], SR, SL[2], NL[1], UN, SN, RV

[1]: "U" when coming from SH
[2]: "U" when coming from PS

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
#TEST-VAL-SUB026-4C65#REF# FCT FS, OS Stored data: Level transition order when mode changes to FS/L1, OS/L2
#TEST-VAL-SUB026-4680#REF# FCT LS Supervision of safe radio connection in LS
#TEST-VAL-SUB026-4C67#REF# FCT NL Stored data: Level transition order when mode changes to NL/L2
#TEST-VAL-SUB026-5782#REF# FCT NL[1] CLTO received in SH evaluated when switching to NL
#TEST-VAL-SUB026-5783#REF# FCT PS CLTO received in SH evaluated after switching to SB via PS/SH
#TEST-VAL-SUB026-4C68#REF# FCT RV Stored data: Level transition order when mode changes to RV/L2
#TEST-VAL-SUB026-4367#REF# FCT SB PR at level change, when establishing a session with RBC, determine train speed and location
#TEST-VAL-SUB026-5777#REF# FCT SB[1] Evaluation of immediate level transition order in SH
#TEST-VAL-SUB026-4366#REF# FCT SH no PR at level change, standstill in SH, determine train speed and location in SH
#TEST-VAL-SUB026-4C66#REF# FCT SL Stored data: Level transition order when mode changes to SB/L2, SL/L1
#TEST-VAL-SUB026-4853#REF# FCT SN Level transition order when mode changes to SN
#TEST-VAL-SUB026-4314#REF# FCT SR Deletion of level transition order when entering SR
#TEST-VAL-SUB026-4C70#REF# FCT TR, PT Stored data: Level transition order when mode changes to TR/L2, PT/L1
#TEST-VAL-SUB026-4C69#REF# FCT UN Stored data: Level transition order when mode changes to UN/L0

#REQ-UNISIG-SUB026-010241#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Stop Shunting on desk opening' shall be deleted when entering the mode

SB, SL

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
The information is generally ignored
TEST APPROACH:
PS is not part of R8.0 refer #REQ-SRS-004412#REF#

#REQ-DESIGN-DATEN-0009:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'List of balises for SH area' shall be deleted when entering the mode

SB, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The 'List of balises for SH area' is relevant in the mode SH only.
The information is accepted only  if received in M28 or together with MP-SH. A Mode profile is accepted only together with a accepted MA. 
The acceptance of SH authorized results into a mode transition to SH. The processing of a accepted MA +MP results in mode FS, OS, LS or SH.
The deletion of a stored 'List of balises for SH area', when SH authorised or new mode profile is received, or the current mode profile is
deleted, is covered by #REQ-UNISIG-SUB026-0581:01#REF#.
The mode SH can be leaved via SB, PS, NL and  TR. NL can be via SB only. A transition from SL and  RV to SH is possible via SB only, the
information is deleted when entering SB anyway. 
Hence, the following aspects remain to be tested:
1) 'List of balises for SH area' is not deleted when entering FS, OS, LS, SH and PS
1.1) FS
1.2) OS
1.3) LS
1.4) SH
1.5) PS
2) 'List of balises for SH area' is deleted when entering SB and TR
2.1) SB
2.2) TR
Note: from modes SB and TR, the transition to SH without receiving new MP-SH or new SH Auth. can only be done via SH by driver, in levels other
than L2/3. 
When SH by driver is performed, the List of balises for SH is deleted. 
However, test cases are provided for these aspects in order to verify that the functional behavior is OK in these scenarios (i.e. List of
balises for SH is deleted).
#TEST-VAL-SUB026-5959#REF# FCT 1.1, 1.2, 1.3, 1.4 Evaluation of List of balises for SH area
#TEST-VAL-SUB026-5985#REF# FCT 1.5 List of balises for SH area when entering PS
#TEST-VAL-SUB026-5982#REF# FCT 2.1 List of balises for SH area when entering SB
#TEST-VAL-SUB026-5984#REF# FCT 2.2 List of balises for SH area when entering TR

#REQ-DESIGN-DATEN-0010:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'MA Request Parameters' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
TEST APPROACH:
The deletion of the 'MA Request Parameters' when entering IS, SF has no functional relevance as these modes can be left via NP only . The test
for the mode IS and SF is omitted
#TEST-VAL-SUB026-4573#REF# FCT LS Movement Authority Request Parameters in LS
#TEST-VAL-SUB026-4527#REF# FCT NL Movement Authority Request Parameters in NL
#TEST-VAL-SUB026-4522#REF# FCT OS Movement Authority Request Parameters in OS
#TEST-VAL-SUB026-5954#REF# FCT PS MA request parameter and position report parameter when entering PS
#TEST-VAL-SUB026-4528#REF# FCT RV Movement Authority Request Parameters in RV
#TEST-VAL-SUB026-4520#REF# FCT SB, FS Movement Authority Request Parameters in SB
#TEST-VAL-SUB026-4526#REF# FCT SH Movement Authority Request Parameters when entering SH
#TEST-VAL-SUB026-4525#REF# FCT SL Movement Authority Request Parameters in SL, acceptance in UN
#TEST-VAL-SUB026-4874#REF# FCT SN MA request parameter when entering STM
#TEST-VAL-SUB026-4521#REF# FCT SR Movement Authority Request Parameters in SR
#TEST-VAL-SUB026-4523#REF# FCT TR/PT Movement Authority Request Parameters in PT
#TEST-VAL-SUB026-4873#REF# FCT UN MA request parameter when entering UN
#TEST-SWHWINT-SWVAL-FKT-0002#REF# EET error expectation Löschen der MA Request Parameters (NP)

#REQ-DESIGN-DATEN-0011:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Position Report Parameters' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
TEST APPROACH:
The deletion of the 'Position Report Parameters' when entering IS, SF has no functional relevance as these modes can be left via NP only . The
test for the mode IS and SF is omitted
#TEST-VAL-SUB026-4399#REF# FCT FS Position Report parameters when entering FS
#TEST-VAL-SUB026-4575#REF# FCT LS Position Report parameters when entering / in LS
#TEST-VAL-SUB026-4395#REF# FCT OS, TR, PT Position Report parameters when entering OS/SR/TR/PT
#TEST-VAL-SUB026-5954#REF# FCT PS MA request parameter and position report parameter when entering PS
#TEST-VAL-SUB026-4397#REF# FCT RV Position Report parameters when entering RV
#TEST-VAL-SUB026-4394#REF# FCT SH Position Report parameters when entering SH/TR
#TEST-VAL-SUB026-4396#REF# FCT SL, SB, NL Position Report parameters when entering SL/NL/SB
#TEST-VAL-SUB026-4875#REF# FCT SN PR parameter when entering STM
#TEST-VAL-SUB026-4207#REF# FCT SR , CFX00035327 MA request and position report parameter when entering SB/SR
#TEST-VAL-SUB026-4402#REF# FCT UN Position Report parameters when entering UN(L1->L0)
#TEST-SWHWINT-SWVAL-FKT-0003#REF# EET error expectation Löschen der Position Report Parameters (NP)

#REQ-DESIGN-CR-0359:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'List of Balises in SR Authority + SR mode speed limit and distance' shall be deleted when entering the mode

SB, PS, SH, FS, LS, OS, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS mode SL, NL, RV, SH and PS to SR is possible via SB, UN or SN only. The information is deleted when entering SB, UN and
SN.
A transition from ETCS mode PT is possible via TR only. The information is deleted when entering TR and new information is rejected in TR.
The verification for the ETCS modes SL, NL, RV, SH, PT and PS is hence omitted.
#TEST-VAL-SUB026-8276#REF# EET CFX00189145 Supervision of SR distance
#TEST-VAL-SUB026-4C79#REF# FCT FS Stored data: List of balises for SR + SR speed + SR distance when mode changes to FS/L1
#TEST-VAL-SUB026-4550#REF# FCT LS SR mode speed limit and distance when entering LS
#TEST-VAL-SUB026-4C80#REF# FCT OS Stored data: List of balises for SR + SR speed + SR distance when mode changes to OS/L1
#TEST-VAL-SUB026-4C82#REF# FCT SB Stored data: List of balises for SR + SR speed + SR distance when mode changes to SB/L1
#TEST-VAL-SUB026-4478#REF# FCT SN SN/STM - stored information SR Authorisation with List of Balises in SR Authority
#TEST-VAL-SUB026-4C78#REF# FCT SR, TR Stored data: List of balises for SR + SR speed + SR distance when mode changes to TR/L1, PT/L1
#TEST-VAL-SUB026-4C81#REF# FCT UN Stored data: List of balises for SR + SR speed + SR distance when mode changes to UN/L0

#REQ-DESIGN-CR-0354:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Temporary Speed Restriction' shall be deleted when entering the mode

SB, PS, SH, SL, NL, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS mode SL and PS is possible via modes where the TSR is deleted and not accepted. The verification for the ETCS modes SL
and PS is hence omitted.
From modes SH, NL and RV, the transition to a mode where the information is managed is possible only via modes where information is deleted.
However, the verification for these modes is provided here, to ensure that in these modes the information is not considered at all.
#TEST-VAL-SUB026-4229#REF# EET CFX00036874 TSR when entering SR
#TEST-VAL-SUB026-4D20#REF# FCT FS, OS TSR + Delete Revoked TSR; FS, OS
#TEST-VAL-SUB026-4551#REF# FCT LS , CFX00039889 TSR when entering LS, TSR in LS; OS->LS[70]
#TEST-VAL-SUB026-4D36#REF# FCT NL TSR: NL, SB
#TEST-VAL-SUB026-4D32#REF# FCT RV TSR: RV/L2
#TEST-VAL-SUB026-4278#REF# FCT SB TSR when entering SB (->SR)
#TEST-VAL-SUB026-4D33#REF# FCT SH TSR: SH
#TEST-VAL-SUB026-4302#REF# FCT SN Default gradient for TSR (SR->SN->SR)
#TEST-VAL-SUB026-4D29#REF# FCT SR TSR: SR, NL, SB and Delete Revoked TSR: SR, SB
#TEST-VAL-SUB026-4461#REF# FCT TR,PT TSR, default gradient for TSR when entering TR/PT/SR
#TEST-VAL-SUB026-4D31#REF# FCT UN Delete Revoked TSR: UN

#REQ-UNISIG-SUB026-010148#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Inhibition of revocable TSRs from balises in L2/3' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The appropriated function is active in the ETCS modes FS, LS, OS, TR and PT only.
The information is deleted when entering SB, UN and SN.
The transition from NL, SL and RV to FS, LS, OS, TR or PT is only be possible via SB. The verification of NL, SL and RV is hence omitted.
The transition from SH and PS to FS, LS, OS, TR or PT is only be possible via SB, UN or SN. The verification of SH and PS is hence omitted.
#TEST-VAL-SUB026-5836#REF# FCT OS, LS, TR Inhibition of revocable TSRs from balises in L2/3 when entering OS, LS, TR
#TEST-VAL-SUB026-5827#REF# FCT PT, FS Inhibition of revocable TSRs from balises in L2/3 in TR
#TEST-VAL-SUB026-5835#REF# FCT SB Inhibition of revocable TSRs from balises in L2/3 when entering SB
#TEST-VAL-SUB026-5832#REF# FCT SN Inhibition of revocable TSRs from balises in L2/3 in NTC
#TEST-VAL-SUB026-5833#REF# FCT SR Inhibition of revocable TSRs from balises in L2/3 in L3
#TEST-VAL-SUB026-5831#REF# FCT UN Inhibition of revocable TSRs from balises in L2/3 in L0

#REQ-DESIGN-CR-0512:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Default Gradient for TSR' shall be deleted when entering the mode

SB, PS, SH, SL, NL, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from modes to mode PS is possible only from mode SH.
The information 'Default Gradient for TSR' is deleted when entering SH and new information is rejected in SH.
The verification for mode PS is hence omitted.
#TEST-VAL-SUB026-4994#REF# FCT FS,OS Check 4.10 --> Default gradient profile (FS, OS)
#TEST-VAL-SUB026-3749#REF# FCT LS default gradient for TSR handling UN/LS/L0/L1
#TEST-VAL-SUB026-4299#REF# FCT NL Default gradient for TSR (SR->NL->SB->SR)
#TEST-VAL-SUB026-4658#REF# FCT RV TSR/default gradient for TSR, accepted in SR/L1 deleted when entering RV
#TEST-VAL-SUB026-4298#REF# FCT SB Check table 4.8.4/4.10 Information->Default gradient for TSR (SR->SB-SR)
#TEST-VAL-SUB026-4300#REF# FCT SH Default gradient for TSR (SR->SH->SB->SR)
#TEST-VAL-SUB026-4301#REF# FCT SL Default gradient for TSR (SR->(SB)SL(SB)->SR)
#TEST-VAL-SUB026-4302#REF# FCT SN Default gradient for TSR (SR->SN->SR)
#TEST-VAL-SUB026-4461#REF# FCT TR,PT,SR TSR, default gradient for TSR when entering TR/PT/SR
#TEST-VAL-SUB026-4462#REF# FCT UN TSR, default gradient for TSR when entering UN

#REQ-DESIGN-DATEN-0015:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Signalling related Speed Restriction' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The information "Signalling related Speed Restriction" is part of the Level 1 MA only. The reception of a new MA overrides the former MA hence
it is not possible to execute a mode transition to FS/LS/OS without overriding the information. 
The verification of the deletion of the information is hence limited to check that the speed restriction is not taken into account in the target
mode.
#TEST-VAL-SUB026-4F01#REF# FCT FS Signalling related speed restriction: OS/L1, FS/L1
#TEST-VAL-SUB026-4679#REF# FCT LS MA(L1 V_MAIN)/SSP/GP ASP when entering LS
#TEST-VAL-SUB026-4F02#REF# FCT OS Signalling related speed restriction: FS/L1, OS/L1
#TEST-VAL-SUB026-7038#REF# FCT PS Signaling speed restriction when entering PS
#TEST-VAL-SUB026-4846#REF# FCT RV, NL, SH, UN, SB Signalling related Speed Restriction in RV, NL, SH, UN, SB
#TEST-VAL-SUB026-7037#REF# FCT SL Signaling speed restriction when entering SL
#TEST-VAL-SUB026-4740#REF# FCT SN SN/STM - V_MAIN
#TEST-VAL-SUB026-4F00#REF# FCT SR Signalling related speed restriction: FS/L1, SR/L1
#TEST-VAL-SUB026-7036#REF# FCT TR, PT Signaling speed restriction when entering TR/PT

#REQ-DESIGN-DATEN-0016:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Route Suitability Data' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The information is deleted when entering SH. PS can be entered via SH only.
The information is deleted when entering SB. SL can be entered via SB or PS only.
The information is deleted in TR. PT can be entered via TR only.
The verification for the ETCS modes PS, SL and PT is hence omitted. 

A transition from SH, NL and RV to a mode where the appropriated function is active is possible via SB only.
#TEST-VAL-SUB026-5969#REF# FCT FS, OS RUS information when entering FS/OS
#TEST-VAL-SUB026-5970#REF# FCT LS RUS information when entering LS
#TEST-VAL-SUB026-5975#REF# FCT RV RUS information when entering RV
#TEST-VAL-SUB026-5972#REF# FCT SB, NL RUS information when entering SB/NL
#TEST-VAL-SUB026-5971#REF# FCT SH RUS information when entering SH
#TEST-VAL-SUB026-5974#REF# FCT SN RUS information when entering SN
#TEST-VAL-SUB026-5964#REF# FCT SR FS, SR - Route Suitability Data processing
#TEST-VAL-SUB026-5967#REF# FCT TR SB - Route Suitability Data processing
#TEST-VAL-SUB026-5973#REF# FCT UN RUS information when entering UN

#REQ-UNISIG-SUB026-3637:01#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#REQ-UNISIG-SUB026-3321:01#REF#
Stored information 'Adhesion Factor information from trackside' shall be reset when entering the mode

SB, PS, SH, SL, NL, SN

Reset means reset to default value "non slippery"

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition to ETCS modes SL and PS is possible via modes where the Adhesion factor is reset. 
The verification for the ETCS modes SL, and PS is hence omitted.
The reset of the information when entering NL can be only verified via DMI indication as no target supervision is active in NL and the mode can
be left via SB only.
#TEST-VAL-SUB026-4664#REF# FCT FS, OS adhesion factor when entering FS, OS
#TEST-VAL-SUB026-4547#REF# FCT LS Adhesions factor from track side in LS, L1 FS->LS[72]
#TEST-VAL-SUB026-4666#REF# FCT NL adhesion factor when entering NL
#TEST-VAL-SUB026-7634#REF# FCT RV Trackside adhesion factor when mode changes to: RV
#TEST-VAL-SUB026-4D44#REF# FCT SB Adhesion factor when mode changes to: SB
#TEST-VAL-SUB026-4D46#REF# FCT SH Adhesion factor when mode changes to: SH
#TEST-VAL-SUB026-4485#REF# FCT SN adhesion factor when entering SN/STM
#TEST-VAL-SUB026-4D47#REF# FCT SR, UN Adhesion factor when mode changes to: SR/L2, UN/L0
#TEST-VAL-SUB026-4665#REF# FCT TR, PT adhesion factor when entering TR, PT, FS

#REQ-UNISIG-SUB026-3638:01#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#REQ-UNISIG-SUB026-3321:01#REF#
Stored information 'Adhesion Factor information from driver' shall be reset when entering the mode

SB, PS, SH, SL, NL

Reset means reset to default value "non slippery"

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
Rel. 8.0:
the mode dependency is changed for SH, SN, RV
TEST APPROACH:
A transition to ETCS modes SL and PS is possible via modes where the Adhesion factor is reset. 
The verification for the ETCS modes SL, and PS is hence omitted.
The reset of the information when entering NL can be only verified via DMI indication as no target supervision is active in NL and the mode can
be left via SB only.
#TEST-VAL-SUB026-4217#REF# FCT FS, OS, NL Driver Id and driver Adhesion factor FS, OS, NL
#TEST-VAL-SUB026-4582#REF# FCT LS Driver Id and driver Adhesion factor LS
#TEST-VAL-SUB026-4667#REF# FCT RV Driver Id and Track Adhesion factor RV
#TEST-VAL-SUB026-4669#REF# FCT SB driver Adhesion factor SB
#TEST-VAL-SUB026-7635#REF# FCT SH Driver adhesion factor when mode changes to: SH
#TEST-VAL-SUB026-4218#REF# FCT SR, UN, SN Driver Id and driver Adhesion factor SR, UN, SN
#TEST-VAL-SUB026-4668#REF# FCT TR, PT Driver Id and driver Adhesion factor TR/PT

#REQ-DESIGN-CR-0356:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Plain Text Information' shall be deleted when entering the mode

SB, PS, SH, SL, SN

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition to ETCS mode PS is possible via SH only.
The information is deleted when entering SH and new 'Plain Text Information' is rejected in SH.
The verification for the ETCS mode PS is hence omitted.
#TEST-VAL-SUB026-4138#REF# EET CFX00031344 , CFX00032980 Text message display at mode transition FS->SH
#TEST-VAL-SUB026-4130#REF# EET CFX00036935 Acceptance of information in conjunction with V_MAIN=0
#TEST-VAL-SUB026-4378#REF# FCT FS text message UN->FS
#TEST-VAL-SUB026-4542#REF# FCT LS text message FS->LS
#TEST-VAL-SUB026-4384#REF# FCT NL text message SB->NL
#TEST-VAL-SUB026-4377#REF# FCT OS text message FS->OS
#TEST-VAL-SUB026-4374#REF# FCT PT text message TR->PT
#TEST-VAL-SUB026-4376#REF# FCT RV text message FS->RV
#TEST-VAL-SUB026-4383#REF# FCT SB text message RV->SB
#TEST-VAL-SUB026-4385#REF# FCT SH text message FS->SH
#TEST-VAL-SUB026-4386#REF# FCT SL text message SB->SL
#TEST-VAL-SUB026-4748#REF# FCT SN Plain Text by transition to Mode SN
#TEST-VAL-SUB026-4375#REF# FCT SR text message PT->SR
#TEST-VAL-SUB026-4380#REF# FCT TR text message OS->TR
#TEST-VAL-SUB026-4381#REF# FCT UN text message SB->UN

#REQ-DESIGN-CR-0357:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Fixed Text Information' shall be deleted when entering the mode

SB, PS, SH, SL, SN

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition to ETCS mode PS is possible via SH only.
The information is deleted when entering SH and new 'Fixed Text Information' is rejected in SH.
The verification for the ETCS mode PS is hence omitted.
#TEST-VAL-SUB026-4378#REF# FCT FS text message UN->FS
#TEST-VAL-SUB026-4542#REF# FCT LS text message FS->LS
#TEST-VAL-SUB026-4384#REF# FCT NL text message SB->NL
#TEST-VAL-SUB026-4377#REF# FCT OS text message FS->OS
#TEST-VAL-SUB026-4374#REF# FCT PT text message TR->PT
#TEST-VAL-SUB026-4376#REF# FCT RV text message FS->RV
#TEST-VAL-SUB026-4383#REF# FCT SB text message RV->SB
#TEST-VAL-SUB026-4385#REF# FCT SH text message FS->SH
#TEST-VAL-SUB026-4386#REF# FCT SL text message SB->SL
#TEST-VAL-SUB026-4745#REF# FCT SN Fixed Text by transition to Mode SN
#TEST-VAL-SUB026-4375#REF# FCT SR text message PT->SR
#TEST-VAL-SUB026-4380#REF# FCT TR text message OS->TR
#TEST-VAL-SUB026-4381#REF# FCT UN text message SB->UN

#REQ-DESIGN-CR-0125:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Geographical Position' shall be deleted when entering the mode

PS, SH, SL, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition to ETCS mode PS is possible via SH only.
The information is deleted when entering SH and new 'Geographical Position' is rejected in SH.
The verification for the ETCS mode PS is hence omitted.
#TEST-VAL-SUB026-4264#REF# FCT FS, OS, SH Geographical Position Information FS->OS->FS->SH->SB
#TEST-VAL-SUB026-4546#REF# FCT LS GeoPos in LS/L2; L2 FS->LS[72]
#TEST-VAL-SUB026-4297#REF# FCT RV Geographical Position Information FS->RV->SB
#TEST-VAL-SUB026-4296#REF# FCT SN Geographical Position Information FS->SN->SB
#TEST-VAL-SUB026-4265#REF# FCT SR, UN, SB, NL, SL Geographical Position Information FS->SR->UN->SB->NL->SB->SL-SB
#TEST-VAL-SUB026-4266#REF# FCT TR, PT Geographical Position Information FS->TR->PT
#TEST-SWHWINT-SWVAL-FKT-0005#REF# EET error expectation Löschen der Geographical Position (GeoPos) - (NP)

#REQ-DESIGN-DATEN-0021:01#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Mode Profile' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The current Mode Profile is deleted/overridden by a new MA (with or without MP).
The verification of the deletion of the information is hence omitted.
The ETCS mode PT can be entered via TR only. The MA is deleted when entering TR.
The ETCS mode PS can be entered via SH only. The MA is deleted when entering SH.
The ETCS mode SL can be entered via SB and PS only. The MA is deleted when entering SB and PS.
A transition from ETCS modes NL and RV is possible only through mode SB. The MA is deleted when entering SB.
The verification for the ETCS modes PT, PS, SL, NL and RV is hence omitted.
#TEST-VAL-SUB026-5959#REF# FCT FS, OS, LS Evaluation of List of balises for SH area
#TEST-VAL-SUB026-4C33#REF# FCT SB Stored data: Mode Profile when mode changes to SB
#TEST-VAL-SUB026-4C31#REF# FCT SH Stored data: Mode Profile when mode changes to SH/L2
#TEST-VAL-SUB026-7814#REF# FCT SN Stored data: Mode Profile when mode changes to SN
#TEST-VAL-SUB026-4C30#REF# FCT SR Stored data: Mode Profile when mode changes to SR/L2, FS/L2
#TEST-VAL-SUB026-7805#REF# FCT TR Stored data: Mode Profile when mode changes to TR
#TEST-VAL-SUB026-4C35#REF# FCT UN Stored data: Mode Profile when mode changes to UN/L0, FS/L1

#REQ-DESIGN-DATEN-0022:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-RBCHandover-0004:01#REF#
Stored information 'RBC Transition Order' shall be deleted when entering the mode

SB, PS, SH, SL, UN, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.

remark: The deletion in UN and SN is resolved indirectly with #REQ-UNISIG-SUB026-3112#REF#.
TEST APPROACH:
Preliminary considerations
The RBC-ID and RBC-Phonenumber of the ACC-RBC is memorized, when the train reached the handover border with max safe front end (refer
#REQ-DESIGN-CR-0744:01#REF#).
The new ETCS mode can be entered before or after passing this location.
The deletion of a RBC transition after passing the RBC transition border aborts the exit procedure. 
The function Manage RBC/RBC Handover is active in the ETCS modes FS, LS, SR, OS, SL, NL and TR.

The modes SR, NL and TR are verified via #REQ-UNISIG-SUB026-010628#REF#
The SL can be entered and left via SB only. A RBC transition order received in SL is buffered for the mode transition to FS, LS or OS (refer
#REQ-UNISIG-SUB026-3140:01#REF#). 
The verification for the ETCS mode SL focuses on the deletion of the buffered RBC transition order.
The stored RBC ID/Phone Number is deleted when entering UN or SN. 
The mode RV can be left via SB only. The allowed train running direction is backward in RV.  
PS can be entered via SH only where the information "RBC transition order" is deleted, new information is only accepted for the current position
only (new RBC ID/Phone Number stored). The verification of the requirements for mode PS is hence omitted.

The following aspects have been identified:
1) mode change before passing the RBC border
1.1) SB
1.2) SH
1.3) SL
1.4) UN
1.5) SN
1.6) RV 
1.7) PT
1.8) FS
1.9) OS
1.10) LS
2) mode change after passing the RBC border 
That a 'RBC Transition Order' is not deleted due to a mode change to FS, OS, LS or PS is sufficiently verified through the verification of
aspect 1.
The verification for RV is executed for completeness reason only.
2.1) SB
2.2) SH
2.3) SL
2.4) UN
2.5) SN 
2.6) RV
#TEST-VAL-SUB026-8237#REF# FCT 1.1 Mode transition to SB in front of RBC transition border
#TEST-VAL-SUB026-8239#REF# FCT 1.2 Mode transition to SH in front of RBC transition border
#TEST-VAL-SUB026-8243#REF# FCT 1.3 Mode transition to SL in front of RBC transition border
#TEST-VAL-SUB026-8245#REF# FCT 1.4 Mode transition to UN in front of RBC transition border
#TEST-VAL-SUB026-8247#REF# FCT 1.5 Mode transition to SN in front of RBC transition border
#TEST-VAL-SUB026-8249#REF# FCT 1.6 Mode transition to RV in front of RBC transition border
#TEST-VAL-SUB026-8241#REF# FCT 1.7 Mode transition to PT in front of RBC transition border
#TEST-VAL-SUB026-8242#REF# FCT 1.8, 1.9, 1.10 Mode transition to FS, LS, OS in front of RBC transition border
#TEST-VAL-SUB026-8238#REF# FCT 2.1 Mode transition to SB after passing RBC transition border
#TEST-VAL-SUB026-8240#REF# FCT 2.2 Mode transition to SH after passing RBC transition border
#TEST-VAL-SUB026-8244#REF# FCT 2.3 Mode transition to SL after passing RBC transition border
#TEST-VAL-SUB026-8246#REF# FCT 2.4 Mode transition to UN after passing RBC transition border
#TEST-VAL-SUB026-8248#REF# FCT 2.5 Mode transition to UN after passing RBC transition border
#TEST-VAL-SUB026-8250#REF# FCT 2.6 Mode transition to RV after passing RBC transition border
#TEST-VAL-SUB026-4A93#REF# EET error expectation Stored RBC Handover; UN
#TEST-VAL-SUB026-8251#REF# EET error expectation P131 received in SH evaluated after leaving PS

#REQ-UNISIG-SUB026-010628#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-RBCHandover-0004:01#REF#
Stored information 'RBC Transition Order' shall be deleted when entering the mode

SR, NL, TR

and the train has not yet passed the RBC transition border with max safe front end.
TEST APPROACH:
The following aspects have been identified:
1) mode change before passing the RBC border
1.1) SR
1.2) NL
1.3) TR
2) mode change after passing the RBC border 
2.1) SR
2.2) NL
2.3) TR
#TEST-VAL-SUB026-8236#REF# FCT 1.1 Mode transition to SR in front of RBC transition border
#TEST-VAL-SUB026-8234#REF# FCT 1.2 Mode transition to NL in front of RBC transition border
#TEST-VAL-SUB026-8232#REF# FCT 1.3 Mode transition to TR in front of RBC transition border
#TEST-VAL-SUB026-3819#REF# FCT 2.1 Cancellation of RBC transition order due to mode change not taken into account after max safe front end passed the border
#TEST-VAL-SUB026-8235#REF# FCT 2.2 Mode transition to NL after passing RBC transition border with max save front end
#TEST-VAL-SUB026-8233#REF# FCT 2.3 Mode transition to TR after passing RBC transition border with max save front end
#TEST-VAL-SUB026-4A92#REF# EET error expectation Stored RBC Handover; NL
#TEST-VAL-SUB026-4H25#REF# EET error expectation Cancellation of RBC/RBC Handover deletes the HO transition buffer

#REQ-UNISIG-SUB026-3145:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Radio Infill Area information' shall be deleted when entering the mode

SB, PS, SH, SR, OS, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
radio infill is not to be realized

#REQ-DESIGN-DATEN-0024:03#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'EOLM information' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
realised by: #REQ-UNISIG-SUB026-010242#REF#

#REQ-DESIGN-CR-0477:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Track Conditions excluding sound horn, non stopping areas, tunnel stopping areas and big metal masses' shall be
reset when entering the mode

SB, PS, SH, SR, SL, UN, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
Regarding mode PS: the transition to this mode is possible via mode SH, where the ''Track Conditions excluding sound horn, non stopping areas,
tunnel stopping areas and big metal masses'' is reset and also not accepted.
The verification for this mode is hence omitted.
#TEST-VAL-SUB026-4583#REF# FCT LS TC Excluding Big Metal Masses (P68) FS/LS
#TEST-VAL-SUB026-5572#REF# FCT NL TC excl. BMM and sound horn, tunnel and non-stop areas retained in SR, but only processed after transition to NL
#TEST-VAL-SUB026-4B75#REF# FCT PT Acceptance of track conditions (P68, P39) in mode TR
#TEST-VAL-SUB026-4361#REF# FCT RV TC Excluding Big Metal Masses - RV
#TEST-VAL-SUB026-4305#REF# FCT SB, OS TC Excluding Big Metal Masses FS/SB/OS
#TEST-VAL-SUB026-7777#REF# FCT SH Reset TC excl. BMM in SH
#TEST-VAL-SUB026-4360#REF# FCT SL TC Excluding Big Metal Masses SB/SL
#TEST-VAL-SUB026-4310#REF# FCT SR, FS TC Excluding Big Metal Masses PT/SR/FS
#TEST-VAL-SUB026-5574#REF# FCT TR TC powerless section (pantograph) and traction system accepted in SR, supervised in TR
#TEST-VAL-SUB026-7778#REF# FCT UN, SN TC deleted entering UN/SN

#REQ-UNISIG-SUB026-3278#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
The track condition „Change of Traction System“ shall be deleted, if the condition for "Reset" for stored information 'Track
Conditions excluding sound horn, non stopping areas, tunnel stopping areas and big metal masses' is fulfilled.
UNISIG clarification:
Change of Traction System have not an initial state
TEST APPROACH:
Regarding mode PS: the transition to this mode is possible via mode SH, where the ''Track Conditions excluding sound horn, non stopping areas,
tunnel stopping areas and big metal masses'' is reset and also not accepted.
The verification for this mode is hence omitted.
#TEST-VAL-SUB026-4E08#REF# FCT LS TC Change of Traction Power in LS/L2
#TEST-VAL-SUB026-5572#REF# FCT NL TC excl. BMM and sound horn, tunnel and non-stop areas retained in SR, but only processed after transition to NL
#TEST-VAL-SUB026-4972#REF# FCT OS, FS Check table 4.5.2, 4.8.4, 4.10 TC Change of traction power (FS/OS/NL)
#TEST-VAL-SUB026-4B75#REF# FCT PT Acceptance of track conditions (P68, P39) in mode TR
#TEST-VAL-SUB026-4361#REF# FCT RV TC Excluding Big Metal Masses - RV
#TEST-VAL-SUB026-4834#REF# FCT SB Deletion of Change of Traction Power when entering SB
#TEST-VAL-SUB026-7777#REF# FCT SH Reset TC excl. BMM in SH
#TEST-VAL-SUB026-4360#REF# FCT SL TC Excluding Big Metal Masses SB/SL
#TEST-VAL-SUB026-4833#REF# FCT SR, UN, SN If the condition for Reset is fulfilled, the track condition Change of Traction System is deleted in SR/SN/UN
#TEST-VAL-SUB026-5574#REF# FCT TR TC powerless section (pantograph) and traction system accepted in SR, supervised in TR

#REQ-UNISIG-SUB026-010444#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Track Conditions sound horn, non stopping areas, tunnel stopping areas' shall be reset when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, PT, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
Regarding mode PS: the transition to this mode is possible via mode SH, where the ''Track Conditions excluding sound horn, non stopping areas,
tunnel stopping areas and big metal masses'' is reset and also not accepted.
The verification for this mode is hence omitted.
The track conditions 'sound horn, non stopping areas, tunnel stopping areas' are considered as belonging to the same equivalence class. 
#TEST-VAL-SUB026-7741#REF# FCT FS Handling of TCs Sound Horn, NSA, TSA in mode PT
#TEST-VAL-SUB026-7743#REF# FCT LS Handling of TCs Sound Horn, NSA, TSA in modes SR, LS
#TEST-VAL-SUB026-4830#REF# FCT OS Track condition excluding BMM not executed in SB but after transition to OS
#TEST-VAL-SUB026-4B75#REF# FCT PT Acceptance of track conditions (P68, P39) in mode TR
#TEST-VAL-SUB026-4361#REF# FCT RV TC Excluding Big Metal Masses - RV
#TEST-VAL-SUB026-7771#REF# FCT SB Stored TCs Sound Horn, TSA, NSA deleted because when mode changes to SB
#TEST-VAL-SUB026-7777#REF# FCT SH Reset TC excl. BMM in SH
#TEST-VAL-SUB026-4360#REF# FCT SL TC Excluding Big Metal Masses SB/SL
#TEST-VAL-SUB026-7772#REF# FCT SR, NL Deletion of TC Sound Horn, NSA, TSA when entering modes SR, NL
#TEST-VAL-SUB026-7773#REF# FCT TR Deletion of TCs Sound Horn, TSA, NSA when entering mode TR
#TEST-VAL-SUB026-7778#REF# FCT UN, SN TC deleted entering UN/SN

#REQ-DESIGN-CR-0478:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Track condition big metal masses' shall be reset when entering the mode

SB, PS, SH, SR, SL, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
#TEST-VAL-SUB026-4222#REF# FCT FS, OS BMM handling in FS/OS
#TEST-VAL-SUB026-4576#REF# FCT LS BMM handling in FS/LS
#TEST-VAL-SUB026-4227#REF# FCT NL BMM handling in SB/NL
#TEST-VAL-SUB026-7768#REF# FCT PS BMM information reset in PS
#TEST-VAL-SUB026-4226#REF# FCT RV BMM handling in FS/RV
#TEST-VAL-SUB026-4225#REF# FCT SB, SH BMM handling in SB/SH
#TEST-VAL-SUB026-4228#REF# FCT SL BMM handling in SB/SL
#TEST-VAL-SUB026-3788#REF# FCT SR Storaged BMM information for fixed distance deleted by mode change
#TEST-VAL-SUB026-4223#REF# FCT TR, PT BMM handling in SR/TR/PT in L1
#TEST-VAL-SUB026-4224#REF# FCT UN, SN BMM handling in UN/SN

#REQ-DESIGN-CR-0503:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Unconditional Emergency Stops' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
hint:
the change to FS/OS/LS with an current UES is not possible
TEST APPROACH:
A transition to FS, OS, LS with pending Unconditional Emergency Stop is excluded refer #REQ-DESIGN-CR-0502#REF#. 
A transition to NL and RV with pending Unconditional Emergency Stop is not possible as the acceptance of Unconditional Emergency Stop leads to a
transition to TR. Neither NL nor RV can be entered from TR or PT. 
The ETCS mode SL can be entered via SB only. Unconditional Emergency Stop is deleted when entering SB.
The ETCS mode PS can be entered via SH only. Unconditional Emergency Stop is deleted when entering SH 
The verification for the ETCS modes FS, OS, LS, NL, RV, SL and PS is hence omitted
#TEST-VAL-SUB026-4221#REF# FCT SB PT -> SB unconditional emergency stop message deleted
#TEST-VAL-SUB026-3863#REF# FCT SH Unconditional Emergency Stop when entering SH
#TEST-VAL-SUB026-4880#REF# FCT SN Deletion of unconditional EmergencyStop on entry into SN
#TEST-VAL-SUB026-4282#REF# FCT SR unconditional emergency stop message deleted when entering SR
#TEST-VAL-SUB026-4212#REF# FCT TR, PT unconditional emergency stop message TR, PT - MA accepted after emergency revoked
#TEST-VAL-SUB026-4A54#REF# FCT UN Unconditional Emergency Stop (cond [2]); UN, OS

#REQ-DESIGN-CR-0504:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Conditional Emergency Stops' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The ETCS mode SL can be entered via ETCS mode SB only. The information is deleted when entering SB and rejected in SB.
The ETCS mode PS can be entered via ETCS mode SH only. The information is deleted when entering SH and rejected in SH.
The verification for the ETCS modes SL and PS is hence omitted.
#TEST-VAL-SUB026-4901#REF# FCT FS Stored Conditional Emergency Stop; FS
#TEST-VAL-SUB026-4F15#REF# FCT LS Conditional Emergency Stop; when entering LS
#TEST-VAL-SUB026-4A65#REF# FCT NL Conditional Emergency Stop Inactive; NL
#TEST-VAL-SUB026-4A69#REF# FCT OS Stored Conditional Emergency Stop; OS
#TEST-VAL-SUB026-4284#REF# FCT RV Conditional Emergency Stop - RV
#TEST-VAL-SUB026-4A66#REF# FCT SB Conditional Emergency Stop Inactive; SB
#TEST-VAL-SUB026-4285#REF# FCT SH Conditional Emergency Stop - SH
#TEST-VAL-SUB026-4891#REF# FCT SN Deletion of conditionalEmergencyStop on entry into SN
#TEST-VAL-SUB026-4283#REF# FCT SR Conditional Emergency Stop - SR
#TEST-VAL-SUB026-4A67#REF# FCT TR, PT Conditional Emergency Stop; OS, TR, PT
#TEST-VAL-SUB026-4A71#REF# FCT UN Stored Conditional Emergency Stop; UN
#TEST-VAL-SUB026-4A63#REF# EET error expectation Conditional Emergency Stop; UN

#REQ-DESIGN-DATEN-0029:01#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'Train Position' shall be deleted when entering the mode
SF, IS
#TEST-VAL-SUB026-4570#REF# FCT IS mode transition LS->IS[1], processing Radio/BG message in IS
#TEST-VAL-SUB026-4845#REF# FCT LS, SH, NL, SL, UN, SR Train Location when entering LS, SH, NL, SL, SB, UN, SR
#TEST-VAL-SUB026-7693#REF# FCT PS Train Location when entering PS
#TEST-VAL-SUB026-4288#REF# FCT SB, OS, RV Last reported balise group identities transition FS(L2)-> RV(L2)-> SB(L2) -> OS(L2) ->FS(L2)
#TEST-VAL-SUB026-3716#REF# FCT SF Processing Radio/BG message in SF
#TEST-VAL-SUB026-4286#REF# FCT SN, TR, PT, FS acceptance of radio message with former LRBG FS, SN, TR, PT
#TEST-SWHWINT-SWVAL-FKT-0007#REF# EET error expectation Liste der gemeldeten LRBGs an das RBC werden nicht remanent gespeichert

#REQ-DESIGN-CR-0569:01#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#REQ-UNISIG-SUB026-3210:01#REF#
#REQ-UNISIG-SUB026-3705:01#REF#
#REQ-UNISIG-SUB026-010384#REF#
#REQ-UNISIG-SUB026-010385#REF#
#REQ-UNISIG-SUB026-010386#REF#
#REQ-DESIGN-CR-0625:01#REF#
#REQ-UNISIG-SUB026-010463#REF#
#REQ-UNISIG-SUB026-010464#REF#
regarding line 'Train Position':
If the train location information is invalid when leaving SB, than the train location information shall be set to unknown and the list of
reported balise group identities shall be deleted.
generalisation of the handling with an invalid train position after leaving SB

Rel. 8.0:
the exception "Exception: transition from SB to NP." is cancelled
#TEST-VAL-SUB026-4211#REF# FCT basic function SoM location invalid - set to unknown when leaving SB

#REQ-DESIGN-DATEN-0030:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Train Data' shall be revalidated when entering the mode

SB, SH, SL, NL

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
UNISIG clarification: It cannot be guaranteed that valid train data are corrected in SL, NL => the state of train data is set also TBR in SL,
NL
TEST APPROACH:
The general approach for all modes is the use of the data view window and an additional functionality. The additional functionality depends on
train data and includes:
- verification of the message 'Validated Train data' sent to RBC: for modes FS, LS, SR, UN, OS, SN, RV, TR, PT
- verification of the 'Start' and 'Override' buttons: for mode SB
- using engine length instead of train length for the supervision of the end point of a track condition : for mode NL
- using engine length instead of train length for the supervision of the distance to keep information in rear of the train in case of track
condition Big Metal Masses: for mode SH
- using engine length instead of train length for the supervision of an RBC transition border: for mode SL
Mode PS shall be omitted because the transition to PS is possible only through SH, where the information becomes invalid and cannot be
revalidated because the train data button is not available in SH. (see #REQ-SAS_DMI-003480#REF#).
#TEST-VAL-SUB026-4D63#REF# FCT FS, LS Train data, Train running number in LS/L2
#TEST-VAL-SUB026-4441#REF# FCT NL Train data in NL
#TEST-VAL-SUB026-4440#REF# FCT RV train data in RV
#TEST-VAL-SUB026-4442#REF# FCT SB, TR, PT train data in TR/PT
#TEST-VAL-SUB026-3B98#REF# FCT SH Train data in SH
#TEST-VAL-SUB026-7856#REF# FCT SL Train data in SL
#TEST-VAL-SUB026-4448#REF# FCT SN Train Data and Train Running Number in mode SN
#TEST-VAL-SUB026-4445#REF# FCT SR train data in SH, SR
#TEST-VAL-SUB026-4444#REF# FCT UN, OS train data in OS/UN

#REQ-UNISIG-SUB026-3728:01#REF# table.4.10 #REQ-UNISIG-SUB026-3726#REF#
#REQ-UNISIG-SUB026-3727#REF#
#REQ-UNISIG-SUB026-005248#REF#
#REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-TrainData-0003:01#REF#
If the status of train data is not "valid" the obu shall use the length of engine instead of the length of the train for the train
location functions.
TEST APPROACH:
The OBU can enter the modes SB, PS, SH, SL, NL, TR and SN without valid train data.
Following function have been identified which are on one hand active in one of these modes and are train length depended on the other hand.
1. PR to handing over RBC
2. PR due to leaving L2/3 area
3. location based PR
4. BMM management
5. Track condition management
#TEST-VAL-SUB026-4A84#REF# FCT 1 Manage RBC Handover; SL
#TEST-VAL-SUB026-4777#REF# FCT 2 PR due to leaving L2 area - NL train data not available
#TEST-VAL-SUB026-4872#REF# FCT 3 Engine length used for definition of PR location based on D_LOC, Q_LGTLOC=0 if no train data available
#TEST-VAL-SUB026-3B98#REF# FCT 4 Train data in SH
#TEST-VAL-SUB026-3830#REF# FCT 5 TC handling without valid train data

#REQ-UNISIG-SUB026-010246#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'ERTMS/ETCS level' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
#ANALYSE-VALUNISIG-4809#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-DESIGN-CR-0067:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'Table of priority of trackside supported levels' shall be deleted when entering the mode
SF, IS
TEST APPROACH:
The deletion of the 'Table of priority of trackside supported levels' when entering IS, SF has no functional relevance as these modes can be
leaved via NP only and cold movement protection is not part of R8 (refer realisation of #REQ-UNISIG-SUB026-010454#REF#). The test for the mode
IS and SF is omitted
#TEST-VAL-SUB026-4F16#REF# FCT LS Table of priority - Mode change FS-LS
#TEST-VAL-SUB026-3422#REF# FCT OS, FS, SH, NL table of priority - Mode change FS-OS-FS-SH-NL-SB
#TEST-VAL-SUB026-7711#REF# FCT PS Level choice according to Table of priority defined by P41 (LT announcement) in PS
#TEST-VAL-SUB026-3423#REF# FCT RV, SL table of priority - Mode change FS-RV-SB-SL-SB
#TEST-VAL-SUB026-3414#REF# FCT SB level_choice - Table of Priority [0/2] - mode change to SB
#TEST-VAL-SUB026-3425#REF# FCT SN table of priority - Mode change SN (Level transition ->STM)
#TEST-VAL-SUB026-3424#REF# FCT TR, PT, UN, SR table of priority - FS-TR-PT-SR-UN
#TEST-VAL-SUB026-3435#REF# EET error expectation Level Transition Order (L0/L1/L2) with NID_STM rejected
#TEST-SWHWINT-SWVAL-FKT-0006#REF# EET error expectation Löschen der Table of priority (NP)

#REQ-DESIGN-DATEN-0032:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Driver ID'
- shall be deleted when entering the mode SL
AND
shall be revalidated when entering the mode SB.

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
#TEST-VAL-SUB026-5482#REF# EET CFX00077897, CFX00041079 Driver Id when entering SL/SR
#TEST-VAL-SUB026-4582#REF# FCT FS, LS Driver Id and driver Adhesion factor LS
#TEST-VAL-SUB026-4441#REF# FCT NL Train data in NL
#TEST-VAL-SUB026-4217#REF# FCT OS Driver Id and driver Adhesion factor FS, OS, NL
#TEST-VAL-SUB026-3B57#REF# FCT PS Train running number in PS
#TEST-VAL-SUB026-4667#REF# FCT RV Driver Id and Track Adhesion factor RV
#TEST-VAL-SUB026-4445#REF# FCT SH, SR train data in SH, SR
#TEST-VAL-SUB026-7856#REF# FCT SL Train data in SL
#TEST-VAL-SUB026-4442#REF# FCT TR, PT, SB train data in TR/PT
#TEST-VAL-SUB026-4218#REF# FCT UN, SN Driver Id and driver Adhesion factor SR, UN, SN
#TEST-SWHWINT-SWVAL-FKT-0004#REF# EET error expectation Löschen driver ID, Train Data, Train Running Number (NP)

#REQ-UNISIG-SUB026-010249#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'Radio Network ID' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
#ANALYSE-VALUNISIG-4810#REF# FCT No additional functional requirement refer column FINALISED.
#TEST-VAL-SUB026-4962#REF# FCT FS, OS, RV, SB, SL Check table 4.10.1.3 Information->Radio Network Registration (FS/OS/RV/SB/SL)
#TEST-VAL-SUB026-8071#REF# FCT IS Radio Network ID when mode changes to IS
#TEST-VAL-SUB026-4B03#REF# FCT LS Check table 4.10.1.3 Information->Radio Network Registration (LS)
#TEST-VAL-SUB026-4965#REF# FCT NL Radio Network ID -> NL
#TEST-VAL-SUB026-5791#REF# FCT PS Evaluation of P45, system version and session termination order in PS
#TEST-VAL-SUB026-8072#REF# FCT SF Radio Network ID when mode changes to IS
#TEST-VAL-SUB026-8120#REF# FCT SN RBC Contact Information when entering SN
#TEST-VAL-SUB026-4964#REF# FCT SR, TR, PT, SH Check table 4.10.1.3 Information->Radio Network Registration (SR/TR/PT/SH)
#TEST-VAL-SUB026-8119#REF# FCT UN RBC Contact Information when entering UN/L0

#REQ-DESIGN-DATEN-0033:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'RBC ID/Phone Number' shall be deleted when entering the mode

UN, SN
#TEST-VAL-SUB026-4659#REF# FCT FS, OS, TR, PT, SR, NL RBC ID/Phone Number unchanged when entering FS/OS/TR/PT/SR/NL
#TEST-VAL-SUB026-8071#REF# FCT IS Radio Network ID when mode changes to IS
#TEST-VAL-SUB026-4B03#REF# FCT LS Check table 4.10.1.3 Information->Radio Network Registration (LS)
#TEST-VAL-SUB026-5783#REF# FCT PS CLTO received in SH evaluated after switching to SB via PS/SH
#TEST-VAL-SUB026-4660#REF# FCT RV, SL, SB RBC ID/Phone Number unchanged when entering RV/SL/SB
#TEST-VAL-SUB026-8072#REF# FCT SF Radio Network ID when mode changes to IS
#TEST-VAL-SUB026-4661#REF# FCT SH RBC ID/Phone Number unchanged when entering SH
#TEST-VAL-SUB026-8120#REF# FCT SN RBC Contact Information when entering SN
#TEST-VAL-SUB026-8119#REF# FCT UN RBC Contact Information when entering UN/L0
#TEST-VAL-SUB026-4488#REF# EET error expectation RBC Contact Information when entering SN/STM
#TEST-VAL-SUB026-4662#REF# EET error expectation RBC ID/Phone Number deleted when entering UN
#TEST-VAL-SUB026-4720#REF# EET error expectation RBC Contact Information when entering UN/L0

#REQ-UNISIG-SUB026-3732#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-RBCData-0005:01#REF#
RBC ID/Phone number in state "to be revalidated" shall be used outside mode SB also, when a session should be established.
relevant in mode SL and when a mode change in level 2 without an opened session
#TEST-VAL-SUB026-3825#REF# FCT basic function Entering SL/L2 - RBC ID/Phone number in state to be revalidated
#TEST-VAL-SUB026-3824#REF# EET error expectation OBU receives order to contact the last known RBC - RBC ID/Phone number in state to be revalidated

#REQ-DESIGN-DATEN-0034:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Train Running Number'
- shall be deleted when entering the mode SL
AND
shall be revalidated when entering the mode SB.

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
#TEST-VAL-SUB026-4442#REF# FCT FS, TR, PT, SB train data in TR/PT
#TEST-VAL-SUB026-4D63#REF# FCT LS Train data, Train running number in LS/L2
#TEST-VAL-SUB026-4441#REF# FCT NL Train data in NL
#TEST-VAL-SUB026-3B57#REF# FCT PS Train running number in PS
#TEST-VAL-SUB026-4440#REF# FCT RV train data in RV
#TEST-VAL-SUB026-4445#REF# FCT SH, SR , CFX00038527 train data in SH, SR
#TEST-VAL-SUB026-7856#REF# FCT SL Train data in SL
#TEST-VAL-SUB026-4448#REF# FCT SN Train Data and Train Running Number in mode SN
#TEST-VAL-SUB026-4444#REF# FCT UN, OS train data in OS/UN
#TEST-SWHWINT-SWVAL-FKT-0004#REF# EET error expectation Löschen driver ID, Train Data, Train Running Number (NP)

#REQ-DESIGN-CR-0358:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Reversing Area Information' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS modes SL and NL is possible only to mode SB. 
A transition from ETCS mode SH is possible only to modes PS, SB, NL, TR.
A transition from ETCS mode PS is possible only to modes SH, SB, SL.
The information is deleted when entering SH, PS, SB, UN, TR, or SN.
The verification for the ETCS modes SL, NL, SH, and PS is hence omitted.
#TEST-VAL-SUB026-4F17#REF# FCT LS Stored data: Reversing Area Information and Reversing Supervision Information LS/L2
#TEST-VAL-SUB026-4C23#REF# FCT OS Stored data: Reversing Area Information and Reversing Supervision Information OS/L2
#TEST-VAL-SUB026-4C19#REF# FCT RV Stored data: Reversing Area Information and Reversing Supervision Information when changing to RV/L2
#TEST-VAL-SUB026-4C26#REF# FCT SB Stored data: Reversing Area Information and Reversing Supervision Information when mode changes: SB/L2, FS/L2
#TEST-VAL-SUB026-4486#REF# FCT SN reversing area information when entering SN/STM
#TEST-VAL-SUB026-4C22#REF# FCT SR Stored data: Reversing Area Information and Reversing Supervision Information SR/L2, FS/L2
#TEST-VAL-SUB026-4C28#REF# FCT TR, PT Stored data: Reversing Area Information and Reversing Supervision Information when changing to TR/L2, PT/L2, FS/L2
#TEST-VAL-SUB026-4C27#REF# FCT UN,FS Stored data: Reversing Area Information and Reversing Supervision Information when changing to UN/L0, FS/L1, RV/L1

#REQ-DESIGN-DATEN-0037:02#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Reversing Supervision Information' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS modes SL and NL is possible only to mode SB. 
A transition from ETCS mode SH is possible only to modes PS, SB, NL, TR.
A transition from ETCS mode PS is possible only to modes SH, SB, SL.
The information is deleted when entering SH, PS, SB, UN, TR, or SN.
The verification for the ETCS modes SL, NL, SH, and PS is hence omitted.
#TEST-VAL-SUB026-4F17#REF# FCT LS Stored data: Reversing Area Information and Reversing Supervision Information LS/L2
#TEST-VAL-SUB026-4C23#REF# FCT OS Stored data: Reversing Area Information and Reversing Supervision Information OS/L2
#TEST-VAL-SUB026-4C19#REF# FCT RV Stored data: Reversing Area Information and Reversing Supervision Information when changing to RV/L2
#TEST-VAL-SUB026-4C26#REF# FCT SB, FS Stored data: Reversing Area Information and Reversing Supervision Information when mode changes: SB/L2, FS/L2
#TEST-VAL-SUB026-4486#REF# FCT SN reversing area information when entering SN/STM
#TEST-VAL-SUB026-4C22#REF# FCT SR Stored data: Reversing Area Information and Reversing Supervision Information SR/L2, FS/L2
#TEST-VAL-SUB026-4C28#REF# FCT TR, PT Stored data: Reversing Area Information and Reversing Supervision Information when changing to TR/L2, PT/L2, FS/L2
#TEST-VAL-SUB026-4C27#REF# FCT UN Stored data: Reversing Area Information and Reversing Supervision Information when changing to UN/L0, FS/L1, RV/L1

#REQ-DESIGN-CR-0471:03#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Track Ahead Free request' shall be deleted when entering the mode

SB, PS, SH, FS, LS, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
The information Track Ahead Free request is accepted in SB, LS, OS, SR and PT only. The appropriated function is active in SB, LS, OS, SR and PT
only.
The information Track Ahead Free request is deleted when entering SB.
A transition to a mode where the function is active from NL, SH, PS, IS, SL, SF and RV is possible via SB only.
Hence the verification focuses on the ETCS modes SB, FS, LS, SR, OS, UN, TR, PT and SN. The verification for mode PS is omitted as it can be
entered via SH only. The verification for mode PT is omitted as it can be entered via TR only.
#TEST-VAL-SUB026-5929#REF# FCT FS, TR Track Ahead Free request when changing modes
#TEST-VAL-SUB026-4D62#REF# FCT LS Manage Track Ahead Free request: when entering LS
#TEST-VAL-SUB026-4D37#REF# FCT SB Manage Track Ahead Free request: SB, NL
#TEST-VAL-SUB026-4D38#REF# FCT SH Manage Track Ahead Free request: SH
#TEST-VAL-SUB026-4289#REF# FCT SN Track Ahead Free Request - transition to STM
#TEST-VAL-SUB026-4D35#REF# FCT SR, OS Manage Track Ahead Free request: SR, OS
#TEST-VAL-SUB026-4D42#REF# FCT UN Track Ahead Free Request when mode changes to UN/L0

#REQ-UNISIG-SUB026-010114#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information "Permitted Braking Distance Information" shall be deleted when entering mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS mode SL, PS and PT is possible via modes where the PBD information is deleted and not accepted. The verification for the
ETCS modes SL, PS and PT is hence omitted.
From modes SH, NL and RV, the transition to a mode where the information is managed is possible only via modes where information is deleted.
However, the verification for these modes is provided here, to ensure that in these modes the information is not considered at all. 
#TEST-VAL-SUB026-3A96#REF# FCT FS, OS, LS PBD information when mode changes to FS, OS, LS
#TEST-VAL-SUB026-8122#REF# FCT NL PBD Information deleted when changing mode to NL
#TEST-VAL-SUB026-3A78#REF# FCT RV PBD Information in mode RV
#TEST-VAL-SUB026-3A75#REF# FCT SB, SN PBD Information deleted when changing mode to SB and SN
#TEST-VAL-SUB026-3A76#REF# FCT SH, UN PBD Information deleted when changing mode to SH and UN
#TEST-VAL-SUB026-3A74#REF# FCT SR FS/L1: acceptance of PBD Information from loop, deleted when entering mode SR
#TEST-VAL-SUB026-3A77#REF# FCT TR PBD Information deleted when entering mode TRIP

#REQ-UNISIG-SUB026-010446#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Level Crossing information' shall be deleted when entering the mode

SB, PS, SH, SR, SL, NL, UN, TR, SN, RV

note: when changing to the modes SF, IS, the handling of the information is not relevant for the application.
TEST APPROACH:
A transition from ETCS mode SL, PS and PT is possible via modes where the LX information is deleted and not accepted. The verification for the
ETCS modes SL, PS and PT is hence omitted.
From modes SH, NL and RV, the transition to a mode where the information is managed is possible only via modes where information is deleted.
However, the verification for these modes is provided here, to ensure that in these modes the information is not considered at all. 
#TEST-VAL-SUB026-7646#REF# FCT FS LX not protected message displayed on the DMI
#TEST-VAL-SUB026-7651#REF# FCT LS Acceptance of Level Crossing Information in L2
#TEST-VAL-SUB026-8123#REF# FCT NL LX Information deleted when changing mode to NL
#TEST-VAL-SUB026-7652#REF# FCT OS Acceptance of Level Crossing Information in L3
#TEST-VAL-SUB026-8125#REF# FCT RV LX Information in mode RV
#TEST-VAL-SUB026-7647#REF# FCT SB Level crossing information deleted when mode changes to SB and when desk is closed during SoM
#TEST-VAL-SUB026-8124#REF# FCT SH FS/L1: acceptance of LX Information from loop, deleted when entering mode SH
#TEST-VAL-SUB026-7649#REF# FCT SN Acceptance of Level Crossing Information in NTC
#TEST-VAL-SUB026-7650#REF# FCT SR Acceptance of Level Crossing Information in L1
#TEST-VAL-SUB026-7653#REF# FCT TR Acceptance of Level Crossing Information in PT
#TEST-VAL-SUB026-7648#REF# FCT UN Acceptance of Level Crossing Information in L0

#REQ-UNISIG-SUB026-010623#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'RBC/RIU System Version' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
#ANALYSE-VALUNISIG-7536#REF# FCT No additional functional requirement refer column FINALISED

#REQ-UNISIG-SUB026-010447#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'operated System Version' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
#ANALYSE-VALUNISIG-7529#REF# FCT No additional functional requirement refer column FINALISED

#REQ-UNISIG-SUB026-010448#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
#ANA-UNISIG-StoredInformation-0005:01#REF#
Stored information 'Virtual Balise Covers' shall remain unchanged, when mode is changed.

--- FINALISED ---
A mode dependency for the stored information have not to be implemented. Therefore this requirement can realized here.
#ANALYSE-VALUNISIG-5296#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-010449#REF# table.4.10 #REQ-UNISIG-SUB026-0762:01#REF#
Stored information 'Language used to display information to the driver' shall remain unchanged, when mode is changed.

--- FINALISED ---
The language, used to display information to the driver, is managed in the DMI. The EVC only activates/deactivates the button for the language
selection.

In ERA SRS DMI isn't define a mode dependency for the Language. The remanent storage is required in the SRS DMI (see /SRS_DMI/,
SRS_DMI_BL3-597).
#ANALYSE-VALUNISIG-5271#REF# FCT The DMI is in charge of language management refer #REQ-SRS_DMI-000565#REF#. The ASW provides a storage function refer #REQ-FFFIS_MMI-006168#REF#, #REQFFFIS_MMI-008849#REF#. The requirement has to be covered by [ESBO_SyValBer].

Chapter 4.11

#REQ-UNISIG-SUB026-005544#REF# 4.11.1.1 #REQ-UNISIG-SUB026-003695#REF#
Status of stored information, which is set to "Invalid" when No Power mode is entered, shall be affected, when relevant, by
information from the Cold Movement Detection function, according to the following table:

see #REQ-SRS-004415#REF# - Cold Movement Detection isn'realized now.
realised by: #REQ-UNISIG-SUB026-010242#REF#
realised by: #REQ-UNISIG-SUB026-010243#REF#
realised by: #REQ-UNISIG-SUB026-010245#REF#
realised by: #REQ-UNISIG-SUB026-010248#REF#
realised by: #REQ-UNISIG-SUB026-010247#REF#

#REQ-UNISIG-SUB026-010242#REF# 4.11.1.1 #REQ-UNISIG-SUB026-005544#REF#
#REQ-DESIGN-DATEN-0024:03#REF#
#REQ-UNISIG-SUB026-010244#REF#
As no cold movement is occurred, the remanent stored EOLM information, if available, shall be used after power on.
Otherwise this information shall be deleted after power on.

--- FINALISED ---
As no "Cold Movement Detection" function is realized, the remanent stored information EOLM and table of priority are set to unknown
after power on (see 4.11.).
Therefore it is not necessary to store the information EOLM and table of priority remanent.

#REQ-UNISIG-SUB026-010243#REF# 4.11.1.1 #REQ-UNISIG-SUB026-005544#REF#
#REQ-UNISIG-SUB026-010244#REF#
As no cold movement is occurred, the remanent stored information 'Table of priority of trackside supported levels', if available,
shall be used after power on.
Otherwise this information shall be deleted after power on.

--- FINALISED ---
As no "Cold Movement Detection" function is realized, the remanent stored information EOLM and table of priority are set to unknown
after power on (see 4.11.).
Therefore it is not necessary to store the information EOLM and table of priority remanent.

#REQ-UNISIG-SUB026-010245#REF# 4.11.1.1 #REQ-UNISIG-SUB026-005544#REF#
#REQ-UNISIG-SUB026-010244#REF#
The stored train position data shall be set invalid as inital state after power on.

Remark: No cold movement detection function is used currently.
#TEST-VAL-SUB026-4211#REF# FCT basic function SoM location invalid - set to unknown when leaving SB

#REQ-UNISIG-SUB026-010248#REF# 4.11.1.1 #REQ-UNISIG-SUB026-005544#REF#
#REQ-UNISIG-SUB026-010244#REF#
The stored ERTMS/ETCS Level shall be set invalid as inital state after power on.

Remark: No cold movement detection function is used currently.
#TEST-VAL-SUB026-4211#REF# FCT basic function SoM location invalid - set to unknown when leaving SB

#REQ-UNISIG-SUB026-010247#REF# 4.11.1.1 #REQ-UNISIG-SUB026-005544#REF#
#REQ-UNISIG-SUB026-010244#REF#
The stored RBC-ID/Phone number shall be set invalid as inital state after power on.

Remark: No cold movement detection function is used currently.
#TEST-VAL-SUB026-7940#REF# FCT basic function Remanent storage of Radio network ID

#REQ-UNISIG-SUB026-005549#REF# 4.11.1.3
If a cold movement has been detected, or the Cold Movement Detection function is not able to confirm that no cold movement has taken place, no
change of status of information to “valid” shall be made until it has been validated by a different means than cold movement detection.
this isn't a functional requirement
can be realized with 5.4.3.3
realised by: #REQ-UNISIG-SUB026-0256:01#REF#

Chapter 5

TEST APPROACH:
Note: The track description is verified via a mode independent test interface if not stated otherwise.
		

Chapter 5.3

#REQ-UNISIG-SUB026-3337#REF# 5.3.1.3
In case the condition(s) in chapter 4 triggering a mode transition is(are) fulfilled, this transition shall be executed even if not shown in the
chapter 5 procedures.
realised by: #REQ-UNISIG-SUB026-0247:01#REF#
realised by: #REQ-UNISIG-SUB026-2214:01#REF#

Chapter 5.4

#REQ-UNISIG-SUB026-0254:01#REF# 5.4.3.2












.

#DSC-UNISIG-SUB026-005732#REF#

Figure 1: Flowchart for “Start of Mission”
TEST APPROACH:
D33, D22, A23 and A38 are track side requirements.
realised by: #REQ-UNISIG-SUB026-1083:01#REF#
realised by: #REQ-UNISIG-SUB026-1084:01#REF#
realised by: #REQ-DESIGN-CR-0413:01#REF#
realised by: #REQ-DESIGN-CR-0412:01#REF#
realised by: #REQ-UNISIG-SUB026-010378#REF#
realised by: #REQ-UNISIG-SUB026-1086:01#REF#
realised by: #REQ-UNISIG-SUB026-1087:01#REF#
realised by: #REQ-UNISIG-SUB026-010380#REF#
realised by: #REQ-UNISIG-SUB026-010381#REF#
realised by: #REQ-DESIGN-CR-0415:01#REF#
realised by: #REQ-UNISIG-SUB026-010382#REF#
realised by: #REQ-UNISIG-SUB026-010383#REF#
realised by: #REQ-UNISIG-SUB026-1093#REF#
realised by: #REQ-DESIGN-CR-0416#REF#
realised by: #REQ-UNISIG-SUB026-1095#REF#
realised by: #REQ-UNISIG-SUB026-1097#REF#
realised by: #REQ-UNISIG-SUB026-1098:01#REF#
realised by: #REQ-UNISIG-SUB026-010384#REF#
realised by: #REQ-UNISIG-SUB026-010385#REF#
realised by: #REQ-UNISIG-SUB026-010386#REF#
realised by: #REQ-UNISIG-SUB026-1102:01#REF#
realised by: #REQ-DESIGN-CR-0536:03#REF#
realised by: #REQ-UNISIG-SUB026-1103#REF#
realised by: #REQ-DESIGN-CR-0417#REF#
realised by: #REQ-UNISIG-SUB026-1105#REF#
realised by: #REQ-DESIGN-CR-0418#REF#
realised by: #REQ-UNISIG-SUB026-1107#REF#
realised by: #REQ-DESIGN-CR-0419#REF#
realised by: #REQ-DESIGN-CR-0420#REF#
realised by: #REQ-DESIGN-CR-0495#REF#
realised by: #REQ-DESIGN-CR-0421#REF#

#REQ-UNISIG-SUB026-1083:01#REF# 5.4.3.2.S0 #REQ-UNISIG-SUB026-0254:01#REF#
The Start of Mission procedure shall be engaged when the ERTMS/ETCS on-board equipment is in Stand-By mode with a desk open and no communication
session is established or is being established.
TEST APPROACH:
Following aspects have been identified 
1) no communication session is established or is being established
2) communication session is established or is being established 

The mode dependency and the desk opening are implicit conditions for the SoM, the verification is hence omitted.
#TEST-VAL-SUB026-5430#REF# FCT 1 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open
#TEST-VAL-SUB026-4232#REF# FCT 2 transition SB-> NL in level 0

#REQ-UNISIG-SUB026-010553#REF# to.5.4.3.2.S0 #ANA-UNISIG-CR0560-0002:01#REF#
If the driver opens a desk and at least one communication session is established or is being established yet, all sessions shall be terminated.

remark: A possible session establishing due to position report of mode change to SB is aborted too.
UNISIG clarification:
- an open session should be closed. 
- the sessions termination is finished with the release of the safe radio connection  (refer 3.5.5.2 c).
TEST APPROACH:
The moment of 'Open Desk' determines the scenario at the beginning of SoM according to the situation of one or two active sessions.
1) EoM procedure not finished yet
1.1) Termination order not received yet
1.2) Termination order received 
1.3) M156 send
1.4) Release of safe connection ongoing 
2) Mode change from SL to SB
3) Two pending session
3.1) no termination order received
3.2) termination order from supervising RBC received 
3.3) termination order from non-supervising RBC received 
4) state of safe connection 
4.1) temporary outage of save connection (other mobile available)
4.2) permanent outage of save connection (other mobile available)
5) Opened Session in mode SB
6) SoM is started by Exit Shunting
#TEST-VAL-SUB026-4232#REF# FCT 1.1 transition SB-> NL in level 0
#TEST-VAL-SUB026-4234#REF# FCT 1.2 transition SB -> SH -> NL in level 0
#TEST-VAL-SUB026-5007#REF# FCT 1.3 delayed/no response from RBC to EoM
#TEST-VAL-SUB026-4231#REF# FCT 1.4 transition SB -> SH -> SB in level 0
#TEST-VAL-SUB026-4D30#REF# FCT 2 TSR: FS, SL
#TEST-VAL-SUB026-5608#REF# FCT 3.1 SoM S0 - OBU first terminates all existing sessions/connections (two connection up)
#TEST-VAL-SUB026-7200#REF# FCT 3.2 SoM S0 - OBU first terminates all existing sessions/connections (only termination order from sv RBC)
#TEST-VAL-SUB026-7201#REF# FCT 3.3 SoM S0 - OBU first terminates all existing sessions/connections (only termination order from non-sv RBC)
#TEST-VAL-SUB026-7202#REF# FCT 4.1 SoM A31 - OBU first terminates all existing sessions/connections (one connection temporary down)
#TEST-VAL-SUB026-5609#REF# FCT 4.2 SoM S0 - OBU first terminates all existing sessions/connections (one connection down)
#TEST-VAL-SUB026-3418#REF# FCT 5 Mode transition SL -> SB (SoM), session termination/establishment
#TEST-VAL-SUB026-4285#REF# FCT 6 Conditional Emergency Stop - SH
#TEST-VAL-SUB026-5523#REF# EET CFX00037626 SoM if pending/established communication session exists

#REQ-UNISIG-SUB026-1084:01#REF# 5.4.3.2.S1 #REQ-UNISIG-SUB026-0254:01#REF#
Depending on the status of the Driver-ID, the ERTMS/ETCS on-board equipment shall request the driver to enter the Driver-ID (if the Driver-ID is
unknown) or shall request the driver to revalidate or re-enter the Driver-ID (if the Driver-ID is invalid).
The ERTMS/ETCS on-board equipment shall offer the driver the possibility to enter/re-validate (depending on the status) the Train running
number.
The ERTMS/ETCS on-board equipment shall also offer the driver the possibility to set/remove a Virtual Balise Cover.
Once the Driver-ID is entered or revalidated (E1) (possibly further to the Train running number entry/revalidation and/or to Virtual Balise
Cover setting/removal), the process shall go to D2
TEST APPROACH:
The status unknown does not exist in the system because the application sets a default value at the start-up or at the revalidation.
The following aspects have to be distinguished: 
1) Enter Driver ID, status unknown (new ID)
2) Re-Validate DriverID, status invalid (ID remains unchanged)
3) Re-Enter DriverID, status invalid (ID is changed)
4) Re-Validate TRN, status invalid (value remains unchanged)
5) Re-Enter TRN, status invalid (value is changed)
6) Setting/Removal VBC
#TEST-VAL-SUB026-4210#REF# FCT 1 SoM Stored position not confirmed by RBC -> data deleted
#TEST-VAL-SUB026-5400#REF# FCT 2 SOM - L1/NL and L2/NL
#TEST-VAL-SUB026-3916#REF# FCT 3 Validity of Driver ID, Train Data and Train running number due to closing of desk during SoM
#TEST-VAL-SUB026-5472#REF# FCT 4 Mode transition L1 PT->SB - L2 SB->FS
#TEST-VAL-SUB026-5529#REF# FCT 5 Variable Q_STATUS is Invalid in PositionReport (RBC accepts)

#REQ-DESIGN-CR-0413:01#REF# 5.4.3.2.D2 #REQ-UNISIG-SUB026-0254:01#REF#
If both the stored position and the stored level are valid, the process shall go to D3
If the stored position or the stored level is “invalid” or “unknown”, the process shall go to S2
the mmi part is defined in ERA SRS DMI 11.7.2.4 D2
TEST APPROACH:
The level is set to a configured value for the first start up the condition level "unknown" can hence not be reached. 
The following aspects have to be distinguished: 
1) Yes path, Position and Level are valid
2) No path
2.1) Position is unknown, Level is invalid (First Start-up)
2.2) Position is invalid, Level is invalid(Start-up)
2.3) Position is invalid, level is valid
2.4) Position is unknown, level is valid
#TEST-VAL-SUB026-5430#REF# ECT 1 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open
#TEST-VAL-SUB026-5400#REF# ECT 2.1, 2.3 SOM - L1/NL and L2/NL
#TEST-VAL-SUB026-4211#REF# ECT 2.2 SoM location invalid - set to unknown when leaving SB
#TEST-VAL-SUB026-3218#REF# ECT 2.4 Input RBC contact data during SoM

#REQ-DESIGN-CR-0412:01#REF# 5.4.3.2.D3 #REQ-UNISIG-SUB026-0254:01#REF#
If the stored level is 2 or 3, the process shall go to D7
If the stored level is 0,1 or NTC, the process shall go to S10
Rel.8.0: former D1 is now defined as D3 and D7

the mmi part is defined in  ERA SRS DMI 11.7.2.4 D3
TEST APPROACH:
The following aspects have been identified:
1) current level is 0,1,NTC
2) current level is 2/3
#TEST-VAL-SUB026-4291#REF# ECT 1 SoM stored level L0, valid RBC data and location, to SH/L0 (E12)
#TEST-VAL-SUB026-5430#REF# ECT 2 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open

#REQ-UNISIG-SUB026-010378#REF# 5.4.3.2.D7 #REQ-UNISIG-SUB026-0254:01#REF#
If at least one Mobile Terminal is registered to a Radio Network, the process shall go to A31
If no Mobile Terminal is registered to a Radio Network, the process shall go to A29
the mmi part is defined in ERA SRS DMI 11.7.2.4 D7
TEST APPROACH:
The following aspects have to be distinguished: 
1) least one registered mobile
2) no registered mobile
#TEST-VAL-SUB026-5430#REF# ECT 1 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open
#TEST-VAL-SUB026-7082#REF# FCT 2 OBU informs driver if network registration not possible

#REQ-UNISIG-SUB026-1086:01#REF# 5.4.3.2.S2 #REQ-UNISIG-SUB026-0127#REF#
#REQ-UNISIG-SUB026-0254:01#REF#
If the status of the Level data is "unknown", the ERTMS/ETCS on-board equipment shall request the driver to enter it.
If the status of the Level data is "invalid", the ERTMS/ETCS on-board equipment shall request the driver to re-validate or re-enter
the ERTMS/ETCS level.
If the entered / re-validated level is 2 or 3, the process shall go to S3
If the entered / re-validated level is 0, 1 or one of proposed NTC level(s) (see 3.18.4.2 for the levels the driver is allowed to select), the
process shall go to S10
TEST APPROACH:
The level is set to a configured value for the first start up the condition level "unknown" can hence not be reached.
The following aspects have been identified:
1) Re-enter Level, status invalid (level is changed)
2) Re-validate Level, status invalid (level remains unchanged)
3) New Level is 2/3
4) New Level is 0,1,NTC
#TEST-VAL-SUB026-5472#REF# FCT 1 Mode transition L1 PT->SB - L2 SB->FS
#TEST-VAL-SUB026-4210#REF# FCT 2 SoM Stored position not confirmed by RBC -> data deleted
#TEST-VAL-SUB026-3218#REF# FCT 3 Input RBC contact data during SoM
#TEST-VAL-SUB026-5403#REF# FCT 4 SOM - L1/SR selection in S10

#REQ-UNISIG-SUB026-1087:01#REF# 5.4.3.2.S3 #REQ-DESIGN-CR-0734#REF#
#REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-010517#REF#
The ERTMS/ETCS on-board equipment shall offer the possibility to the driver to re-enter the Radio Network ID. If the driver elects to do so, the
on-board equipment shall acquire an alphanumeric list of available and allowed networks, based on a request to the Mobile Terminal(s) and:
∙	If this list is empty (E3) the process shall go to A29
∙	If the driver selects a new Radio Network ID from the proposed list, the registration of the Mobile Terminal(s) to this new Radio
Network shall be ordered and the status of the RBC-ID/phone number shall be immediately set to “unknown”.
If at least one Mobile Terminal is registered to a Radio Network, the ERTMS/ETCS on-board equipment shall offer the following options to the
driver for the RBC-ID/phone number:
∙	Only if the status of the RBC-ID/phone number is “invalid": order the ERTMS/ETCS on-board equipment to use the last stored
RBC-ID/phone number
∙	Order the ERTMS/ETCS on-board equipment to use the EIRENE short number (trackside call routing function)
∙	Enter the RBC-ID/phone number (if its status is "unknown"), or revalidate/re-enter it (if its status is “invalid”).
Once the driver has selected the first or second option or once data is validated (E5), the process shall go to A31
UNISIG clarification: 
if the radio network registration is not finished after a defined time, the process is going to A29 too (see clarification in REQ-SRS_DMI-004386
TEST APPROACH:
The aspects are determines by status of the network registration and the RbcData.
Aspects for enter Radio Network ID in Level 2/3:
1)   Re-entry of Radio Network ID
1.1)  empty network list 
1.2)  selection from list
2)   at least one mobile terminal is registered to a radio network
2.1)  unknown RBC-ID/phone number 
2.1.1) enter RBC-ID/phone number
2.2)  invalid RBC-ID/phone number
2.2.1) re-validate RBC-ID/phone number
2.2.2) re-enter RBC-ID/phone number
2.2.3) use the last stored RBC-ID/phone number
2.2.4) use the EIRENE short number
3) network registration timeout
Note:
1) A successfully mobile registration removes the display SystemStatusMsg "Radio network registration failed".
2) During the network registration the symbol "hour glass" is displayed.
#TEST-VAL-SUB026-7082#REF# FCT 1.1 OBU informs driver if network registration not possible
#TEST-VAL-SUB026-5536#REF# FCT 1.2 RadioNetworkId - selection of a radio network from the list
#TEST-VAL-SUB026-4295#REF# FCT 2.1.1, 2.2.1 RBC contact information entered during SoM memorized
#TEST-VAL-SUB026-4210#REF# FCT 2.2.2 SoM Stored position not confirmed by RBC -> data deleted
#TEST-VAL-SUB026-5408#REF# FCT 2.2.3 SoM status of information 'ERTMS/ETCS Level' and 'RBC ID/Phone Number'
#TEST-VAL-SUB026-5527#REF# FCT 2.2.4 SoM - deletion of stored position data on reception of Train Rejected
#TEST-VAL-SUB026-7209#REF# FCT 3 SoM S3 - Network registration timeout

#REQ-UNISIG-SUB026-010533#REF# to.5.4.3.2.S3
If the driver selects "Use short number" and current RBC data are available (i.e. "invalid" data), these RBC data shall be
deleted before the short number is used.
UNISIG clarification:
if the old data are not deleted, it is not clear whether the old RBC ID should be used or not.
#TEST-VAL-SUB026-5527#REF# FCT basic function SoM - deletion of stored position data on reception of Train Rejected

#REQ-UNISIG-SUB026-010627#REF# to.5.4.3.2
The determination of the list of available and allowed networks shall be limited to a parameterizable time.
internal decision, that a termination of waiting of the list of available and allowed networks has to be possible.
TEST APPROACH:
The contents of the list are dependent on the process of the scanning.
The scanning delivers a list of found networks (one or more) in case of success.
In the case of a timeout the scanning delivers a list with the networks found up to now, in the worst case an empty list.
In case of no response from the scanning the application sends an empty list too.

The following aspects have been identified:
1) Immediate response with filled list (two items)
2) response in time with filled list (more than two items)
3) response to the timeout with empty list
4) no response, after timeout empty list
#TEST-VAL-SUB026-5536#REF# FCT 1 RadioNetworkId - selection of a radio network from the list
#TEST-VAL-SUB026-7209#REF# FCT 2 SoM S3 - Network registration timeout
#TEST-VAL-SUB026-7082#REF# FCT 3, 4 OBU informs driver if network registration not possible
#TEST-VAL-SUB026-4208#REF# EET error expectation SoM stored train location confirmed by RBC
#TEST-VAL-SUB026-4H97#REF# EET error expectation SoM PR with invalid position repeated without response, with defined waiting time, definded times -> session terminated

#REQ-UNISIG-SUB026-010380#REF# 5.4.3.2.A29 #REQ-UNISIG-SUB026-0254:01#REF#
The ERTMS/ETCS on-board equipment shall inform the driver that the Radio Network registration has failed
This condition leads to S10 (the driver has to unlock the situation to continue e.g. selection of new level)
see S3 - is only relevant, if the list of available networks is empty.
=> can be directly realized with ERA SRS DMI 11.7.2.4 A29
#TEST-VAL-SUB026-7082#REF# FCT basic function OBU informs driver if network registration not possible

#REQ-UNISIG-SUB026-010381#REF# 5.4.3.2.S10 #REQ-UNISIG-SUB026-0254:01#REF#
The ERTMS/ETCS on-board equipment shall offer the possibility to the driver to select SH, NL, or to select Train Data Entry.
  If the driver selects SH (E12), the process shall continue in the same way as the procedure “Shunting initiated by the driver”.
  If, in level 2 or 3, the RBC rejects the request for Shunting (E13), the process shall go back to S10.
  If the driver selects NL (E10) then the ERTMS/ETCS on-board equipment shall immediately switch to Non Leading mode (refer to SRS chapter 4,
transition between modes: transition [46]). The mission starts in NL mode (if level is 2 or 3, the ERTMS/ETCS on-board equipment also reports
the change of mode to the RBC).
  If the driver selects Train Data Entry (E11), the process shall go to S12
  Following E10, E12,  if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”)
realised by: #REQ-DESIGN-CR-0414:01#REF#
realised by: #REQ-UNISIG-SUB026-3210:01#REF#

#REQ-DESIGN-CR-0414:01#REF# 5.4.3.2.S10 #REQ-UNISIG-SUB026-010381#REF#
The ERTMS/ETCS on-board equipment shall offer the possibility to the driver to select SH, NL, or to select Train Data Entry.
  If the driver selects SH (E12), the process shall continue in the same way as the procedure “Shunting initiated by the driver”.
  If, in level 2 or 3, the RBC rejects the request for Shunting (E13), the process shall go back to S10.
  If the driver selects NL (E10) then the ERTMS/ETCS on-board equipment shall immediately switch to Non Leading mode (refer to SRS chapter 4,
transition between modes: transition [46]). The mission starts in NL mode (if level is 2 or 3, the ERTMS/ETCS on-board equipment also reports
the change of mode to the RBC).
  If the driver selects Train Data Entry (E11), the process shall go to S12
TEST APPROACH:
The following aspects have to be distinguished: 
1) Selection SH
2) Request for Shunting is rejected by RBC in Level2/3
3) Selection NL 
4) Selection Train Data Entry 
#TEST-VAL-SUB026-5429#REF# FCT 1, 2 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open with a future version
#TEST-VAL-SUB026-4232#REF# FCT 3 transition SB-> NL in level 0
#TEST-VAL-SUB026-3218#REF# FCT 4 Input RBC contact data during SoM
#TEST-VAL-SUB026-5427#REF# EET error expectation SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session not open

#REQ-UNISIG-SUB026-3210:01#REF# 5.4.3.2.S10 #REQ-UNISIG-SUB026-010381#REF#
Following E10, E12,  if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”).
realised by: #REQ-DESIGN-CR-0569:01#REF#

#REQ-DESIGN-CR-0415:01#REF# 5.4.3.2.S12 #REQ-UNISIG-SUB026-0122:02#REF#
#REQ-UNISIG-SUB026-0254:01#REF#
The ERTMS/ETCS on-board equipment shall request the driver to enter/revalidate the Train Data that requires driver validation.
Once Train Data is stored and validated (E16), the process shall go to D12
TEST APPROACH:
The train data are set to a parameterizable default values the condition train data "unknown" can hence not be reached refer
#REQ-BA-Erweiterung-0011:02#REF#. The following aspects have to be distinguished: 
1) Re-Validate TD, status invalid (value remains unchanged)
2) Re-Enter TD, status invalid (value is changed)
#TEST-VAL-SUB026-5401#REF# FCT 1 SOM - L2/OS
#TEST-VAL-SUB026-4210#REF# FCT 2 SoM Stored position not confirmed by RBC -> data deleted

#REQ-UNISIG-SUB026-010382#REF# 5.4.3.2.D12 #REQ-UNISIG-SUB026-0254:01#REF#
If Train running number is valid, the process shall go to D10
If Train running number is “unknown” or “invalid”, the process shall go to S13
TEST APPROACH:
The status unknown does not exist in the system because the application sets a default value at the start-up or at the revalidation.
The following aspects have been identified:
1) TRN status is invalid
2) TRN status is valid 
#TEST-VAL-SUB026-5401#REF# ECT 1 SOM - L2/OS
#TEST-VAL-SUB026-5406#REF# ECT 2 SOM - L2/FS

#REQ-UNISIG-SUB026-010383#REF# 5.4.3.2.S13 #REQ-UNISIG-SUB026-0254:01#REF#
If the status of the Train running number is "unknown" or “invalid”, the ERTMS/ETCS on-board equipment shall request the driver to
enter/re-validate the Train running number now.
Once Train running number is entered/re-validated (E18), the process shall go to D10.
TEST APPROACH:
The status unknown does not exist in the system because the application sets a default value at the start-up or at the revalidation.
The following aspects have to be distinguished: 
1) Re-Validate TRN, status invalid (value remains unchanged)
2) Re-Enter TRN, status invalid (value is changed)
#TEST-VAL-SUB026-5401#REF# FCT 1 SOM - L2/OS
#TEST-VAL-SUB026-5407#REF# FCT 2 SoM - L0/UN (nach: RBC rejects Train (A38))

#REQ-UNISIG-SUB026-1093#REF# 5.4.3.2.D10 #REQ-UNISIG-SUB026-0254:01#REF#
When the validated level is 2/3, the process shall go to D11
When the validated level is 0,1 or NTC, the process shall go to S20
TEST APPROACH:
The following aspects have been identified:
1) current level is LNTC/L0/L1
2) current level is L2/3
#TEST-VAL-SUB026-4949#REF# ECT 1 Transition from SB to SN
#TEST-VAL-SUB026-5404#REF# ECT 2 SOM - L2/SR

#REQ-DESIGN-CR-0416#REF# 5.4.3.2.D11 #REQ-UNISIG-SUB026-0254:01#REF#
When the session is open, the process shall go to S11, otherwise it shall go to S10
TEST APPROACH:
The following aspects have been identified:
1) session is open
2) no session is open
#TEST-VAL-SUB026-5404#REF# ECT 1 SOM - L2/SR
#TEST-VAL-SUB026-5405#REF# ECT 2 SoM - L2/SR via Override in S10

#REQ-UNISIG-SUB026-1095#REF# 5.4.3.2.S11 #REQ-UNISIG-SUB026-0254:01#REF#
#ANA-UNISIG-SoM-0002#REF#
The ERTMS/ETCS on-board equipment shall send Train Data to the RBC.
When the RBC acknowledges Train Data (E14), then the ERTMS/ETCS onboard equipment shall go to the step S20.
UNISIG clarifications: 
- the train data are send only, if they are entered or changed (see 3.18.3.4)

- if the session is terminated (i.e. safe radio connection is lost), the next step (S10) should be started only, if the safe radio connection is
closed too.

deviation from SoM procedure: the validated train data are immediately send to the RBC also, when the train running number is still invalid
TEST APPROACH:
The aspects of this step are determines by RBC version, the changing of the data and the communication situation.

The Train Data are sent before the TRN is valid in case of a RBC with version 2 because of the defined deviation.

The following aspects have been identified:
1) Normal successful Train Data Report
2) no RBC response (M8)
3) temporary loss of the safe connection (Session is continued)
4) permanent loss of the safe connection (Session is down)
5) Sending the Train Data before TRN is valid
#TEST-VAL-SUB026-3218#REF# FCT 1 Input RBC contact data during SoM
#TEST-VAL-SUB026-7031#REF# FCT 2 SoM S11, RBC does not send acknowledge train data
#TEST-VAL-SUB026-7203#REF# FCT 3 SoM S11, temporaray loss of safe connection
#TEST-VAL-SUB026-7204#REF# FCT 4 SoM S11, permanent loss of safe connection
#TEST-VAL-SUB026-4208#REF# FCT 5 SoM stored train location confirmed by RBC
#TEST-VAL-SUB026-8280#REF# FCT CFX00190811 Train data input while answer to M129 pending

#REQ-UNISIG-SUB026-1097#REF# 5.4.3.2.S20 #REQ-UNISIG-SUB026-0254:01#REF#
The ERTMS/ETCS on-board equipment shall offer the possibility to the driver to select “Start”
  When the validated level is NTC and the driver selects "start" (E20), the process shall go to S22
  When the validated level is 0 and the driver selects "start" (E21), the process shall go to S23
  When the validated level is 1 and the driver selects "start" (E22), the process shall go to S24
  When the validated level is 2 or 3 and the driver selects "start" (E24), the process shall go to S21
realised by: #REQ-UNISIG-SUB026-010535#REF#
realised by: #REQ-UNISIG-SUB026-1098:01#REF#
realised by: #REQ-UNISIG-SUB026-1099:02#REF#
realised by: #REQ-UNISIG-SUB026-1100:01#REF#
realised by: #REQ-UNISIG-SUB026-010456#REF#
realised by: #REQ-UNISIG-SUB026-010455#REF#

#REQ-UNISIG-SUB026-010535#REF# 5.4.3.2.S20 #REQ-UNISIG-SUB026-1097#REF#
The ERTMS/ETCS on-board equipment shall offer the possibility to the driver to select “Start”.
#TEST-VAL-SUB026-5472#REF# FCT basic function Mode transition L1 PT->SB - L2 SB->FS

#REQ-UNISIG-SUB026-1098:01#REF# 5.4.3.2.S21 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-1097#REF#
#REQ-UNISIG-SUB026-010465#REF#
The ERTMS/ETCS on-board equipment shall send an MA request to the RBC and wait.
If an SR authorisation is received from RBC (E26), the process shall go to S24
If an MA allowing OS/LS/SH is received from RBC (E27), the process shall go to S25
If an MA allowing FS is received from RBC (E29), the mission starts in Full Supervision mode (refer to SRS chapter 4, transitions between modes:
transition from SB to FS)
The MA Request after Start is realized with 3.8.2.7

the change to mode FS is conformed with mode transition condition [10]
realised by: #REQ-UNISIG-SUB026-0475#REF#
realised by: #REQ-UNISIG-SUB026-2217#REF#
realised by: #REQ-UNISIG-SUB026-010455#REF#
realised by: #REQ-UNISIG-SUB026-1102:01#REF#

#REQ-UNISIG-SUB026-010384#REF# 5.4.3.2.S22 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-010403#REF#
#REQ-UNISIG-SUB026-010420#REF#
#REQ-UNISIG-SUB026-010465#REF#
The ERTMS/ETCS on-board equipment shall request an acknowledgement from the driver for running under supervision of the selected National
System. When the driver acknowledges (E30) , the mission starts in SN mode  (refer to SRS chapter 4, transitions between modes).
Following E30, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”)
the change to mode SN after acknowledegement is conformed with mode transition condition [58]

the deletion of invalid train position data after leaving is generalised
realised by: #REQ-DESIGN-CR-0110:02#REF#
realised by: #REQ-DESIGN-CR-0569:01#REF#
realised by: #REQ-UNISIG-SUB026-1099:02#REF#

#REQ-UNISIG-SUB026-1099:02#REF# 5.4.3.2.S22 #REQ-UNISIG-SUB026-1097#REF#
#REQ-UNISIG-SUB026-010384#REF#
The obu shall require an acknowledgement from the driver for running in mode SN, if
- the driver selected "Start"
AND
- mode=SB
AND
- ETCS-Level=STM
see also subset 35
the selected STM has to be done in HS State before the ack is required
TEST APPROACH:
The selection Start is possible in S20, if Train Data and TRN are valid also in S10:
1) selection start in S10 with valid TD/TRN
2) selection start in S10 with invalid TD/TRN
3) selection start in S20 (implies valid TD/TRN)
#TEST-VAL-SUB026-7592#REF# FCT 1, 2 Check of M_VERSION=127 by radio
#TEST-VAL-SUB026-4949#REF# FCT 3 Transition from SB to SN

#REQ-UNISIG-SUB026-010385#REF# 5.4.3.2.S23 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-3587#REF#
#REQ-UNISIG-SUB026-010421#REF#
#REQ-UNISIG-SUB026-010465#REF#
The ERTMS/ETCS on-board equipment shall require an acknowledgement from the driver for running in Unfitted mode. When the driver acknowledges
(E31), the mission starts in Unfitted mode (refer to SRS chapter 4, transitions between modes: transition from SB to UN)
Following E31, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”)”
the change to mode UN after acknowledegement is conformed with mode transition condition [60]

the deletion of invalid train position data after leaving is generalised
realised by: #REQ-UNISIG-SUB026-2223#REF#
realised by: #REQ-DESIGN-CR-0569:01#REF#
realised by: #REQ-UNISIG-SUB026-1100:01#REF#

#REQ-UNISIG-SUB026-1100:01#REF# 5.4.3.2.S23 #REQ-UNISIG-SUB026-1097#REF#
#REQ-UNISIG-SUB026-010385#REF#
The obu shall require an acknowledgement from the driver for running in mode UNFITTED, if
- the driver selected "Start"
AND
- mode=SB
AND
- ETCS-Level=0
TEST APPROACH:
The selection Start is possible in S20, if Train Data and TRN are valid also in S10:
1) selection start in S10 with valid TD/TRN
2) selection start in S10 with invalid TD/TRN
3) selection start in S20 (implies valid TD/TRN)
#TEST-VAL-SUB026-3262#REF# FCT 1, 2 Connection to RBC can not be established during SoM
#TEST-VAL-SUB026-5407#REF# FCT 3 SoM - L0/UN (nach: RBC rejects Train (A38))

#REQ-UNISIG-SUB026-010386#REF# 5.4.3.2.S24 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-3588:01#REF#
#REQ-UNISIG-SUB026-010418#REF#
#REQ-UNISIG-SUB026-010465#REF#
The ERTMS/ETCS on-board equipment shall require an acknowledgement from the driver for running in Staff Responsible mode. When the driver
acknowledges (E32), the mission starts in SR mode (refer to SRS chapter 4, transitions between modes: transition from SB to SR)
Following E32, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”)”
the change to mode SR after acknowledegement is conformed with mode transition condition [8]

the deletion of invalid train position data after leaving is generalised
realised by: #REQ-UNISIG-SUB026-2218#REF#
realised by: #REQ-DESIGN-CR-0569:01#REF#
realised by: #REQ-UNISIG-SUB026-010456#REF#
realised by: #REQ-UNISIG-SUB026-010455#REF#
realised by: #REQ-UNISIG-SUB026-010457#REF#

#REQ-UNISIG-SUB026-010456#REF# 5.4.3.2.S24 #REQ-UNISIG-SUB026-1097#REF#
#REQ-UNISIG-SUB026-010386#REF#
The obu shall require an acknowledgement from the driver for running in mode STAFF RESPONSIBLE, if
- the driver selected "Start"
AND
- mode=SB
AND
- ETCS-Level=1
TEST APPROACH:
The selection Start is possible in S20, if Train Data and TRN are valid also in S10:
1) selection start in S10 with valid TD/TRN
2) selection start in S10 with invalid TD/TRN
3) selection start in S20 (implies valid TD/TRN)
#TEST-VAL-SUB026-5403#REF# FCT 1 SOM - L1/SR selection in S10
#TEST-VAL-SUB026-7207#REF# FCT 2, 3 SOM - L1/SR selection in S20

#REQ-UNISIG-SUB026-010455#REF# 5.4.3.2.S24 #REQ-UNISIG-SUB026-1097#REF#
#REQ-UNISIG-SUB026-1098:01#REF#
#REQ-UNISIG-SUB026-010386#REF#
The obu shall require an acknowledgement from the driver for running in mode STAFF RESPONSIBLE, if
- the driver selected "Start"
AND
- mode=SB
AND
- ETCS-Level=2/3
AND
- a SR authorisation is received from RBC
TEST APPROACH:
The selection Start is possible in S20, if Train Data and TRN are valid also in S10:
1) selection start in S10 with invalid TD/TRN
2) selection start in S20 (implies valid TD/TRN)
#TEST-VAL-SUB026-5404#REF# FCT 1, 2 SOM - L2/SR

#REQ-UNISIG-SUB026-010457#REF# 5.4.3.2.S24 #REQ-UNISIG-SUB026-010386#REF#
The obu shall require an acknowledgement from the driver for running in mode STAFF RESPONSIBLE, if
- the driver selected "Start"
AND
- mode=SB
AND
- ETCS-Level=2/3
AND
- no communication session to a RBC is open
TEST APPROACH:
The selection Start is possible in S20, if Train Data and TRN are valid also in S10:
1) selection start in S10 with valid TD/TRN
2) selection start in S10 with invalid TD/TRN
#TEST-VAL-SUB026-3B17#REF# ECT 1, 2 Establishing communication session after SoM - degraded situation

#REQ-UNISIG-SUB026-1102:01#REF# 5.4.3.2.S25 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-1098:01#REF#
The ERTMS/ETCS on-board equipment shall require an acknowledgement from the driver for running in On Sight/Limited Supervision/Shunting mode.
When the driver acknowledges (E33), the mission starts in On Sight/Limited Supervision/Shunting mode (refer to SRS chapter 4, transitions
between modes: transition from SB to OS, LS or SH)
realizes through SH-/OS-/LS-Procedure (see 5.7.4.1, 5.9.5.1, 5.19.5.1)
realised by: #REQ-DESIGN-CR-0061#REF#
realised by: #REQ-DESIGN-CR-0054#REF#
realised by: #REQ-UNISIG-SUB026-3529#REF#

#REQ-DESIGN-CR-0536:03#REF# 5.4.3.2.A31 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-DESIGN-CR-0363:01#REF#
The ERTMS/ETCS on-board equipment shall open the session with the RBC.

Exceptions:
The on-board shall not establish a new communication session with a RBC in case a communication session is currently being established or is
already established with this RBC.

If no RBC data are available and the driver didn't selected "Use Short Number", the process shall go directly to A32.
UNISIG clarification:
It's possible, that no RBC data are available and the driver didn't selected "Use Short Number". In this case the procedure
is continuesed directly with A32, respectively S10.
TEST APPROACH:
The following aspects have been identified for the session establishment:
1) A31 entered from D7 (state of RBC data)
1.1) RBC data available 
1.2) RBC data not available 
2) A31 entered from S3 (session state)
2.1) session already establsihed
2.2) session establishment ongoing 
2.3) new session has to be establsihed

Note:
1) The hour glass symbol is displayed during the complete procedure step.
2) The SystemStatusMsg "Trackside not compatible" is removed at the begin of the process step.
3) The StatusSymbols "Connection Up" is displayed at the end of successfully session establishment.
#TEST-VAL-SUB026-5430#REF# FCT 1.1 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open
#TEST-VAL-SUB026-7208#REF# FCT 1.2 SoM - no session establishment in level 2 with unknown RbcData
#TEST-VAL-SUB026-5480#REF# FCT 2.1 Accidental loss of an already open session SoM (S20) - maximal time to consider the communication session still established exceeded
#TEST-VAL-SUB026-8254#REF# FCT 2.2 Entering S3/A31 while setup of communicaiton session ongoing
#TEST-VAL-SUB026-4295#REF# FCT 2.3 RBC contact information entered during SoM memorized

#REQ-UNISIG-SUB026-1103#REF# 5.4.3.2.D31 #REQ-UNISIG-SUB026-0254:01#REF#
If the opening of the session is successful, the process shall go to D32
If the opening of the session has failed, the process shall go to A32
UNISIG clarification: 
the next step (S10) should be started only, if the safe radio connection is closed too.
TEST APPROACH:
The following aspects have been identified:
1) opening of the session is successful
1.1) Normal successful session establishment
1.2) Establishment of session after repetition of connection request
1.3) Establishment of session after repetition of M155
1.4) Establishment of session after temporary connection outage
2) opening of the session has failed 
2.1) Safe connection cannot be established
2.2) No RBC response (The connection will be terminated after maximum of repetition of M155)
2.3) Permanent connection outage during repetition of M155
2.4) RBC version is not compatible (The termination of session is part of A32)
#TEST-VAL-SUB026-5430#REF# FCT 1.1 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open
#TEST-VAL-SUB026-3B18#REF# FCT 1.2, 1.3 Troubleshooting during establishment a communication session at SoM in A31
#TEST-VAL-SUB026-3218#REF# ECT 1.4 Input RBC contact data during SoM
#TEST-VAL-SUB026-3262#REF# FCT 2.1 Connection to RBC can not be established during SoM
#TEST-VAL-SUB026-5405#REF# FCT 2.2 SoM - L2/SR via Override in S10
#TEST-VAL-SUB026-3B17#REF# FCT 2.3 Establishing communication session after SoM - degraded situation
#TEST-VAL-SUB026-5427#REF# FCT 2.4 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session not open

#REQ-DESIGN-CR-0417#REF# 5.4.3.2.A32 #REQ-UNISIG-SUB026-0254:01#REF#
The driver shall be informed when the on-board equipment fails to open a radio session.
Opening  of a radio session has failed if
  No connection to the RBC can be established (see section 3.5.3.7) OR
  The ERTMS/ETCS on-board equipment, based on the system configuration reported by the RBC, decides that compatibility is not ensured and
terminates the communication session
This condition leads to  S10 (The driver has to unlock the situation to continue e.g. selection of new level).
clarification:
in first point the "normal" indication of the connection state is meant

in second point the text message "Trackside not compatible" is dipslayed (see A32 in ERA SRS DMI.
TEST APPROACH:
Faults during the session establishment are shown to the driver by StatusSymbols "Connection Lost/Set-Up failed" and SystemStatusMsg "Trackside
not compatible".
The following aspects have been identified:
1) Display StatusSymbols "Connection Lost/Set-Up failed" 
2) Display SystemStatusMsg "Trackside not compatible"
3) No indication is displayed
#TEST-VAL-SUB026-3B17#REF# FCT 1 Establishing communication session after SoM - degraded situation
#TEST-VAL-SUB026-5427#REF# FCT 2 SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session not open
#TEST-VAL-SUB026-5405#REF# FCT 3 SoM - L2/SR via Override in S10

#REQ-UNISIG-SUB026-1105#REF# 5.4.3.2.D32 #REQ-UNISIG-SUB026-0254:01#REF#
If the stored position is valid, the process shall go to A33
If the stored position is invalid, the process shall go to A34
TEST APPROACH:
The following aspects have been identified:
1) Stored TrainPosition is unknown
2) Stored TrainPosition is invalid 
3) Stored TrainPosition is valid
#TEST-VAL-SUB026-3218#REF# ECT 1 Input RBC contact data during SoM
#TEST-VAL-SUB026-4208#REF# ECT 2 SoM stored train location confirmed by RBC
#TEST-VAL-SUB026-5401#REF# ECT 3 SOM - L2/OS

#REQ-DESIGN-CR-0418#REF# 5.4.3.2.A33 #REQ-UNISIG-SUB026-0254:01#REF#
If the train position data stored in the on-board equipment is of status “valid”, the train position, marked as “valid” shall be transmitted to
the RBC via the "SoM position report" message.
This condition leads to S10.
#TEST-VAL-SUB026-5401#REF# FCT basic function SOM - L2/OS

#REQ-UNISIG-SUB026-1107#REF# 5.4.3.2.A34 #REQ-UNISIG-SUB026-0254:01#REF#
If the train position data stored in the on-board equipment is of status “invalid” or "unknown", the train position, marked as
“invalid” or "unknown" shall be transmitted to the RBC via the "SoM position report" message.
The process shall then go to D33
TEST APPROACH:
The following aspects have been identified:
1) OBU reports invalid TrainPosition
2) OBU reports unknown TrainPosition
3) RBC Version 2 and TRN is valid : M157(status) + P5(TRN)
4) RBC Version 1 and TRN is valid : M157(status) only
#TEST-VAL-SUB026-4210#REF# FCT 1 SoM Stored position not confirmed by RBC -> data deleted
#TEST-VAL-SUB026-5407#REF# FCT 2 SoM - L0/UN (nach: RBC rejects Train (A38))
#TEST-VAL-SUB026-5472#REF# FCT 3 Mode transition L1 PT->SB - L2 SB->FS
#TEST-VAL-SUB026-5529#REF# FCT 4 Variable Q_STATUS is Invalid in PositionReport (RBC accepts)

#REQ-DESIGN-CR-0419#REF# 5.4.3.2.A35 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-3703#REF#
The RBC shall inform the ERTMS/ETCS onboard equipment that the reported position is valid.
When this message is received by the ERTMS/ETCS on-board equipment, the status	of the position shall be set to "valid"
The process shall go to S10.
only the second part is relevant for obu
TEST APPROACH:
Following aspects have been identified:
1) RBC response is received 
2) no RBC response is received
#TEST-VAL-SUB026-4208#REF# FCT 1 SoM stored train location confirmed by RBC
#TEST-VAL-SUB026-4211#REF# FCT 2 SoM location invalid - set to unknown when leaving SB

#REQ-DESIGN-CR-0420#REF# 5.4.3.2.A24 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-3704#REF#
When the ERTMS/ETCS on-board equipment is informed that the train is accepted without valid position data, it shall delete the train position
data (new status: “unknown”)
This condition leads to S10.
#TEST-VAL-SUB026-5529#REF# FCT basic function Variable Q_STATUS is Invalid in PositionReport (RBC accepts)

#REQ-DESIGN-CR-0495#REF# 5.4.3.2.A39 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-3704#REF#
#REQ-DESIGN-CR-0411#REF#
When the ERTMS/ETCS on-board equipment is informed that the train is rejected, it shall delete the train position data (new status: “unknown”)
and shall terminate the session with the RBC.
The process shall then go to A40
#TEST-VAL-SUB026-5527#REF# FCT basic function SoM - deletion of stored position data on reception of Train Rejected

#REQ-DESIGN-CR-0421#REF# 5.4.3.2.A40 #REQ-UNISIG-SUB026-0254:01#REF#
#REQ-UNISIG-SUB026-010433#REF#
The ERTMS/ETCS on-board equipment shall inform the driver that the train is rejected
This condition leads to S10 (the driver has to unlock the situation to continue e.g. selection of new level).
UNISIG clarification: 
the next step (S10) should be started only, if the safe radio connection is closed too.
#TEST-VAL-SUB026-5527#REF# FCT basic function SoM - deletion of stored position data on reception of Train Rejected

#REQ-UNISIG-SUB026-005720#REF# 5.4.3.2.1
The SoM procedure shall end as soon as at least one of the following conditions is fulfilled:
  Transition to any mode other than SB
  The desk is closed
TEST APPROACH:
Following aspects have been identified:
1) Mode transition during SoM PositionReport repetition
2) Close Desk during SoM PositionReport repetition
#TEST-VAL-SUB026-5988#REF# FCT 1 Break of SoM by UES in D33
#TEST-VAL-SUB026-4295#REF# FCT 2 RBC contact information entered during SoM memorized
#TEST-VAL-SUB026-5523#REF# EET error expectation SoM if pending/established communication session exists
#TEST-VAL-SUB026-7031#REF# EET error expectation SoM S11, RBC does not send acknowledge train data

#REQ-UNISIG-SUB026-0256:01#REF# 5.4.3.3 #REQ-UNISIG-SUB026-005549#REF#


.
realised by: #REQ-UNISIG-SUB026-3700#REF#
realised by: #REQ-UNISIG-SUB026-010450#REF#
realised by: #REQ-UNISIG-SUB026-3701#REF#
realised by: #REQ-UNISIG-SUB026-3702:01#REF#
realised by: #REQ-UNISIG-SUB026-010514#REF#
realised by: #REQ-UNISIG-SUB026-3706#REF#
realised by: #REQ-UNISIG-SUB026-3703#REF#
realised by: #REQ-UNISIG-SUB026-010515#REF#
realised by: #REQ-UNISIG-SUB026-010516#REF#
realised by: #REQ-UNISIG-SUB026-010517#REF#
realised by: #REQ-UNISIG-SUB026-3704#REF#
realised by: #REQ-UNISIG-SUB026-3705:01#REF#
realised by: #REQ-UNISIG-SUB026-010471#REF#
realised by: #REQ-UNISIG-SUB026-010470#REF#

#REQ-UNISIG-SUB026-3700#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'Driver ID' shall be set valid when the driver has entered/re-entered or validated the driver id.
TEST APPROACH:
Following aspects have been identified:
1) Status changes from unknown to valid by enter of a Driver ID
2) Status changes from invalid to valid by re-validate of the existing Driver ID
3) Status changes from invalid to valid by re-enter of a new Driver ID (overwrite)
#TEST-VAL-SUB026-4210#REF# FCT 1 SoM Stored position not confirmed by RBC -> data deleted
#TEST-VAL-SUB026-5400#REF# FCT 2 SOM - L1/NL and L2/NL
#TEST-VAL-SUB026-3916#REF# FCT 3 Validity of Driver ID, Train Data and Train running number due to closing of desk during SoM

#REQ-UNISIG-SUB026-010450#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'Train Running Number' shall be set valid when the driver has entered/re-entered or validated the tTrain
Running Number.
TEST APPROACH:
The status unknown does not exist in the system because the application sets a default value at the start-up or at the revalidation.
Following aspects have been identified:
1) Re-Enter TRN, status is changed from invalid to valid (value is changed)
2) Re-Validate TRN, status is changed from invalid to valid (value remains unchanged)
Note: A complete separate test in S1 and S13 is not necessary for the status change.
#TEST-VAL-SUB026-5407#REF# FCT 1 SoM - L0/UN (nach: RBC rejects Train (A38))
#TEST-VAL-SUB026-5401#REF# FCT 2 SOM - L2/OS

#REQ-UNISIG-SUB026-3701#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'ERTMS/ETCS Level' shall be set valid when the driver has entered/re-entered or validated the ETCS Level.
TEST APPROACH:
The level is set to a configured value for the first start up the condition level "unknown" can hence not be reached. 
Following aspects have been identified:
1) Status changes from invalid to valid by re-enter of another Level
2) Status changes from invalid to valid by re-validate of the existing Level
#TEST-VAL-SUB026-5472#REF# FCT 1 Mode transition L1 PT->SB - L2 SB->FS
#TEST-VAL-SUB026-4210#REF# FCT 2 SoM Stored position not confirmed by RBC -> data deleted

#REQ-UNISIG-SUB026-3702:01#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'RBC ID/Phone Number' shall be set valid when the driver has entered/re-entered or validated the RBC
ID/Phone Number.

clarification: This applies both driver input during SoM and manual level change to level 2.
UNISIG clarification
TEST APPROACH:
Following aspects have been identified:
1) During SoM
1.1) Status changes from unknown to valid by enter of RbcData
1.2) Status changes from invalid to valid by re-validate of the existing RbcData
1.3) Status changes from invalid to valid by re-enter of a new RbcData (overwrite)
2) Outside of SoM
2.1) Status changes from unknown to valid by enter of RbcData
2.2) Status changes from invalid to valid by re-validate of the existing RbcData
2.3) Status changes from invalid to valid by re-enter of a new RbcData (overwrite)
#TEST-VAL-SUB026-8068#REF# FCT 1.1 RBC contact information entered during SoM memorized: unknown->valid
#TEST-VAL-SUB026-4295#REF# FCT 1.2 RBC contact information entered during SoM memorized
#TEST-VAL-SUB026-4210#REF# FCT 1.3 SoM Stored position not confirmed by RBC -> data deleted
#TEST-VAL-SUB026-8065#REF# FCT 2.1 Driver entered RBCData set to valid outside of SoM: unknown->valid
#TEST-VAL-SUB026-8066#REF# FCT 2.2 Driver entered RBCData set to valid outside of SoM: invalid data is revalidated by driver
#TEST-VAL-SUB026-8067#REF# FCT 2.3 Driver entered RBCData set to valid outside of SoM: invalid data is changed by driver

#REQ-UNISIG-SUB026-010514#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'RBC ID/Phone Number' shall be set valid if a session is opened sucessfull with these data.

clarification: This applies outside of the SoM procedure as well when the status of rbc data is invalid before.
UNISIG clarification:
a generalisation is useful
TEST APPROACH:
Following aspects have been identified:
1) During SoM
1.1) Session is opened successfully with the current RbcData, the status will be set to valid
1.2) Session is opened successfully with the Short Number, the status will be set to valid
1.3) Session is not opened with the current RbcData, the status of the RbcData remains invalid
1.4) Session is not opened successfully with the Short Number, the status remains invalid
2) Outside of SoM
2.1) Session is opened successfully with the current RbcData, the status will be set to valid
2.2) Session is opened successfully with the Short Number, the status will be set to valid
2.3) Session is not opened with the current RbcData, the status of the RbcData remains invalid
2.4) Session is not opened successfully with the Short Number, the status remains invalid
#TEST-VAL-SUB026-7210#REF# FCT 1.1 SoM A31: Session is opened successfully with invalid RbcData
#TEST-VAL-SUB026-5527#REF# FCT 1.2 SoM - deletion of stored position data on reception of Train Rejected
#TEST-VAL-SUB026-7211#REF# FCT 1.3 SoM A31: Session is not opened with invalid RbcData
#TEST-VAL-SUB026-8062#REF# FCT 1.4, 2.2, 2.4 Session is not opened successfully with the Short Number
#TEST-VAL-SUB026-8063#REF# FCT 2.1, 2.3 RBCData set to valid outside of SoM
#TEST-VAL-SUB026-8064#REF# EET error expectation RBC version not supported -> RBC data goes to valid

#REQ-UNISIG-SUB026-3706#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'Train Data' shall be set valid when the driver has entered/re-entered or validated the train data.
TEST APPROACH:
The status unknown does not exist in the system because the application loads default data in start-up.
Following aspects have been identified:
1) Re-Validate TD, status is changed from invalid to valid (value remains unchanged)
2) Re-Enter TD, status is changed from invalid to valid (value is changed)
#TEST-VAL-SUB026-5401#REF# FCT 1 SOM - L2/OS
#TEST-VAL-SUB026-5407#REF# FCT 2 SoM - L0/UN (nach: RBC rejects Train (A38))

#REQ-UNISIG-SUB026-3703#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'Train Location' shall be set valid when the RBC confirm the current position.
realizes through SoM A35
realised by: #REQ-DESIGN-CR-0419#REF#

#REQ-UNISIG-SUB026-010515#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'ERTMS/ETCS Level' shall be reset from valid to invalid if the stored train position data are not
"valid" at the beginning of the SoM-Procedure (D2).
UNISIG clarification:
the same is true for the manual level change.
TEST APPROACH:
The level is set to a configured value for the first start up the condition level "unknown" can hence not be reached.
Following aspects have been identified:
1) A valid status of Level will be set to invalid, if Train Position is not valid
#TEST-VAL-SUB026-5400#REF# FCT 1 SOM - L1/NL and L2/NL
#TEST-VAL-SUB026-4210#REF# EET error expectation SoM Stored position not confirmed by RBC -> data deleted

#REQ-UNISIG-SUB026-010516#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'RBC ID/Phone Number' shall be reset from valid to invalid if the stored train position data OR the stored
level are not valid at the beginning of the SoM-Procedure (D2).
UNISIG clarification:
the same is true for the manual level change.
TEST APPROACH:
The required function is executed on the No- path of the D2- decision. Therefore the differentiation of variants of the Train Position and Level
are not relevant here.
Following aspects have been identified:
1) A valid status of the RbcData will be set to invalid, if Train Position or Level are not valid
#TEST-VAL-SUB026-4295#REF# FCT 1 RBC contact information entered during SoM memorized
#TEST-VAL-SUB026-4210#REF# EET error expectation SoM Stored position not confirmed by RBC -> data deleted

#REQ-UNISIG-SUB026-010517#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'RBC ID/Phone Number' shall be reset to unknown if the driver has re-entered a Radio Network ID.
UNISIG clarification:
the same is true for the manual level change.
realised by: #REQ-UNISIG-SUB026-1087:01#REF#

#REQ-UNISIG-SUB026-3704#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The information 'Train Location' shall be deleted if the RBC accept or reject the train during SoM.
realizes through A24 and A39
realised by: #REQ-DESIGN-CR-0420#REF#
realised by: #REQ-DESIGN-CR-0495#REF#

#REQ-UNISIG-SUB026-3705:01#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The information 'train position data' shall be deleted if
the stored train location data are invalid when the train leaves mode STAND BY.
points following E10, ... and  5.4.5.3 a), f), g)
realised by: #REQ-DESIGN-CR-0569:01#REF#

#REQ-UNISIG-SUB026-010471#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'ERTMS/ETCS Level' shall be reset from valid to invalid if the driver chooses to re-enter the level in the
SoM-Procedure.
test hint:
the level dialogue cannot aborted in this case => the reset to invalid doesn't have an impact on ASW
TEST APPROACH:
Following aspects have been identified:
basic function
#TEST-VAL-SUB026-5408#REF# FCT basic function SoM status of information 'ERTMS/ETCS Level' and 'RBC ID/Phone Number'

#REQ-UNISIG-SUB026-010470#REF# 5.4.3.3 #REQ-UNISIG-SUB026-0256:01#REF#
The status of information 'RBC ID/Phone Number' shall be reset from valid to invalid if the driver chooses to re-enter the level in
the SoM-Procedure.
TEST APPROACH:
Following aspects have been identified:
basic function
#TEST-VAL-SUB026-5408#REF# FCT basic function SoM status of information 'ERTMS/ETCS Level' and 'RBC ID/Phone Number'

#REQ-DESIGN-CR-0624#REF# 5.4.5.1
Nominally, accidental loss of an already open session (that can occur at any step) has not been taken into account for the design of the SoM
flowchart. However, should such a fault occur above D11 the nominal procedure applies (refer to D11 in flowchart). On the other hand, if it
occurs in any step further than D11, the process shall go to S10.
TEST APPROACH:
The following aspects have been identified:
1) fault occur above D11 
2) fault occurs at step further than D11 
#TEST-VAL-SUB026-5541#REF# FCT 1 Degraded situations in SoM driver choice input train data in S10
#TEST-VAL-SUB026-7031#REF# FCT 2 SoM S11, RBC does not send acknowledge train data
#TEST-VAL-SUB026-5449#REF# EET CFX00039985 Accidental loss of an already open session SoM (S21) - driver selection L0 as fall-back
#TEST-VAL-SUB026-5480#REF# EET CFX00039985 Accidental loss of an already open session SoM (S20) - maximal time to consider the communication session still established exceeded

#REQ-DESIGN-CR-0626:02#REF# 5.4.5.3
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibilities, in addition to the ones that are described in section
5.4.3:
  only at S10 and S20 and if valid Train data is available, to select “Override”. If the driver chooses to do so, then the process shall go to
the procedure “Override” and, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status:
“unknown”)
  only at S10 and S20, to re-enter the Driver-ID
  only at S10 and S20,to re-enter the “Train running number”
  only at S20, to re-enter the Train data. If the driver chooses to do so, then the process shall go to S12.
  only at S10 and S20, to re-enter the Level. If the driver chooses to do so, then the process shall go to S2
  only at S20, to select “Non Leading”. If the driver chooses to do so, then the ERTMS/ETCS on-board equipment shall immediately switch to Non
Leading mode and, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”).
  only at S20, to select “Shunting”. If the driver chooses to do so, then the process shall go to the procedure “Shunting initiated by driver”
and, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”). If, in level 2 or
3, the RBC rejects the request for Shunting, the process shall go back to S20.
  only at S10, if valid Train Data is available, to select “Start”. If the driver chooses to do so:
  - if the level is 0, then the process shall go to S23.
  - if the level is NTC, then the process shall go to S22.
  - if the level is 1, then the process shall go to S24.
  - if the level is 2/3 and a session is open, then the process shall go to S21.
  - if the level is 2/3 and no session is open, then the process shall go to S24.
  only at S10 and S20, to set/remove a Virtual Balise Cover.
realised by: #REQ-DESIGN-CR-0625:01#REF#
realised by: #REQ-UNISIG-SUB026-010458#REF#
realised by: #REQ-UNISIG-SUB026-010461#REF#
realised by: #REQ-UNISIG-SUB026-010462#REF#
realised by: #REQ-UNISIG-SUB026-010463#REF#
realised by: #REQ-UNISIG-SUB026-010464#REF#
realised by: #REQ-UNISIG-SUB026-010465#REF#
realised by: #REQ-UNISIG-SUB026-010466#REF#

#REQ-DESIGN-CR-0625:01#REF# 5.4.5.3.a) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S10 and S20 and if valid Train data is available, to select “Override”. If the driver chooses to do so, then the process shall go to the
procedure “Override” and, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”)
the deletion of position data is realized with 4.10

UNISIG clarification:  
the conditions in ERA SRS DMI are less restrictive than here - otherwise the procedure have a deadlock in S11;
the Override in SB is constrained to level 2/3 in ERA SRS DMI and 5.8.2.1
realised by: #REQ-DESIGN-CR-0569:01#REF#

#REQ-UNISIG-SUB026-010458#REF# 5.4.5.3.b,.c) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S10 and S20, to re-enter the Driver-ID OR/AND the “Train running number”
S10 and S20 leads to S1 in the main window; the enabling of the individual buttons is defined in ERA SRS DMI

#REQ-UNISIG-SUB026-010461#REF# 5.4.5.3.d) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S20, to re-enter the Train data. If the driver chooses to do so, then the process shall go to S12.
S10 and S20 leads to S1 in the main window; the enabling of the individual buttons is defined in ERA SRS DMI

#REQ-UNISIG-SUB026-010462#REF# 5.4.5.3.e) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S10 and S20, to re-enter the Level. If the driver chooses to do so, then the process shall go to S2
S10 and S20 leads to S1 in the main window; the enabling of the individual buttons is defined in ERA SRS DMI

#REQ-UNISIG-SUB026-010463#REF# 5.4.5.3.f) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S20, to select “Non Leading”. If the driver chooses to do so, then the ERTMS/ETCS on-board equipment shall immediately switch to Non
Leading mode and, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”).
S10 and S20 leads to S1 in the main window; the enabling of the individual buttons is defined in ERA SRS DMI

the deletion of position data is realized with 4.10
realised by: #REQ-DESIGN-CR-0569:01#REF#

#REQ-UNISIG-SUB026-010464#REF# 5.4.5.3.g) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S20, to select “Shunting”. If the driver chooses to do so, then the process shall go to the procedure “Shunting initiated by driver”
and, if the position is still invalid, the ERTMS/ETCS on-board shall delete the train position data (new status: “unknown”). If, in level 2 or
3, the RBC rejects the request for Shunting, the process shall go back to S20.
S10 and S20 leads to S1 in the main window; the enabling of the individual buttons is defined in ERA SRS DMI

the deletion of position data is realized with 4.10
realised by: #REQ-DESIGN-CR-0569:01#REF#

#REQ-UNISIG-SUB026-010465#REF# 5.4.5.3.h) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S10, if valid Train Data is available, to select “Start”.

If the driver chooses to do so:
-	if the level is 0, then the process shall go to S23.
-	if the level is NTC, then the process shall go to S22.
-	if the level is 1, then the process shall go to S24.
-	if the level is 2/3 and a session is open, then the process shall go to S21.
-	if the level is 2/3 and no session is open, then the process shall go to S24.
S10 and S20 leads to S1 in the main window; the enabling of the individual buttons is defined in ERA SRS DMI

the following steps are the same as the normal SoM procedure
realised by: #REQ-UNISIG-SUB026-1098:01#REF#
realised by: #REQ-UNISIG-SUB026-010384#REF#
realised by: #REQ-UNISIG-SUB026-010385#REF#
realised by: #REQ-UNISIG-SUB026-010386#REF#

#REQ-UNISIG-SUB026-010466#REF# 5.4.5.3.i ) #REQ-DESIGN-CR-0626:02#REF#
The ERTMS/ETCS on-board equipment shall also offer the driver the following possibility, in addition to the ones that are described in section
5.4.3:
only at S10 and S20, to set/remove a Virtual Balise Cover

#REQ-UNISIG-SUB026-010374#REF# to.5.4.5
The SoM position report shall be repeated with a defined waiting time (see fixed value) after each repetition, in case
- no reply is received from the RBC
AND
- a communication session is open
AND
- the mode is Stand By

If no reply is received from the RBC after a defined number of repetitions (see fixed value), obu shall terminate the session.

The SoM process shall then go to step A32 respectively S10.
UNISIG clarification:
a definition is necessary, when the RBC is not answered of a SoM-PR. This case is handled analog to a session cannot be opened.

The next step (S10) should be started only, if the safe radio connection is closed too.
TEST APPROACH:
The following aspects have been identified:
1) Stop the repetition at end of SoM due to mode change
2) Stop the repetition at end of SoM because the desk is closed
3) RBC answers before end of repetition
4) No reply is received from the RBC after a defined number of repetitions and OBU terminates session
5) Stop the repetition because an RBC termination order
#TEST-VAL-SUB026-5988#REF# FCT 1 Break of SoM by UES in D33
#TEST-VAL-SUB026-4295#REF# FCT 2 RBC contact information entered during SoM memorized
#TEST-VAL-SUB026-4H98#REF# FCT 3 SoM PR with unknown position repeated with defined waiting time until RBC replies
#TEST-VAL-SUB026-4H97#REF# FCT 4 SoM PR with invalid position repeated without response, with defined waiting time, definded times -> session terminated
#TEST-VAL-SUB026-7702#REF# FCT 5 SoM PR is not sent after session is terminated and established again because of a session management order during SoM

#REQ-UNISIG-SUB026-3512#REF# 5.4.6.1 #REQ-UNISIG-SUB026-005757#REF#
A mission shall be considered as started as soon as the ERTMS/ETCS on-board equipment enters FS, LS, SR, OS, NL, UN, or SN mode.
TEST APPROACH:
The mission started information is evaluated in the procedure SH initiated by driver D040. The test focuses as far as possible on this
procedure. 
#TEST-VAL-SUB026-5011#REF# FCT FS Shunting initiated by driver L2, FS
#TEST-VAL-SUB026-5559#REF# FCT LS transition from SB to LS [70], SoM beyond S20
#TEST-VAL-SUB026-5136#REF# FCT NL Transition from NL/UN to SB
#TEST-VAL-SUB026-5002#REF# FCT SR SR->SH
#TEST-VAL-SUB026-7159#REF# FCT UN, OS, SN Mission start UN, OS, SN

#REQ-UNISIG-SUB026-005757#REF# 5.4.6.2
Entry in all other modes, from SB mode, shall not be considered as a mission.
the relevant modes are defined in 5.4.6.1
realised by: #REQ-UNISIG-SUB026-3512#REF#

Chapter 5.5

#REQ-DESIGN-CR-0072:01#REF# 5.5.2.1.1 #REQ-UNISIG-SUB026-006400#REF#
From FS, LS, OS, UN, NL, SR, PT, RV or SN mode, the entry of the ERTMS/ETCS on-board equipment into the Stand-by mode is considered as an End of
Mission
#TEST-VAL-SUB026-5117#REF# FCT FS Uebergang FS nach SB
#TEST-VAL-SUB026-4558#REF# FCT LS linking information when entering LS, L2 LS->SB[28]->LS[70]->TR[66] ->PT->LS[70]
#TEST-VAL-SUB026-5136#REF# FCT NL, UN Transition from NL/UN to SB
#TEST-VAL-SUB026-5118#REF# FCT OS Uebergang OS nach SB
#TEST-VAL-SUB026-5127#REF# FCT PT, RV Übergang PT->SB
#TEST-VAL-SUB026-4491#REF# FCT SN transition from SN to SB considered as EoM
#TEST-VAL-SUB026-5121#REF# FCT SR Transition from SR to SB

#REQ-UNISIG-SUB026-005773#REF# 5.5.2.1.3
The entry of the ERTMS/ETCS on-board equipment into the Stand-by mode, from PT mode, is only considered as an End of Mission if there was an
on-going mission.
TEST APPROACH:
The following aspects have been identified:
1) on-going mission
2) no on-going mission
#TEST-VAL-SUB026-5809#REF# FCT 1 Transition from PT to SB ongoing mission
#TEST-VAL-SUB026-5810#REF# FCT 2 Transition from PT to SB no ongoing mission

#REQ-UNISIG-SUB026-0774:02#REF# 5.5.2.3.1
The entry of the ERTMS/ETCS on-board equipment into the Shunting mode, from FS, LS, OS, SR, SN or UN mode, is considered as an End of Mission.
#TEST-VAL-SUB026-5000#REF# FCT FS FS->SH
#TEST-VAL-SUB026-4565#REF# FCT LS mode change LS->SH[6]
#TEST-VAL-SUB026-5001#REF# FCT OS OS->SH [50]
#TEST-VAL-SUB026-4480#REF# FCT SN SN/STM acceptance MP-SH - LTO L2 onboard
#TEST-VAL-SUB026-5002#REF# FCT SR SR->SH
#TEST-VAL-SUB026-5009#REF# FCT UN Shunting initiated by driver L0, UN
#TEST-VAL-SUB026-5430#REF# EET error expectation SoM stored level L2, valid RBC data and location, driver requests SH (E12) - session open

#REQ-UNISIG-SUB026-3513#REF# 5.5.2.3.2
The entry of the ERTMS/ETCS on-board equipment into the Shunting mode, from PT mode, is only considered as an End of Mission if there was an
on-going mission.
TEST APPROACH:
The following aspects have been identified:
1) on-going mission
2) no on-going mission
#TEST-VAL-SUB026-5542#REF# FCT 1 PT->SH(L1)[5] - communication session to RBC active
#TEST-VAL-SUB026-5543#REF# FCT 2 PT->SH[6] - degraded situation RBC does not order termination of connection

#REQ-UNISIG-SUB026-005796#REF# 5.5.3.1.2 #REQ-UNISIG-SUB026-0776:01#REF#
If a communication session with an RIU exists:
Step 2 -	The ERTMS/ETCS on-board equipment shall terminate the communication session
End of procedure

#REQ-UNISIG-SUB026-3694#REF# 5.5.3.1.3 #REQ-UNISIG-SUB026-0776:01#REF#
If a communication session with an RBC exists:
Step 2 -	The end of mission shall be reported to the RBC by means of the message “End of Mission”.
Step 3 -	The RBC shall request to terminate the communication session.
Step 4 -	The ERTMS/ETCS on-board equipment shall terminate the communication session
End of procedure

--- FINALISED ---
Für die End of Mission Prozedur ist das Senden der Message "End of Mission" entscheidend (Step 2).
Das Senden der Termination Order (Step 3) ist eine Anforderung an die Strecke.
Der Ablauf bei Erhalt der Termination Order von der Strecke entspricht dann einem normalen Termination entsprechend 3.5.5.2 (Step 4).
Um die degraded situation 5.5.4.1.1 zu erfüllen, muss das Fahrzeug nach Senden der Message "End of Mission" jedoch auf die Termination
Order warten.
realised by: #REQ-UNISIG-SUB026-0434#REF#
realised by: #REQ-UNISIG-SUB026-0260:01#REF#

#REQ-UNISIG-SUB026-0260:01#REF# 5.5.3.1.3 #REQ-UNISIG-SUB026-3694#REF#
If the train executes an end of mission procedure and a communication session to a RBC exists, the train shall report the end of Mission
(message “End of Mission”) to the RBC and shall wait for the termination order from the RBC.
see 5.5.4.1.1 in case of no termination order from trackside
TEST APPROACH:
The following aspect have been identified:
1) no communication session is open
2) communication session is open
2.1) RBC orders termination of the communication session
2.2) RBC does not order termination of the communication session
#TEST-VAL-SUB026-5008#REF# FCT 1 , CFX00035488 End of mission due to transition to SH/L2 - no communication session open
#TEST-VAL-SUB026-5126#REF# FCT 2.1 EoM in L1 with open communication session
#TEST-VAL-SUB026-4491#REF# FCT 2.2 transition from SN to SB considered as EoM
#TEST-VAL-SUB026-5608#REF# EET error expectation SoM S0 - OBU first terminates all existing sessions/connections (two connection up)
#TEST-VAL-SUB026-7200#REF# EET error expectation SoM S0 - OBU first terminates all existing sessions/connections (only termination order from sv RBC)
#TEST-VAL-SUB026-7201#REF# EET error expectation SoM S0 - OBU first terminates all existing sessions/connections (only termination order from non-sv RBC)

#REQ-UNISIG-SUB026-005815#REF# 5.5.4.1.1
Level 2,3 : In case a communication session is established and no request to terminate the communication session is received from the RBC within
a fixed waiting time (see appendix to chapter 3, List of Fixed Value Data) after sending the “End of Mission” message, the message shall be
repeated with the fixed waiting time after each repetition.
realised by: #REQ-UNISIG-SUB026-0262:02#REF#

#REQ-UNISIG-SUB026-0262:02#REF# 5.5.4.1.1 #REQ-UNISIG-SUB026-005815#REF#
#REQ-DESIGN-CR-0093:01#REF#
In case a communication session is established and no request to terminate the communication session is received from the RBC within a fixed
waiting time (see appendix to chapter 3, List of Fixed Value Data) after sending the “End of Mission” message, the message shall be repeated
with the fixed waiting time after each repetition.
UNISIG clarification:
5.5.3.1.2 and 5.5.3.1.3 defines the procedure without a level 2/3 dependency. Therefore the error handling is also independent of level 2/3.

Rel. 8.0 - 
change of requirement - the termination is defined now in 5.5.4.1.1.
TEST APPROACH:
The following equivalence classes were identified:
1) L2, L3
2) L0, L1, NTC
#TEST-VAL-SUB026-5007#REF# ECT 1 delayed/no response from RBC to EoM
#TEST-VAL-SUB026-5542#REF# ECT 2 PT->SH(L1)[5] - communication session to RBC active
#TEST-VAL-SUB026-5609#REF# EET error expectation SoM S0 - OBU first terminates all existing sessions/connections (one connection down)

#REQ-UNISIG-SUB026-005817#REF# 5.5.4.1.1.1
After a defined number of repetitions (see appendix to chapter 3, List of Fixed Value Data), and if no reply is received within the fixed
waiting time from the time of the last sending of “End of Mission”, the ERTMS/ETCS onboard equipment shall terminate the communication session.
TEST APPROACH:
The following equivalence classes were identified:
1) L2, L3
2) L0, L1, NTC
#TEST-VAL-SUB026-5007#REF# ECT 1 delayed/no response from RBC to EoM
#TEST-VAL-SUB026-5542#REF# ECT 2 PT->SH(L1)[5] - communication session to RBC active
#TEST-VAL-SUB026-5609#REF# EET error expectation SoM S0 - OBU first terminates all existing sessions/connections (one connection down)

#REQ-UNISIG-SUB026-005819#REF# 5.5.4.1.2
Level 2,3 : In case no communication session is open, no communication session shall be established to report the end of mission.
realised by: #REQ-UNISIG-SUB026-0776:01#REF#

#REQ-UNISIG-SUB026-0776:01#REF# 5.5.4.1.2 #REQ-UNISIG-SUB026-005819#REF#
In case no communication session is open, no communication session shall be established to report the end of mission.
clarification:
5.5.3.1.2 and 5.5.3.1.3 defines the procedure without a level 2/3 dependency. Therefore this exception is also independent of level 2/3.

realizes through 5.5.3.1.2, 5.5.3.1.3
realised by: #REQ-UNISIG-SUB026-005796#REF#
realised by: #REQ-UNISIG-SUB026-3694#REF#

Chapter 5.6

#REQ-UNISIG-SUB026-0264:01#REF# 5.6.2.2




#DSC-UNISIG-SUB026-005841#REF#

Figure 2: Flowchart for “Shunting Initiated by Driver” --- FINALISED --- The conditions for enabling the Shunting Request Button on DMI (E015) are defined in /ERA SRS DMI/. ------ Die Entscheidungen D40 und D80 ergeben sich nicht aus dem Ablauf der SH-Prozedur. Sowohl das Anstoßen und Ausführen der End of Mission-Prozedur als auch das Senden des Positionreports haben ihren Auslöser im Wechsel nach SH und geschehen deshalb unabhängig von dieser Prozedur und den genannten Bedingungen. D40 - Entscheidung fällt in End of Mission Prozedur - Subset 026, Kap. 5.5.2.3 D80 - Senden eines PR bei Modewechsel 3.6.5.1 und 4.5.2 (übrigens unabhängig von Level 2/3) ------ The session termination after a RBC order to terminate the session is performed independend of this procedure (see 3.5.5).
realised by: #REQ-UNISIG-SUB026-010540#REF#
realised by: #REQ-UNISIG-SUB026-010541#REF#
realised by: #REQ-UNISIG-SUB026-005836#REF#
realised by: #REQ-UNISIG-SUB026-0986:01#REF#
realised by: #REQ-UNISIG-SUB026-0988#REF#
realised by: #REQ-UNISIG-SUB026-010542#REF#
realised by: #REQ-UNISIG-SUB026-0994:01#REF#
realised by: #REQ-UNISIG-SUB026-010545#REF#

#REQ-UNISIG-SUB026-010540#REF# 5.6.2.2.D20,.D30,.A030 #REQ-UNISIG-SUB026-0264:01#REF#
If the driver selects "Shunting"
AND
the current level is STM (NTC)
AND
a national trip procedure is activated for the current STM (NTC)
the on board unit shall be tripped.
conform to mode transition condition [35]
realised by: #REQ-UNISIG-SUB026-010397#REF#

#REQ-UNISIG-SUB026-010541#REF# 5.6.2.2.D20,.D30,.A050 #REQ-UNISIG-SUB026-0264:01#REF#
If the driver selects "Shunting"
AND
the current level is 0, 1, STM (NTC)
AND
(if Level = STM) no a national trip procedure is activated for the current STM (NTC)
the on board unit shall be changed to mode SHUNTING.
conform to mode transition condition [5]
the part "no national trip procedure ..." is realized through the lower priority of mode transition SN->SH to SN->TR
realised by: #REQ-UNISIG-SUB026-2215:01#REF#

#REQ-UNISIG-SUB026-005836#REF# 5.6.2.2.A050 #REQ-UNISIG-SUB026-0264:01#REF#
If obu change to mode Shunting after a driver selection, any previous list of balise groups for SH area shall be deleted or replaced by a new
list of of balise groups for Shunting area.
The deletion in Level 2/3 after receiving of a SH authorised from RBC is already specified in the clarification of 3.12.4.4.
An additional req. for the replacement isn't necessary. In this case must only be ensured that the new list from SH authorised is not
deleted after change to SH.
realised by: #REQ-UNISIG-SUB026-0581:01#REF#
realised by: #REQ-UNISIG-SUB026-005838#REF#

#REQ-UNISIG-SUB026-005838#REF# to.5.6.2.2.A050 #REQ-UNISIG-SUB026-005836#REF#
If obu change to mode Shunting after a driver selection and the current level is L1, any previous list of balise groups for SH area shall be
deleted.
L0 and STM can be excluded too, because due to 4.8/4.10 a list cannot managed in the modes TR/UN/SN.
TEST APPROACH:
The List of balises for SH area is accepted together with a MP or SH Authorization only (so when in Level 1 or Level 2/3 only).
Level 2 is covered by verification of #REQ-UNISIG-SUB026-0581:01#REF#.
When entering Level 0 or NTC, the list of balises for SH area is deleted (#REQ-DESIGN-DATEN-0009:02#REF#)
Hence, only Level 1 is verified here.
#TEST-VAL-SUB026-8162#REF# FCT basic function List of balises in SH when driver initiates SH

#REQ-UNISIG-SUB026-0986:01#REF# 5.6.2.2.D20,.A045 #REQ-UNISIG-SUB026-0264:01#REF#
The ERTMS/ETCS on-board equipment shall send the “Request for Shunting” message to the RBC, if
- the driver selects "Shunting"
AND
- the current level is 2/3.
the position report is a part of this message (see Msg 130)
TEST APPROACH:
The following aspects have been identified:
1) current level is 2/3
2) current level is other than 2/3
#TEST-VAL-SUB026-5011#REF# FCT 1 Shunting initiated by driver L2, FS
#TEST-VAL-SUB026-7064#REF# FCT 2 OBU does not send 'Request for Shunting' outside L2/L3
#TEST-VAL-SUB026-7065#REF# EET error expectation Shunting Initiated by Driver S050, Level transition L1

#REQ-UNISIG-SUB026-0988#REF# 5.6.2.2.S050 #REQ-UNISIG-SUB026-0264:01#REF#
After sending a Shunting Request to the RBC the ERTMS/ETCS on-board equipment shall wait for a SH permission from RBC.
#TEST-VAL-SUB026-7066#REF# FCT basic function Shunting Initiated by Driver S050

#REQ-UNISIG-SUB026-010542#REF# 5.6.2.2.E90,.S050 #REQ-UNISIG-SUB026-0264:01#REF#
If
- a “Request for Shunting” message was send to the RBC
AND
- the Shunting is permitted from the RBC
AND
- the current level is 2/3,
the on board unit shall change to mode SHUNTING.
conform to mode transition condition [6]
realised by: #REQ-DESIGN-CR-0737#REF#

#REQ-UNISIG-SUB026-010557#REF# 5.6.2.2.S050 #REQ-UNISIG-SUB026-005851#REF#
#REQ-UNISIG-SUB026-3328#REF#
When the “Request for Shunting” message to RBC is send, the on board unit shall cancel the waiting on an answer from RBC,
if
- obu terminates the session during the waiting on an answer
OR
- the train leaves level 2 or 3
OR
- the mode is changed
OR
- no reply is received from the RBC after a defined number of repetitions (see fixed value)

The driver shall be informed, that the RBC not answers the SH request.
UNISIG clarification: There is no abort criteria is defined, when OBU waits of the RBC answer and any another operational situation is entered.
TEST APPROACH:
Following aspects have been identified:
1) level transition L2/3 left
2) level transition L2/3 not left
3) mode change
4) mode level change
5) termination after defined number of repetitions
6) termination of communication session
7) indication of system status message in all relevant modes
7.1) FS
7.2) LS
7.3) OS
7.4) PT
7.5) SB
7.6) SR
#TEST-VAL-SUB026-7065#REF# FCT 1 Shunting Initiated by Driver S050, Level transition L1
#TEST-VAL-SUB026-7071#REF# FCT 2 Shunting Initiated by Driver S050, level change L2/L3
#TEST-VAL-SUB026-7068#REF# FCT 3 Shunting Initiated by Driver S050, mode change
#TEST-VAL-SUB026-7070#REF# FCT 4 Shunting Initiated by Driver S050, mode/level change
#TEST-VAL-SUB026-5015#REF# ECT 5 RBC sends no response to M130
#TEST-VAL-SUB026-7072#REF# FCT 6 OBU sends M130 depending on communication session state
#TEST-VAL-SUB026-4681#REF# FCT 7.1, 7.6 request for SH not granted in FS/SR
#TEST-VAL-SUB026-4682#REF# FCT 7.2, 7.3 request for SH not granted in OS/LS
#TEST-VAL-SUB026-4589#REF# FCT 7.4 SH request not granted in PT
#TEST-VAL-SUB026-4683#REF# FCT 7.5 request for SH not granted SoM
#TEST-VAL-SUB026-3665#REF# EET error expectation Outage of safe connection after sending Request for Shunting

#REQ-UNISIG-SUB026-0994:01#REF# 5.6.2.2.E215,.A220 #REQ-UNISIG-SUB026-0264:01#REF#
#REQ-UNISIG-SUB026-3327#REF#
An indication shall be given to the driver that SH was refused by the RBC, if
a “Request for Shunting” message was send to the RBC
AND
the SH permission is refused from the RBC
AND
the current level is 2/3.
TEST APPROACH:
The level dependency is fulfilled by default as the SH request procedure is started in level 2/3 only and aborted when leaving these levels.
The indication of the system status message is verified for all relevant modes.
Following aspects have been identified:
1) indication of system status message in all relevant modes.
1.1) SB
1.2) FS
1.3) OS
1.4) LS
1.5) SR
1.6) PT
2) 'Request for shunting' has been send
3) level 2/3 change
#TEST-VAL-SUB026-4B62#REF# FCT 1.1 SB/L2 - Acceptance of SH Refused; related indication on DMI
#TEST-VAL-SUB026-4578#REF# FCT 1.2, 1.3 Reception of SH Refused FS/OS
#TEST-VAL-SUB026-4579#REF# FCT 1.4, 1.5 Reception of SH Refused SR/LS
#TEST-VAL-SUB026-5012#REF# FCT 1.6 Shunting initiated by driver (L2, PT) rejected by RBC
#TEST-VAL-SUB026-7068#REF# FCT 2 Shunting Initiated by Driver S050, mode change
#TEST-VAL-SUB026-7069#REF# FCT 3 Shunting Initiated by Driver S050, level change L2/L3

#REQ-UNISIG-SUB026-010545#REF# 5.6.2.2.S100 #REQ-UNISIG-SUB026-0264:01#REF#
The ERTMS/ETCS on-board equipment shall awaited a RBC order to terminate the communication session, if
- a position report for mode change to SH is sended
AND
- no on-going mission exists.
realised by: #REQ-UNISIG-SUB026-3691:02#REF#

#REQ-UNISIG-SUB026-0265:01#REF# 5.6.4.1.1
In case a communication session is established and no reply is received from the RBC within a fixed waiting time (see appendix to chapter 3,
List of Fixed Value Data) after sending the “Request for Shunting” message, the message shall be repeated with the fixed waiting time after each
repetition.
TEST APPROACH:
Following aspects have been identified:
1) immediate response
2) response after max number of repetitions
3) response repetition start
#TEST-VAL-SUB026-4616#REF# FCT 1 OS->SH[6]
#TEST-VAL-SUB026-5014#REF# FCT 2 RBC sends M28 after M130 repetition
#TEST-VAL-SUB026-7066#REF# FCT 3 Shunting Initiated by Driver S050

#REQ-UNISIG-SUB026-005851#REF# 5.6.4.1.2
After a defined number of repetitions (see appendix to chapter 3, List of Fixed Value Data) , and if no reply is received within the fixed
waiting time from the time of the last sending of “Request for Shunting”, the ERTMS/ETCS onboard equipment shall inform the driver and shall
terminate the communication session.
realised by: #REQ-UNISIG-SUB026-010557#REF#
realised by: #REQ-UNISIG-SUB026-010304#REF#

#REQ-UNISIG-SUB026-010304#REF# to.5.6.4.1.2 #REQ-UNISIG-SUB026-005851#REF#
If no reply of a SH request is received from the RBC after a defined number of repetitions, obu shall terminate the session.
#TEST-VAL-SUB026-5015#REF# ECT basic function RBC sends no response to M130

#REQ-UNISIG-SUB026-3102:01#REF# 5.6.4.2
ERTMS/ETCS level 2 or 3: in case a communication session is established and no order to terminate the session is received from the RBC within a
fixed waiting time (see appendix to chapter 3, List of Fixed Value Data) after reporting the mode change, the report shall be repeated with the
fixed waiting time after each repetition
realised by: #REQ-UNISIG-SUB026-3691:02#REF#

#REQ-UNISIG-SUB026-3691:02#REF# to.5.6.4.2 #REQ-UNISIG-SUB026-3102:01#REF#
#REQ-UNISIG-SUB026-005855#REF#
#REQ-DESIGN-CR-0093:01#REF#
#REQ-UNISIG-SUB026-010545#REF#
When no on-going mission exists, the position report of mode change to Shunting shall be repeated with a defined waiting time (see fixed value)
after each repetition, as long as
- no request to terminate the session is received from the RBC
AND
- a communication session is open
AND
- the mode is furthermore SH or PS

If no request to terminate the session is received from the RBC after a defined number of repetitions (see fixed value) or another condition is
violated, obu shall terminate the session.
UNISIG clarification: a session, if available, has to be terminated independent of the current level
the condition "no mode change" is necessary, because a change to TR/NL/SB is possible.
TEST APPROACH:
The following aspects have been identified:
1) Conditions to consider no ongoing mission at transition to SH by procedure Shunting initiated by driver
1.1) SH by driver initiated in mode SB
1.2) SH by driver initiated in mode PT
2) Level dependency: a communication session has to be terminated independent of level
2.1) equivalence class comprising L2/3
2.2) equivalence class comprising L0/1/NTC
3) Conditions that cause the stop of Position Reports repetition
3.1) RBC responds with session termination order
3.2) Session termination order received from BG
3.3) loss of safe radio connection after entry in SH
3.3.1) safe connection restored before PR repetition is completed
3.3.2) safe connection is not restored before PR repetition is completed
3.4) Mode change to other than SH
3.4.1) mode change to SB via Exit Shunting (restart SoM)
3.4.2) mode change to other modes (equivalence class: SB (via close desk), NL, TR)
3.4.3) mode change to PS
#TEST-VAL-SUB026-4393#REF# FCT 1.1, 2.1 SB->SH[6] - degraded situation RBC does not order termination of connection
#TEST-VAL-SUB026-5543#REF# FCT 1.2 PT->SH[6] - degraded situation RBC does not order termination of connection
#TEST-VAL-SUB026-7074#REF# FCT 2.2 RBC does not respond to PR for mode change to SH in L1
#TEST-VAL-SUB026-7986#REF# FCT 3.1 RBC responds to PR mode change to SH
#TEST-VAL-SUB026-7987#REF# FCT 3.2 pass BG with session termination order after switch to SH
#TEST-VAL-SUB026-7988#REF# FCT 3.3.1 loss of safe radio connection after sending PR with mode change to SH (safe connection re-established)
#TEST-VAL-SUB026-7989#REF# FCT 3.3.2 loss of safe radio connection after sending PR with mode change to SH (safe connection not re-established)
#TEST-VAL-SUB026-7990#REF# FCT 3.4.1 Exit shunting after switch to SH, no session termination ordered by RBC
#TEST-VAL-SUB026-7991#REF# FCT 3.4.2 Mode change SH->NL (no session termination ordered by RBC while in SH)
#TEST-VAL-SUB026-8101#REF# FCT 3.4.3 Mode change SH->PS (no session termination ordered by RBC after entry in SH by driver)

#REQ-UNISIG-SUB026-005855#REF# 5.6.4.3
After a defined number of repetitions (see appendix to chapter 3, List of Fixed Value Data), and if no reply is received within the fixed
waiting time from the last sending of the mode change report, the ERTMS/ETCS onboard equipment shall terminate the session.
realised by: #REQ-UNISIG-SUB026-3691:02#REF#

Chapter 5.7

#REQ-UNISIG-SUB026-0783#REF# 5.7.2.2
Shunting is requested for the current location means that, according to the mode profile received the max safe front end of the train is at or
in advance of the location for which switching to SH mode is requested.
realised by: #REQ-UNISIG-SUB026-0784:02#REF#

#REQ-UNISIG-SUB026-3667#REF# 5.7.2.3
The ERTMS/ETCS on-board equipment shall switch immediately to SH mode and a request for acknowledgement shall be displayed to the driver (refer
to SRS chapter 4, transitions between modes).
realised by: #REQ-UNISIG-SUB026-0784:02#REF#

#REQ-UNISIG-SUB026-0784:02#REF# to.5.7.2.3 #REQ-UNISIG-SUB026-0783#REF#
#REQ-UNISIG-SUB026-3667#REF#
#REQ-DESIGN-CR-0128:01#REF#
The obu shall switch immediately to SH mode and a request for acknowledgement shall be displayed to the driver, if
- a mode profile giving a Shunting area is received and max safe front end of the train is already inside this area
AND
- the obu is not in the modes SB and PT.
the exception for SB and PT is followed from 5.7.4 (first ACK, than mode change)
TEST APPROACH:
The following aspects have been identified:
1) D_MAMODE > 0
2) D_MAMODE = 0
#TEST-VAL-SUB026-5115#REF# FCT 1 SH immediately, D_MAMODE+L_MAMODE already passed
#TEST-VAL-SUB026-5018#REF# FCT 2 Acknowledgment of shunting requested for the current location

#REQ-UNISIG-SUB026-0785:01#REF# 5.7.2.4 #REQ-UNISIG-SUB026-0791:01#REF#
#REQ-UNISIG-SUB026-007978#REF#
If the driver does not acknowledge within the driver acknowledgement time (refer to Appendix A.3.1) after the change to SH mode, the service
brake command shall be triggered. The command shall be released as soon as the driver acknowledges (unless the command was triggered also for
other reasons).
TEST APPROACH:
The following aspects have been identified:
1) Shunting requested for a further location 
2) Shunting requested for a further current location
3) Brake command was triggered also for other reasons
#TEST-VAL-SUB026-4326#REF# FCT 1 , CFX00035849 Release speed given by the MA not taken into account for mode transition FS->SH (level2)
#TEST-VAL-SUB026-5018#REF# FCT 2 Acknowledgment of shunting requested for the current location
#TEST-VAL-SUB026-7664#REF# FCT 3 SB handling when driver does not acknowledge within the driver acknowledgement time: SH
#TEST-VAL-SUB026-5757#REF# EET error expectation Brake due to missing SH acknowledgment and over speed in SH

#REQ-UNISIG-SUB026-0786#REF# 5.7.3.2
A request for acknowledgement shall be displayed to the driver, when the following two conditions are fulfilled:
a)	the distance between the estimated front end of the train and the beginning of shunting area is shorter than a value, contained in the
mode profile
b)	the speed is lower than the Shunting mode speed limit (National Value, or value given in the mode profile)
TEST APPROACH:
The following aspects have been identified:
1) the distance between the estimated front end of the train and the beginning of shunting area is shorter than a value, contained in the mode
profile
2) the speed is lower than the Shunting mode speed limit 
2.1) National Value
2.2) value given in the mode profile
#TEST-VAL-SUB026-5019#REF# FCT 1 Train reaches SH acknowledgment window with speed < V_MAMODE (SH)
#TEST-VAL-SUB026-5251#REF# FCT 2.1 Train reaches SH acknowledment window with speed > V_NVSHUNT
#TEST-VAL-SUB026-8135#REF# FCT 2.2 No SH acknowledgment request when entering acknowledgment window if train speed exceeds V_MAMODE (/=127)

#REQ-UNISIG-SUB026-0787#REF# 5.7.3.3
Once the request for acknowledgement is displayed, it shall not be taken back, even if the above conditions are no more fulfilled (e.g., the
train accelerates).
TEST APPROACH:
The following aspects have been identified:
1) independent of speed condition
2) independent of location condition
#TEST-VAL-SUB026-5019#REF# FCT 1 Train reaches SH acknowledgment window with speed < V_MAMODE (SH)
#TEST-VAL-SUB026-5252#REF# FCT 2 Once the SH acknowledgment request is displayed, it is not taken back if the train sets back out of ack window
#TEST-VAL-SUB026-5256#REF# EET error expectation SH acknowledgment request taken back if acknowledgment would not lead to a transition to SH

#REQ-UNISIG-SUB026-0788:01#REF# 5.7.3.4
Until the ERTMS/ETCS on-board equipment has switched to SH mode, according to the mode profile, the beginning of the shunting area shall be
considered either as the EOA (keeping the SvL given by the MA) or as both the EOA and SvL (instead of the EOA and SvL given by the MA), with no
release speed.
UNISIG clarification:
"with no release speed" is valid for both conditions
TEST APPROACH:
The speed and distance monitoring evaluates the targets mode independent refer to SUBSET-026 3.13. The actual brake curve calculation is tested
by the appropriated module tests. The test outlined here has to be ensured that the EoA, SvL and release speed provided to the module BC agree
with the requirement.
The following aspects have been identified:
1) Q_MAMODE dependency (black box)
2) EOA and SvL depending on Q_MAMODE (BC input)
3) no release speed
#TEST-VAL-SUB026-5761#REF# FCT 1 Start of SH area supervision
#TEST-VAL-SUB026-5758#REF# FCT 2 SH area start considered either as the EOA (keeping the SvL given by the MA) or as both the EOA and SvL depending on Q_MAMODE
#TEST-VAL-SUB026-5766#REF# FCT 3 Start of MP-SH supervised without release speed

#REQ-UNISIG-SUB026-0789#REF# 5.7.3.5 #REQ-DESIGN-CR-0128:01#REF#
When the driver acknowledges, the ERTMS/ETCS on-board equipment shall immediately switch to SH mode (refer to chapter 4, transitions between
modes).
TEST APPROACH:

The requirement verification for all relevant start modes takes place via verification of SUBSET-026 4.6.
Following aspects have been identified:
1) current speed above V_MAMODE
2) current speed below V_MAMODE
#TEST-VAL-SUB026-5019#REF# FCT 1 Train reaches SH acknowledgment window with speed < V_MAMODE (SH)
#TEST-VAL-SUB026-5020#REF# FCT 2 Train reaches SH acknowledgment window with speed > V_MAMODE (SH)

#REQ-UNISIG-SUB026-0790#REF# 5.7.3.6 #REQ-UNISIG-SUB026-0582#REF#
If the max safe front end of the train reaches the beginning of the shunting area according the mode profile and the driver has not yet
acknowledged, the ERTMS/ETCS on-board equipment shall switch immediately to SH mode and a request for acknowledgement shall be displayed to the
driver (refer to SRS chapter 4, transitions between modes).
#TEST-VAL-SUB026-5021#REF# FCT basic function Movement into SH area without driver acknowledgment

#REQ-UNISIG-SUB026-0791:01#REF# 5.7.3.7 #REQ-UNISIG-SUB026-007978#REF#
If, in this case, the driver does not acknowledge within the driver acknowledgement time (refer to Appendix A.3.1) after the change to SH mode,
the service brake command shall be triggered. The command shall be released as soon as the driver acknowledges (unless the command was triggered
also for other reasons).
realised by: #REQ-UNISIG-SUB026-0785:01#REF#

#REQ-DESIGN-CR-0061#REF# 5.7.4.1 #REQ-UNISIG-SUB026-1102:01#REF#
#REQ-DESIGN-CR-0137:02#REF#
When performing a SoM or a Train Trip procedure and when the current level is 2 or 3, the ERTMS/ETCS on-board equipment can receive a mode
profile giving an Shunting area which the train has already entered with its max safe front end. In this case, the ERTMS/ETCS on-board equipment
shall first require an acknowledgement from the driver.
realised by: #REQ-UNISIG-SUB026-3696#REF#

#REQ-UNISIG-SUB026-3696#REF# 5.7.4.1 #REQ-DESIGN-CR-0061#REF#
#REQ-DESIGN-CR-0128:01#REF#
#REQ-UNISIG-SUB026-010419#REF#
#ANA-UNISIG-Procedure-0001#REF#
If a mode profile requiring Shunting is accepted in the modes SB or PT and the train has already entered the mode profile area with its max safe
front end, the ERTMS/ETCS on-board equipment shall first require an ackowledgement from the driver.

Remark: The mode change to Shunting is execute after the ackowledgement from the driver (see condition[50] in 4.6.3).
gilt auch bei Erhalt eines Modeprofils vor Betätigen der Start-Taste
TEST APPROACH:
The following aspects have been identified:
1) PT
1.1) START selected
1.2) START not selected
2) SB
2.1) START selected
2.2) START not selected
#TEST-VAL-SUB026-3B13#REF# FCT 1.1 Establishing a communication session at mode transition SB -> SH (L2, not EoM)
#TEST-VAL-SUB026-4938#REF# FCT 1.2 Mode transition SR->TR[54], SH->TR[49], PT->SH[50], PT->SR[37], PT->OS[15]
#TEST-VAL-SUB026-4112#REF# FCT 2.1 SOM - L2/SH
#TEST-VAL-SUB026-5579#REF# FCT 2.2 transition from SB to SH, SoM beyond S20

#REQ-DESIGN-CR-0062#REF# 5.7.4.2
When the driver acknowledges, the ERTMS/ETCS on-board equipment shall perform transition to Shunting mode.
realizes through 4.6.3, condition[50]
realised by: #REQ-UNISIG-SUB026-2216#REF#

Chapter 5.8

#REQ-DESIGN-CR-0141:02#REF# 5.8.2.1
The ERTMS/ETCS on-board equipment shall allow the driver to select “Override” (i.e. the “Override” button becomes available) only when:
a)	The train speed is under or equal to the speed limit for triggering the “override” function (national value) AND
b)	The current mode is Full Supervision, Limited Supervision, On Sight, Staff Responsible, Shunting, Unfitted, Post Trip, Stand By (in
level 2/3 only) or SN (National System) AND
c)	Validated Train Data is available (except when already in Shunting mode).
is realized with enabling conditions for the button "EoA" in ERA SRS DMI
#TEST-VAL-SUB026-3588#REF# EET CFX00038183 driver manually changes to level 2 communication session to the respective RBC already exists - T_NVCONTACT expiry before
#TEST-VAL-SUB026-4H82#REF# FCT b) SB L0, L1, NTC, L2 Override in SB L0, L1, NTC, L2
#TEST-VAL-SUB026-5200#REF# EET error expectation Override EoA with pending 'emergency stop revocation'

#REQ-UNISIG-SUB026-3676#REF# 5.8.2.3
The “Override” procedure shall be triggered when selected by the driver.
#TEST-VAL-SUB026-4980#REF# FCT basic function Transition Table 4.6.3 OS->FS[32]->SR[37]->FS[31]->SR[37]->TR[54]

#REQ-UNISIG-SUB026-0269:01#REF# 5.8.3.1
The mode shall change as follows:
a)	If the current mode is Full Supervision, Limited Supervision, On Sight, Stand-By or Post Trip, the mode shall immediately switch to the
Staff Responsible (SR) mode (if the mode is already SR it remains unchanged)
b)	If the current mode is Shunting the mode shall remain unchanged
c)	If the current mode is Unfitted (level 0 area) or SN (level NTC area) the mode shall only change to Staff Responsible when the level
changes to 1,2 or 3 (refer to SRS chapter 4, transitions between modes)

--- FINALISED ---
The concrete mode transitions after Override triggering are defined in chapter 4.6.
#ANALYSE-VALUNISIG-4115#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-DESIGN-CR-0463:01#REF# 5.8.3.1.1
If the mode, when activating Override, is OS, LS or FS, the former EOA shall be retained. If the mode is SB or PT, the current position of the
train front shall be considered as the former EOA.
#TEST-VAL-SUB026-5207#REF# EET CFX00041458 Revocation of override when passing override activation location (after two override activations)
#TEST-VAL-SUB026-5210#REF# EET CFX00041458 Supervision of former EoA after override revocation due to passing of BG not indicated in P63
#TEST-VAL-SUB026-5494#REF# EET CFX00041458 Any further activation of the Override in SR mode has no effect on the former EoA
#TEST-VAL-SUB026-5206#REF# FCT FS Supervision of former EoA and SR distance supervised before overriding
#TEST-VAL-SUB026-5447#REF# FCT LS LS - former EoA retained when activating override
#TEST-VAL-SUB026-5509#REF# FCT OS Retention of EoA when override EoA done in FS/OS
#TEST-VAL-SUB026-5515#REF# FCT SB, PT Position considered as former EoA in SB/PT when override EoA done
#TEST-VAL-SUB026-5933#REF# EET error expectation LoA / EoA+DP, EoA retained when activating override

#REQ-DESIGN-CR-0464:01#REF# 5.8.3.1.3
The former EOA shall be deleted if:
a)	the train reads the information “stop in SR mode” from a balise group OR
b)	SR mode is left.
TEST APPROACH:
The following aspects have been identified:
1) the train reads the information “stop in SR mode” from a balise group
2) SR mode is left
2.1) FS
2.2) LS
2.3) NL
2.4) OS
2.5) SB
2.6) SH
2.7) SN
2.8) TR
2.9) UN
#TEST-VAL-SUB026-5511#REF# FCT 1 Deletion of EoA on crossing Stop if in Staff Responsible (pkt 137) with active override EoA
#TEST-VAL-SUB026-5934#REF# FCT 2.1, 2.2, 2.4 Due to override retained EoA when SR mode is left to mode with new MA
#TEST-VAL-SUB026-5939#REF# FCT 2.3 NL - due to override retained EoA when SR mode is left
#TEST-VAL-SUB026-5935#REF# FCT 2.5, 2.6 SH, SB - due to override retained EoA when SR mode is left
#TEST-VAL-SUB026-5937#REF# FCT 2.7 SN - due to override retained EoA when SR mode is left
#TEST-VAL-SUB026-5938#REF# FCT 2.8 TR - due to override retained EoA when SR mode is left
#TEST-VAL-SUB026-5936#REF# FCT 2.9 UN - due to override retained EoA when SR mode is left
#TEST-VAL-SUB026-8268#REF# EET CFX00189145 Deletion of former EoA (used as TRIP condition in SR) due to mode change

#REQ-UNISIG-SUB026-3103#REF# 5.8.3.6 #ANA-UNISIG-Override-0001#REF#
The train trip shall be inhibited (suppression of the transition to the Trip mode), and only in level 0, 1, 2, 3, the MRSP shall include the
Override function related Speed Restriction (see 3.11.10) as long as the Override function is active.
see analysis - is realized through the mode transition table, 3.11.10 and 4.5.2
realised by: #REQ-UNISIG-SUB026-3104#REF#
realised by: #REQ-UNISIG-SUB026-3101#REF#
realised by: #REQ-UNISIG-SUB026-2273#REF#
realised by: #REQ-DESIGN-CR-0465#REF#
realised by: #REQ-DESIGN-CR-0459#REF#
realised by: #REQ-DESIGN-CR-0462#REF#
realised by: #REQ-DESIGN-CR-0466#REF#
realised by: #REQ-DESIGN-CR-0467#REF#
realised by: #REQ-DESIGN-CR-0468:01#REF#
realised by: #REQ-UNISIG-SUB026-2244#REF#

#REQ-DESIGN-CR-0183#REF# 5.8.3.7 #REQ-DESIGN-CR-0034#REF#
The status “override active” shall be indicated to the driver.
#TEST-VAL-SUB026-5518#REF# FCT basic function Re-activation of Trip inhibition after Override aktiv in SN

#REQ-UNISIG-SUB026-005982#REF# 5.8.3.8 #REQ-UNISIG-SUB026-010091#REF#
As long as the Override function is active, new SR distance information received from EUROLOOP shall be rejected.
awakening on loop isn't realized

#REQ-UNISIG-SUB026-005984#REF# 5.8.3.9
When “Override” is selected and Override is already active, the supervision of the time and distance (see 5.8.4.1 a) and b)) for train trip
suppression shall be re-started.
#TEST-VAL-SUB026-5940#REF# FCT basic function Re-start of override time and distance supervision when selecting override while override is active

#REQ-DESIGN-CR-0456:02#REF# 5.8.4.1
The Override procedure shall end when at least one of the following conditions is fulfilled:
a)	The "max. time for train trip suppression when Override function is triggered" (national value) elapses after Override has
been selected, OR
b)	The train has run more than the "distance for train trip suppression when Override function is triggered" (national value)
after Override has been selected, OR
c)	The former EOA has been passed with the min safe  antenna position (calculated by subtracting distance between active EUROBALISE antenna
and the front end of the train from the min safe front end position), OR
d)	The train passes a balise group giving “stop in SR” or “stop in SH” information, OR
e)	The train passes a balise group giving proceed information (i.e., MA with no signalling related speed restriction of value zero)
f)	In level 2,3, an MA is received from the RBC
g)	The train passes a balise group not in the list of expected balises in SR mode or the list of expected balises in SH mode
h)	The train overpasses the SR distance supervised before overriding with its estimated front end
i)	The ERTMS/ETCS on-board equipment switches to TR, LS, OS or SH mode.
Rel. 8.0:
modes LS, OS, SH in i) are new (UCR 124).
The other changes are only formal.
TEST APPROACH:
1) The 'max. time for train trip suppression when Override function is triggered' elapses after Override has been selected
2) The train has run more than the 'distance for train trip suppression when Override function is triggered' after Override has been selected
3)The former EOA has been passed with the min safe  antenna position
3.1) current position at override activation considered as EoA
3.2) former EoA
4) The train passes a balise group giving 'stop in SR' or 'stop in SH' information
4.1) stop in SR
4.2) stop in SH
5) The train passes a balise group giving proceed information 
6) In level 2,3, an MA is received from the RBC
7) The train passes a balise group not in the list of expected balises in SR mode or the list of expected balises in SH mode
8) The train overpasses the SR distance supervised before overriding with its estimated front end
8.1) M2 based SR distance
8.2) NV based SR distance
8.3) driver input based SR distance
9) The ERTMS/ETCS on-board equipment switches to TR, LS, OS or SH mode.
9.1) TR
9.2) LS
9.3) OS
9.4) SH
#TEST-VAL-SUB026-5029#REF# FCT 1 T_NVOVTRP
#TEST-VAL-SUB026-5030#REF# FCT 2 D_NVOVTRP
#TEST-VAL-SUB026-4600#REF# FCT 3.1 Mode change SB->SR [37]
#TEST-VAL-SUB026-5031#REF# FCT 3.2 Override, MinFront > EOA
#TEST-VAL-SUB026-4898#REF# FCT 4.1 Transition table 4.6.3 - Conditions 36, 54
#TEST-VAL-SUB026-4899#REF# FCT 4.2 Transition table 4.6.3 - Condition 49
#TEST-VAL-SUB026-5739#REF# FCT 5 Override revoked due to passing a balise group giving proceed information
#TEST-VAL-SUB026-4242#REF# FCT 6 transition FS -> SR -> FS in level 2
#TEST-VAL-SUB026-5503#REF# FCT 7 , CFX00036991 Supression of trip in SR, SH using Override EoA
#TEST-VAL-SUB026-2011#REF# FCT 8.1 Override revocation due to passing for D_SR received from RBC
#TEST-VAL-SUB026-5483#REF# FCT 8.2 End of override when train overpasses the SR distance supervised before overriding with its estimated front end
#TEST-VAL-SUB026-5507#REF# FCT 8.3 End of inhibition to Trip in SR on crossing SR supervised distance
#TEST-VAL-SUB026-4685#REF# FCT 9.1 override indication when entering FS/TR
#TEST-VAL-SUB026-4E18#REF# FCT 9.2 Override active, pass BG with MA with V_MAIN=0 (trip order) plus MP LS with D_MAMODE=0
#TEST-VAL-SUB026-4E17#REF# FCT 9.3 Override active, pass BG with MA with V_MAIN=0 (trip order) plus MP OS with D_MAMODE=0
#TEST-VAL-SUB026-4E19#REF# FCT 9.4 Override active, pass BG with MA with V_MAIN=0 (trip order) plus MP SH with D_MAMODE=0

#REQ-DESIGN-CR-0457#REF# 5.8.4.1.1
Note: For modes UN and SN, only end conditions a) and b) are supervised.
#TEST-VAL-SUB026-5518#REF# FCT SN Re-activation of Trip inhibition after Override aktiv in SN
#TEST-VAL-SUB026-5505#REF# FCT UN Re-activation of Trip inhibition/Supervision of speed when Override aktiv in UN

Chapter 5.9

#REQ-UNISIG-SUB026-0274#REF# 5.9.2.1
In a level 1 area, the beginning of the On Sight area can be the balise (group) that gives the Mode Profile. When the train passes the balise
group and receives this information, the ERTMS/ETCS on-board equipment shall immediately switch to On Sight mode.
Justification: 
The reference to level 1 is not relevant for obu.
realised by: #REQ-UNISIG-SUB026-0803:02#REF#

#REQ-UNISIG-SUB026-3668#REF# 5.9.2.2
In a level 2 or 3 area, the ERTMS/ETCS on-board equipment can receive a mode profile giving an On Sight area which the train has already entered
with its max safe front end. In this case, the ERTMS/ETCS on-board equipment shall immediately switch to On Sight mode.
Justification: 
The reference to level 2/3 is not relevant for obu.
realised by: #REQ-UNISIG-SUB026-0803:02#REF#

#REQ-UNISIG-SUB026-0803:02#REF# zu.5.9.2.1.und.5.9.2.2 #REQ-UNISIG-SUB026-0274#REF#
#REQ-UNISIG-SUB026-3668#REF#
The obu shall immediately switch to On Sight mode, if
- a mode profile giving an On Sight area is received and max safe front end of the train is already inside this area
AND
- the obu is not in the modes SB and PT.
the exception for SB and PT is followed from 5.9.5 (first ACK, than mode change)
TEST APPROACH:
The following aspects have been identified:
1) D_MAMODE > 0
2) D_MAMODE = 0
#TEST-VAL-SUB026-5038#REF# FCT 1 OS mode not acknowleged in time
#TEST-VAL-SUB026-5037#REF# FCT 2 Reception of MP-OS for current location from BG
#TEST-VAL-SUB026-5457#REF# EET CFX00040274 Multiple mode transition LS/OS

#REQ-UNISIG-SUB026-0275#REF# 5.9.2.3 #REQ-DESIGN-CR-0051:01#REF#
The driver must acknowledge the On Sight mode. A request of acknowledgement shall be displayed to the driver.
TEST APPROACH:
The following aspects have been identified:
1) D_MAMODE > 0
2) D_MAMODE = 0
#TEST-VAL-SUB026-5038#REF# FCT 1 OS mode not acknowleged in time
#TEST-VAL-SUB026-5037#REF# FCT 2 Reception of MP-OS for current location from BG

#REQ-UNISIG-SUB026-0276:01#REF# 5.9.2.4 #REQ-UNISIG-SUB026-007978#REF#
If the driver has not acknowledged after the driver acknowledgement time (refer to Appendix A.3.1), the service brake command shall be
triggered. The brake command is released when the driver acknowledges, except if brakes are also applied for another reason(s).
realised by: #REQ-DESIGN-CR-0096:01#REF#

#REQ-DESIGN-CR-0052#REF# 5.9.2.7
If the ERTMS/ETCS on-board equipment is already in OS mode when receiving the OS mode profile, no further acknowledgement shall be requested
from the driver.
TEST APPROACH:
The following aspects have been identified:
1) D_MAMODE > 0
2) D_MAMODE = 0
3) special case overlapping MP
#TEST-VAL-SUB026-5128#REF# FCT 1 Ack-OS vor OS-Area, dann erneut MA+OS
#TEST-VAL-SUB026-5508#REF# FCT 2 No Ack in OS Mode if already in OS Mode
#TEST-VAL-SUB026-5546#REF# FCT 3 two overlapping MP-OS area (different V_MAMODE)
#TEST-VAL-SUB026-5530#REF# EET error expectation Display of Ack OS msg when existing mode is OS
#TEST-VAL-SUB026-5776#REF# FCT error expectation OBU is already in OS mode when receiving the OS mode profile

#REQ-UNISIG-SUB026-0277:01#REF# 5.9.3.2
A request for acknowledgement shall be displayed to the driver when the following conditions are fulfilled:
a)	 The distance between the estimated front end of the train and the beginning of On Sight area is shorter than a value, contained in the
mode profile.
b)	The speed is lower than the On Sight mode speed limit (national value, or value given in the mode profile).
c)	The current mode is not On Sight
TEST APPROACH:
The following aspects have been identified:
1) The distance between the estimated front end of the train and the beginning of On Sight area is shorter than a value, contained in the mode
profile.
2) The speed is lower than the On Sight mode speed limit
2.1) national value
2.2) value given in the mode profile
3) The current mode is not On Sight
#TEST-VAL-SUB026-5039#REF# FCT 1 Test 'rectangle of acknowledgement', acknowledgement request not taken back after leaving the rectangle
#TEST-VAL-SUB026-5253#REF# FCT 2.1 Train reaches OS acknowledment window with speed > V_NVONSIGHT
#TEST-VAL-SUB026-8134#REF# FCT 2.2 No OS acknowledgment request when entering acknowledgment window if train speed exceeds V_MAMODE (/=127)
#TEST-VAL-SUB026-3778#REF# FCT 3 , CFX00039908 Entry into OS acknowledgment window for further OS area in OS (gap between OS areas)
#TEST-VAL-SUB026-5545#REF# EET error expectation two MP-OS acknowledgment area second OS area starts in first OS area

#REQ-UNISIG-SUB026-0278#REF# 5.9.3.4
Once the acknowledgement request is displayed, it is not taken back if the train leaves the “rectangle of acknowledgement” (for example: because
the train accelerates).
TEST APPROACH:
The following aspects have been identified:
1) speed condition not fulfilled anymore 
2) location condition not fulfilled anymore 
3) condition for mode change not valid any more
#TEST-VAL-SUB026-5039#REF# FCT 1 Test 'rectangle of acknowledgement', acknowledgement request not taken back after leaving the rectangle
#TEST-VAL-SUB026-5254#REF# FCT 2 Once the OS acknowledgment request is displayed, it is not taken back if the train sets back out of ack window
#TEST-VAL-SUB026-5419#REF# FCT 3 pass OS area without OS acknowledgement
#TEST-VAL-SUB026-5526#REF# EET error expectation OS acknowledgment if OS area entry is not feasible anymore
#TEST-VAL-SUB026-7153#REF# EET error expectation Concurrent revocation of MP and driver acknowledgment

#REQ-DESIGN-CR-0360:01#REF# 5.9.3.5
Until the ERTMS/ETCS on-board equipment has switched to OS mode, according to the mode profile, the beginning of the On Sight area shall be
temporarily considered either as the EOA (keeping the SvL given by the MA) or as both the EOA and SvL (instead of the EOA and SvL given by the
MA), with no Release Speed.
UNISIG clarification:
"with no release speed" is valid for both conditions
TEST APPROACH:
The speed and distance monitoring evaluates the targets mode independent refer to SUBSET-026 3.13. The actual brake curve calculation is tested
by the appropriated module tests. The test outlined here has to be ensured that the EoA, SvL and release speed provided to the module BC agree
with the requirement.
The following aspects have been identified:
1) Q_MAMODE dependency (black box)
2) EOA and SvL depending on Q_MAMODE (BC input)
3) no release speed
#TEST-VAL-SUB026-5763#REF# FCT 1 Start of OS area supervision
#TEST-VAL-SUB026-5759#REF# FCT 2 OS area start considered either as the EOA (keeping the SvL given by the MA) or as both the EOA and SvL depending on Q_MAMODE
#TEST-VAL-SUB026-5767#REF# FCT 3 Start of MP-OS supervised without release speed
#TEST-VAL-SUB026-5131#REF# EET CFX00033034 Release Speed und OS-Bereich

#REQ-UNISIG-SUB026-0280#REF# 5.9.3.6 #REQ-DESIGN-CR-0051:01#REF#
When the driver acknowledges the On Sight mode, the ERTMS/ETCS on-board equipment shall immediately switch to the On Sight mode.

#DSC-UNISIG-SUB026-006050#REF#

Figure 5: Transition from FS/LS to OS mode after driver acknowledgement
TEST APPROACH:
Following aspects have been identified:
1) current speed above V_MAMODE
2) current speed below V_MAMODE
#TEST-VAL-SUB026-5039#REF# FCT 1 Test 'rectangle of acknowledgement', acknowledgement request not taken back after leaving the rectangle
#TEST-VAL-SUB026-5040#REF# FCT 2 Test 'rectangle of acknowledgement' speed above V_MAMODE (OS)

#REQ-UNISIG-SUB026-0805#REF# 5.9.3.7 #REQ-UNISIG-SUB026-0582#REF#
If the max safe front end of the train reaches the beginning of the On Sight area according to the mode profile and the driver has not yet
acknowledged, the ERTMS/ETCS on-board equipment shall switch immediately to OS mode and a request for acknowledgement shall be displayed to the
driver (refer to SRS chapter 4, transitions between modes).
TEST APPROACH:
Following aspects have been identified:
1) current speed above V_MAMODE
2) current speed below V_MAMODE
#TEST-VAL-SUB026-5041#REF# FCT 1 Erreichen einer OS-Area
#TEST-VAL-SUB026-4327#REF# FCT 2 Release speed given by the MA not taken into account FS->OS (level2)
#TEST-VAL-SUB026-5501#REF# EET error expectation Two OS-Areas

#REQ-UNISIG-SUB026-0806:01#REF# 5.9.3.8
If, in this case, the driver does not acknowledge within the driver acknowledgement time (refer to Appendix A.3.1) after the change to OS mode,
the service brake command shall be triggered. The command shall be released as soon as the driver acknowledges (unless the command was triggered
also for other reasons).
realised by: #REQ-DESIGN-CR-0096:01#REF#

#REQ-DESIGN-CR-0096:01#REF# to.5.9.3.8 #REQ-UNISIG-SUB026-0276:01#REF#
#REQ-UNISIG-SUB026-0806:01#REF#
#ANA-UNISIG-ModeProfile-0002#REF#
If the driver does not acknowledge within the driver acknowledgement time (refer to Appendix A.3.1)  after the change to OS mode, the service
brake command shall be triggered. The command shall be released as soon as the driver acknowledges (unless the command was triggered also for
other reasons) or the acknowledgement is not possible anymore.
realizes 5.9.2.4 and 5.9.3.8
TEST APPROACH:
The following aspects have been identified:
1) OS mode requested for a further location 
2) OS mode requested for a further current location
3) Brake command was triggered also for other reasons
#TEST-VAL-SUB026-5244#REF# FCT 1 Mode transition to OS driver does not acknowledges in time
#TEST-VAL-SUB026-4328#REF# FCT 2 L1 mode transition SR->OS[40], info from BG D_MAMODE=0, service brake after 5 sec
#TEST-VAL-SUB026-7039#REF# FCT 3 Brake due to missing OS acknowledgment and over speed in OS
#TEST-VAL-SUB026-5038#REF# EET error expectation OS mode not acknowleged in time
#TEST-VAL-SUB026-5245#REF# EET error expectation Reception of new MP-OS before driver acknowledgment for entered OS area
#TEST-VAL-SUB026-5499#REF# EET error expectation Release of serviceBrake done if OS acknowledgment is not feasible
#TEST-VAL-SUB026-7665#REF# EET error expectation SB handling when driver does not acknowledge within the driver acknowledgement time: OS
#TEST-VAL-SyAnfSpezCR-0046#REF# EET error expectation Removing on sight acknowledge requests im OS-Bereich durch Wechsel nach Level0

#REQ-DESIGN-CR-0168#REF# 5.9.4.1
The mode profile with regards to an OS area is only evaluated in levels 1,2,3, although the mode profile may have been received in level 0
(Unfitted mode) or NTC (SN mode). A transition to On Sight mode can therefore earliest occur at a transition of level: from level 0 or NTC to
level 1 or 2 or 3.
realized through acceptance of mode profile and mode transitions
realised by: #REQ-DESIGN-CR-0049#REF#
realised by: #REQ-DESIGN-CR-0343:01#REF#
realised by: #REQ-UNISIG-SUB026-3484#REF#

#REQ-DESIGN-CR-0054#REF# 5.9.5.1 #REQ-UNISIG-SUB026-1102:01#REF#
#REQ-DESIGN-CR-0137:02#REF#
When performing a SoM or a Train Trip procedure and when the current level is 2 or 3, the ERTMS/ETCS on-board equipment can receive a mode
profile giving an On Sight area which the train has already entered with its max safe front end. In this case, the ERTMS/ETCS on-board equipment
shall first require an acknowledgement from the driver.
realised by: #REQ-UNISIG-SUB026-3695#REF#

#REQ-UNISIG-SUB026-3695#REF# 5.9.5.1 #REQ-DESIGN-CR-0054#REF#
#REQ-DESIGN-CR-0051:01#REF#
#REQ-UNISIG-SUB026-010419#REF#
#ANA-UNISIG-Procedure-0001#REF#
If a mode profile requiring On Sight is accepted in the modes SB or PT and the train has already entered the mode profile area with its max safe
front end, the ERTMS/ETCS on-board equipment shall first require an ackowledgement from the driver.

Remark: The mode change to On Sight is execute after the ackowledgement from the driver (see condition[15] in 4.6.3).
gilt auch bei Erhalt eines Modeprofils vor Betätigen der Start-Taste
TEST APPROACH:
The following aspects have been identified:
1) PT
1.1) START selected
1.2) START not selected
2) SB
2.1) START selected
2.2) START not selected
#TEST-VAL-SUB026-4654#REF# FCT 1.1 PT->OS[15]
#TEST-VAL-SUB026-5420#REF# FCT 1.2 Ueberpruefung des Zustanddiagramms 5.9.7 Mode PT
#TEST-VAL-SUB026-5401#REF# FCT 2.1 SOM - L2/OS
#TEST-VAL-SUB026-5577#REF# FCT 2.2 transition from SB to OS, SoM beyond S20
#TEST-VAL-SUB026-5623#REF# EET error expectation Acknowledging of OS after leaving OS area

#REQ-DESIGN-CR-0055#REF# 5.9.5.2
When the driver acknowledges, the ERTMS/ETCS on-board equipment shall perform the transition to On Sight mode.”
realizes through 4.6.3, condition [15]
realised by: #REQ-UNISIG-SUB026-2220#REF#

#REQ-UNISIG-SUB026-0282#REF# 5.9.6.1.1 #REQ-UNISIG-SUB026-0583#REF#
The ERTMS/ETCS on-board equipment exits the On Sight mode when the min safe front end of the train passes the end of the On Sight area.
#TEST-VAL-SUB026-5451#REF# EET CFX00039089 Already acknowledged MP from infill BG repeated by main BG
#TEST-VAL-SUB026-3141#REF# FCT basic function Start and end of mode profile
#TEST-VAL-SUB026-5419#REF# EET error expectation pass OS area without OS acknowledgement
#TEST-VAL-SyAnfSpezCR-0018#REF# EET error expectation Verlaengerung des OS Bereiches ohne erneute Quittierungsaufforderung

#REQ-DESIGN-CR-0633:01#REF# 5.9.6.3.2
When exiting the On Sight area, the ERTMS/ETCS on-board equipment switches either to Full Supervision, to Limited Supervision or to Shunting
mode (refer to SRS chapter 4, transitions between modes).
realised by: #REQ-UNISIG-SUB026-2279#REF#
realised by: #REQ-DESIGN-CR-0593#REF#
realised by: #REQ-UNISIG-SUB026-3503:01#REF#

Chapter 5.10

#REQ-UNISIG-SUB026-0816#REF# 5.10.1.3 #REQ-UNISIG-SUB026-3331:01#REF#
When the ERTMS/ETCS on-board equipment receives a level transition announcement, and if this announcement will result in a change of the
on-board level, it shall immediately inform the driver about the announced level transition.
TEST APPROACH:
The following aspects have been identified:
1) announcement results in a change of the level
2) announcement results not in a change of the level
#TEST-VAL-SUB026-5661#REF# FCT 1 Indication of level transition to the driver
#TEST-VAL-SUB026-3415#REF# FCT 2 level_choice according to Table of priority defined by P41 (no level change)
#TEST-VAL-SUB026-7056#REF# EET error expectation Level transition announcement in SB

#REQ-UNISIG-SUB026-0818#REF# 5.10.1.5
If the message from the border balise group is not received, the level transition shall still be executed when the estimated front end passes
the location given in the announcement.
#TEST-VAL-SUB026-5056#REF# FCT basic function Execution of level transition, if the message from the border balise group is not received
#TEST-VAL-SUB026-7067#REF# EET error expectation Level transition announcement with D_LEVELTR=0

#REQ-UNISIG-SUB026-0819#REF# 5.10.1.6
The on-board equipment shall manage only one level transition order at a time. Therefore a new level transition order shall replace a previously
received order, i.e. if a new order to switch to a different level or to the same level but at a different location is received, before the
action from the first order has been performed, only the last order shall be executed.
TEST APPROACH:
The following aspects have been identified:
1) new LTO to other level
2) new LTO to other location
#TEST-VAL-SUB026-5057#REF# FCT 1 New level transition order to different level replaces the previous received one
#TEST-VAL-SUB026-5129#REF# FCT 2 New level transition order to different location replaces the previous received one
#TEST-VAL-SUB026-7170#REF# EET CFX00177664 Outage of NTC in level transition announcement phase (ToP NTC, L0)
#TEST-VAL-SUB026-7172#REF# EET CFX00177664 Outage of NTC in level transition announcement phase (ToP NTC(1), NTC(2))
#TEST-VAL-SUB026-7819#REF# EET error expectation Level and mode acknowledgements in the list of acknowledgements
#TEST-VAL-SUB026-7828#REF# EET error expectation Mode acknowledgement followed by 2 level acknowledgements

#REQ-UNISIG-SUB026-006118#REF# 5.10.1.6.1
In Shunting and Passive Shunting modes only one set of Level Transition Information shall be stored at a time. Therefore a set of Level
Transition Information received shall replace any Level Transition Information already stored on-board.
#TEST-VAL-SUB026-5942#REF# FCT PS Reception of several LTO in PS, no supervision safe radio connection
#TEST-VAL-SUB026-5943#REF# FCT SH Reception of several LTO in SH

#REQ-UNISIG-SUB026-0820#REF# 5.10.1.7
As soon as the announcement of the level transition has been received, some data (mainly movement authority and track description data) from the
transmission media of the new level shall be accepted, but shall not be used until the level transition is effective.
realizes through table 4.8.3 exception[1] and [2]
realised by: #REQ-UNISIG-SUB026-1200:01#REF#

#REQ-UNISIG-SUB026-0821#REF# 5.10.1.8
When the onboard has performed the level transition, further data (mainly movement authority and track description data) received from the
transmission media of the level being left shall be rejected.
realizes through table 4.8.3
realised by: #REQ-UNISIG-SUB026-1200:01#REF#

#REQ-UNISIG-SUB026-0823#REF# 5.10.2.3
The table of priority shall list all the supported levels from the highest priority level to the lowest one.
#ANALYSE-VALUNISIG-4184#REF# FCT The requirement has to be fulfilled by track side, the OBU has to take the definition into account when evaluating the table of priority refer #REQ-UNISIG-SUB026-0824#REF#. The validation of the OBU requirement takes place via #REQ-UNISIG-SUB026-0824#REF#.

#REQ-UNISIG-SUB026-0824#REF# 5.10.2.4
When receiving the information about all ERTMS/ETCS levels that are supported by trackside, the ERTMS/ETCS on-board equipment shall select from
the table the level with the highest priority, which is available for use by the onboard equipment.
TEST APPROACH:
The following aspects have been identified:
1) OBU equipped for highest ToP entry
2) OBU not equipped for highest ToP entry
2.1) highest ToP ETCS Level 0 1, 2, or 3
2.2) highest ToP entry NTC
#TEST-VAL-SUB026-5062#REF# FCT 1 Level transition according to ToP
#TEST-VAL-SUB026-5061#REF# FCT 2.1 Table of Priority (L2/L1), L2 not supported, level change L0->L1
#TEST-VAL-SUB026-5660#REF# FCT 2.2 Level transition depending on table of priority and available STM

#REQ-UNISIG-SUB026-006146#REF# 5.10.2.4.1
The on-board equipment shall consider an ERTMS/ETCS level as “Available for use” as follows:
a)	Level 2 or 3: the level is configured on-board and at least one Mobile Terminal is available on-board, i.e. the ETCS onboard has
detected at least one Mobile Terminal in working condition, independently whether it is registered to a network or not.
b)	Level NTC: the concerned National System is available on-board (if an STM is used, refer to SUBSET-035 for further details).
c)	Level 0 or 1: always.
UNISIG clarifcation:
is  only relevant for level selection due to driving transition.
TEST APPROACH:
Note: Point c) is no restriction and is hence omitted by the refinement.
realised by: #REQ-DESIGN-CR-0558#REF#
realised by: #REQ-UNISIG-SUB026-3643#REF#

#REQ-DESIGN-CR-0558#REF# to.5.10.2.4.1 #REQ-UNISIG-SUB026-006146#REF#
The on-board equipment shall consider Level 2 or 3 as “Available for use” only, if the level is configured on-board and at least one Mobile
Terminal is available on-board, i.e. the ETCS onboard has detected at least one Mobile Terminal in working condition, independently whether it
is registered to a network or not.

remark: This requirement is valid for the evaluation of a level transition order from trackside only (see #REQ-UNISIG-SUB026-0824#REF#).
TEST APPROACH:
The following aspects have been identified:
1) L2 not configured
2) L2 configured, but no Mobile Terminal in working condition
3) L2 configured, Mobile Terminal in work condition but not registered to network

Note: The evaluation of the mobile outage indication is suppressed during the start-up phase (currently for 3min after start-up) 
#TEST-VAL-SUB026-5061#REF# FCT 1 Table of Priority (L2/L1), L2 not supported, level change L0->L1
#TEST-VAL-SUB026-7700#REF# FCT 2 Level 2 and 3 not available when no mobile terminal is in working condition(neither mobile one nor mobile two)
#TEST-VAL-SUB026-5599#REF# FCT 3 Levels 2 or 3 are available when mobile terminal is not registered but in working condition
#TEST-VAL-SUB026-5463#REF# EET CFX00040043 OBU configured for L0/L1 only, processing of level transition order L2

#REQ-UNISIG-SUB026-3643#REF# to.5.10.2.4.1 #REQ-UNISIG-SUB026-006146#REF#
#ANA-UNISIG-TrainData-0002:01#REF#
The on-board equipment shall consider Level NTC as “Available for use” only, if the onboard equipment is allowed to use level STM and the stm id
in the table of priority is existed in the list of "available" STMs (see /UNISIG SUBSET 035/, 7.4.1.1.4).

remark: The requirement is valid for the evaluation of a level transition order from trackside only (see #REQ-UNISIG-SUB026-0824#REF#).
TEST APPROACH:
Following aspects have been identified:
1) STM available
2) STM unavailable
#TEST-VAL-SUB026-5589#REF# FCT 1 Leveltransition to STM, (STM-Id from TOP in STM available List, state DA)
#TEST-VAL-SUB026-5590#REF# FCT 2 Level transition to STM (STM-Id from TOP not in STM supported List)

#REQ-UNISIG-SUB026-0825#REF# 5.10.2.5
When the onboard has selected the level it will switch to, it shall carry out the level transition as if it has received a level transition
order to this level only i.e. it shall ignore the requirements related to transitions to the other levels.
TEST APPROACH:
Following aspects have been identified:
selected ETCS level
1) NTC
2) L0
3) L1
4) L2
5) L3
#TEST-VAL-SUB026-5660#REF# FCT 1 Level transition depending on table of priority and available STM
#TEST-VAL-SUB026-4598#REF# FCT 2 LTO - only information for selected destination level accepted L1->L0
#TEST-VAL-SUB026-4596#REF# FCT 3 LTO - only information for selected destination level accepted L0->L1
#TEST-VAL-SUB026-4597#REF# FCT 4 LTO - only information for selected destination level accepted LSTM->L2
#TEST-VAL-SUB026-8131#REF# FCT 5 LTO - only information for selected destination level accepted LSTM->L3

#REQ-UNISIG-SUB026-0826#REF# 5.10.2.6
The ERTMS/ETCS on-board equipment shall inform the driver about the selected level transition only.
#TEST-VAL-SUB026-5061#REF# FCT basic function Table of Priority (L2/L1), L2 not supported, level change L0->L1

#REQ-UNISIG-SUB026-0827#REF# 5.10.2.7
If none of the ordered level(s) is available for use by the ERTMS/ETCS on-board equipment, it shall nevertheless make the transition, to the
ordered level with the lowest priority.
#TEST-VAL-SUB026-5063#REF# FCT basic function OBU equipment is not fitted for any of the announced level

#REQ-UNISIG-SUB026-3758:01#REF# to.5.10.2.7 #ANA-UNISIG-Leveltransition-0002:02#REF#
If the on-board is changed to a not supported level or to a not available STM, the on-board shall command a brake to standstill.

SB shall be used for a change to a not supported ETCS Level (L0/1/2/3). Otherwise the EB shall be used.
TEST APPROACH:
The following aspects have been identified:
1) SB - not supported ETCS Level (L0/1/2/3)
1.1) L0
1.2) L1
1.3) L2
1.4) L3
2) EB - NTC
#TEST-VAL-SUB026-3B60#REF# FCT 1.1 Service Brake triggered due to transition to unsupported Level 0
#TEST-VAL-SUB026-3917#REF# FCT 1.2 Brake triggered due to entry into unsupported Level L1, brake release due to entry into supported level
#TEST-VAL-SUB026-3B61#REF# FCT 1.3 Service Brake triggered due to transition to unsupported Level 2
#TEST-VAL-SUB026-3841#REF# FCT 1.4 Brake command due to transition to L3 and brake release after execution of LTO L2
#TEST-VAL-SUB026-3856#REF# FCT 2 Brake triggered due to transition to not supported NTC, revoked after transition to available NTC
#TEST-VAL-SUB026-5596#REF# FCT error expectation Level transition to not supported level L1 without MA

#REQ-UNISIG-SUB026-0828#REF# 5.10.2.8
The ERTMS/ETCS on-board equipment shall store the table of priority of trackside supported ERTMS/ETCS levels.
#ANALYSE-VALUNISIG-4192#REF# FCT The requirement is tested via verification of #REQ-DESIGN-CR-0067:02#REF#/#REQ-UNISIG-SUB026-010454#REF# (table 4.10.1.3).

#REQ-DESIGN-CR-0574#REF# to.5.10.2.8
If the level transition order concerns the transition to the ETCS level currently used on-board, the table of priority shall be stored
nevertheless at the position from the level transition order.
UNISIG clarification:
5.10.2.8 is apply also for a LTO to the same Level but with a different table of priority
TEST APPROACH:
Following aspects have been identified:
ETCS level currently used on-board
1) NTC
2) L0
3) L1
4) L2
5) L3
#TEST-VAL-SUB026-5423#REF# FCT 1 Change of table of priority by level transition order not causing to current level
#TEST-VAL-SUB026-3421#REF# FCT 2 Table of priority wird aktualisiert, wenn Level nicht gewechselt wird (L0)
#TEST-VAL-SUB026-3420#REF# FCT 3 Table of priority updated, although accepted LT order does not causes a level change (L1)
#TEST-VAL-SUB026-3415#REF# FCT 4 level_choice according to Table of priority defined by P41 (no level change)
#TEST-VAL-SUB026-8132#REF# FCT 5 level_choice according to Table of priority defined by P41 (no level change in L3)

#REQ-DESIGN-CR-0153#REF# 5.10.3.1.3
When the ERTMS/ETCS communication session is open, Train Data shall be sent to the RBC (which acknowledges the data) unless the onboard
equipment is in SL or NL mode.
realised by: #REQ-DESIGN-CR-0748:02#REF#

#REQ-UNISIG-SUB026-0291#REF# 5.10.3.1.4
If no Level 2/3 MA and track description has been received when entering the new area, the train shall still be supervised according to the
level 1 MA previously received.

--- FINALISED ---
Die Gültigkeit von MA-Daten soll entsprechend 4.9 (hier speziell 4.9.1.4) und 4.10 nur modeabhängig, nicht jedoch bei einem Levelwechsel neu
bewertet werden.
#ANALYSE-VALUNISIG-4117#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-0292#REF# 5.10.3.1.5
When the ERTMS/ETCS on-board equipment has switched to the new level, it shall report the new on-board level, including a position report.
is realized through line "report train when change  of level due to trackside order" in 4.5.2
realised by: #REQ-UNISIG-SUB026-1025:02#REF#

#REQ-DESIGN-CR-0154#REF# 5.10.3.2.2
When the ERTMS/ETCS communication session is open, Train Data shall be sent to the RBC (which acknowledges the data) unless the onboard
equipment is in SL or NL mode.
realised by: #REQ-DESIGN-CR-0748:02#REF#

#REQ-UNISIG-SUB026-0294#REF# 5.10.3.2.3
A level 2/3 MA and track description information shall be received from the RBC before the level transition border. If not, the train shall be
tripped at passage of the border, i.e. after switching to level 2 or 3, movement is not allowed without a movement authority (refer to SRS
chapter 4, transitions between modes).
realised by: #REQ-UNISIG-SUB026-2245#REF#

#REQ-UNISIG-SUB026-0295#REF# 5.10.3.2.5
When the ERTMS/ETCS on-board equipment has switched to the new level, it shall report the new on-board level, including a position report.
is realized through line "report train when change  of level due to trackside order" in 4.5.2
realised by: #REQ-UNISIG-SUB026-1025:02#REF#

#REQ-UNISIG-SUB026-0831#REF# 5.10.3.3.2
If no Level 1 MA and track description has been received when entering the new area, the train shall still be supervised according to the level
2/3 MA previously received from the RBC.

--- FINALISED ---
Die Gültigkeit von MA-Daten soll entsprechend 4.9 (hier speziell 4.9.1.4) und 4.10 nur modeabhängig, nicht jedoch bei einem Levelwechsel neu
bewertet werden.
#ANALYSE-VALUNISIG-4118#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB026-0297#REF# 5.10.3.3.3
When the train has passed the level transition border with its min safe rear end, i.e. when the whole train has left the level 2/3 area, the
onboard equipment of the leading engine shall send a position report to the RBC.
is realized through 3.6.5.1.4 f)
realised by: #REQ-UNISIG-SUB026-3025#REF#

#REQ-UNISIG-SUB026-0298#REF# 5.10.3.4.1
A level 1 MA and track description information shall be received before or at the level transition border. If not, when the level transition is
performed, the train shall be tripped, i.e. after switching to level 1, movement is not allowed without a movement authority (refer to SRS
chapter 4, transitions between modes).
realizes through mode transition table, condition[39]
realised by: #REQ-UNISIG-SUB026-2245#REF#

#REQ-UNISIG-SUB026-0301#REF# 5.10.3.6.2
When the train has passed the level transition border with its min safe rear end, i.e. when the whole train has left the level 2/3 area, the
onboard equipment of the leading engine shall send a position report to the RBC.
realised by: #REQ-UNISIG-SUB026-3025#REF#

#REQ-DESIGN-CR-0155#REF# 5.10.3.7.2
When the ERTMS/ETCS communication session is open, Train Data shall be sent to the RBC (which acknowledges the data) unless the onboard
equipment is in SL or NL  mode.
realised by: #REQ-DESIGN-CR-0748:02#REF#

#REQ-UNISIG-SUB026-0304#REF# 5.10.3.7.3
A level 2/3 MA and track description information shall be received from the RBC before the level transition border. If not, the train shall be
tripped at passage of the border, i.e. after switching to level 2 or 3, movement is not allowed without a movement authority (refer to SRS
chapter 4, transitions between modes).
realizes through mode transition table, condition[39]
realised by: #REQ-UNISIG-SUB026-2245#REF#

#REQ-UNISIG-SUB026-3594#REF# 5.10.3.7.5
When the level transition location is passed with the estimated front end a position report shall be sent to the RBC. In case the ERTMS/ETCS
on-board equipment is interfaced to the National System through an STM, please refer to SUBSET-035 for the STM state transition order.
the part pr sending is is realized through line "report train when change	of level due to trackside order" in 4.5.2
realised by: #REQ-UNISIG-SUB026-1025:02#REF#

#REQ-UNISIG-SUB026-0306#REF# 5.10.3.8.1
A level 1 MA and track description information shall be received before or at the level transition border. If not, when the level transition is
performed, the train shall be tripped, i.e. after switching to level 1, movement is not allowed without a movement authority (refer to SRS
chapter 4, transitions between modes).
realizes through mode transition table, condition[39]
realised by: #REQ-UNISIG-SUB026-2245#REF#

#REQ-UNISIG-SUB026-2404#REF# 5.10.3.10.3
When the train has passed the level transition border with its min safe rear end, i.e. when the whole train has left the level 2/3 area, the
onboard equipment of the leading engine shall send a position report to the RBC.
is realized through 3.6.5.1.4 f)
realised by: #REQ-UNISIG-SUB026-3025#REF#

#REQ-DESIGN-CR-0473#REF# 5.10.3.14.1
When the ERTMS/ETCS on-board equipment accepts a conditional level transition order the onboard shall check whether the current level is
contained in the priority list of the conditional level transition order.
#TEST-VAL-SUB026-5512#REF# FCT basic function Conditional Level Transition Order (L1/L2), effect on existing level (L1)

#REQ-DESIGN-CR-0474#REF# 5.10.3.14.2
If the current level is contained in the priority list of the conditional level transition order, the onboard shall not change the level.
TEST APPROACH:
Following aspects have been identified:
current ETCS level
1) NTC
2) L0
3) L1
4) L2
5) L3
#TEST-VAL-SUB026-5421#REF# FCT 1 Conditional level transition order to/from NTC (same STM-Id)
#TEST-VAL-SUB026-5422#REF# FCT 2 Conditional level transition order in L0, effect on existing level
#TEST-VAL-SUB026-5512#REF# FCT 3, 4 Conditional Level Transition Order (L1/L2), effect on existing level (L1)
#TEST-VAL-SUB026-8133#REF# FCT 5 Conditional Level Transition Order to/from L3

#REQ-DESIGN-CR-0475#REF# 5.10.3.14.3
If the current level is not contained in the priority list of the conditional level transition order, the onboard shall evaluate the conditional
level transition order in the same way as an immediate level transition order (see section 5.10.2).
TEST APPROACH:
Following aspects have been identified:
conditional level transition order to ETCS level
1) NTC
2) L0
3) L1
4) L2
5) L3
#TEST-VAL-SUB026-5421#REF# FCT 1, 2 Conditional level transition order to/from NTC (same STM-Id)
#TEST-VAL-SUB026-5422#REF# FCT 3 Conditional level transition order in L0, effect on existing level
#TEST-VAL-SUB026-5512#REF# FCT 4 Conditional Level Transition Order (L1/L2), effect on existing level (L1)
#TEST-VAL-SUB026-8133#REF# FCT 5 Conditional Level Transition Order to/from L3

#REQ-DESIGN-CR-0476#REF# 5.10.3.14.4
In the same way as for a level transition order, the ERTMS/ETCS on-board equipment shall store the table of ERTMS/ETCS levels supported by
trackside.
TEST APPROACH:
Following aspects have been identified:
conditional level transition order in ETCS level
1) NTC
2) L0
3) L1
4) L2
5) L3
#TEST-VAL-SUB026-5421#REF# FCT 1, 4 Conditional level transition order to/from NTC (same STM-Id)
#TEST-VAL-SUB026-5422#REF# FCT 2 Conditional level transition order in L0, effect on existing level
#TEST-VAL-SUB026-5512#REF# FCT 3 Conditional Level Transition Order (L1/L2), effect on existing level (L1)
#TEST-VAL-SUB026-8133#REF# FCT 5 Conditional Level Transition Order to/from L3

#REQ-DESIGN-CR-0735:02#REF# 5.10.3.15.2 #REQ-UNISIG-SUB026-004162#REF#
If the driver changes the level to 2 or 3, the ERTMS/ETCS on-board equipment shall establish a communication session with the RBC:
a)	immediately if at least one Mobile Terminal is registered to a Radio Network and a valid RBC ID/ phone number is available, OR
b)	once the driver has selected the RBC contact information (by the same means as for Start of Mission), if either no Mobile Terminal is
registered to a Radio Network or no valid RBC ID/phone number is available.
TEST APPROACH:
The following aspects were identified:
1) at least one Mobile Terminal is registered and valid RBC ID / Phone Number available
2) no mobile terminal is registered to a radio network
3) at least one mobile terminal is registered to a radio network
3.1) unknown RBC-ID/phone number 
3.2) invalid RBC-ID/phone number
#TEST-VAL-SUB026-3586#REF# FCT 1 OBU establishes communication session due to manual level change L1->L2
#TEST-VAL-SUB026-7937#REF# FCT 2 Manual level choice - no mobiles registered
#TEST-VAL-SUB026-3587#REF# FCT 3.1 OBU establishes communication session due to manual level change L0->L2
#TEST-VAL-SUB026-4029#REF# FCT 3.2 Manual level choice - RBC ID/phone number invalid
#TEST-VAL-SUB026-5450#REF# EET CFX00039893 Enter/re-enter the RBC contact information not offered if the driver changes the level to 2 and valid RBC ID/ phone number available
#TEST-VAL-SUB026-4213#REF# EET error expectation RBC contact information input possible during manual level transition to L2 - data memorized

#REQ-UNISIG-SUB026-3117#REF# to.5.10.3.15.2 #ANA-UNISIG-ManualLeveltransition-0002#REF#
If the driver changed the level during a level transition announce, the manual level transition shall be interpreted as an immediately level
transition order.

Justification:
if the selected level from the driver was an other level as the announced level, the level transition announce shall be deleted  (see 4.8.5.4
a).
If the selected level from the driver was the same level as the announced level, the level transition buffer shall be evaluated immediately.
TEST APPROACH:
The following aspects have been identified:
1) driver selects an other level as the announced level
2) driver selects announced level
#TEST-VAL-SUB026-5549#REF# FCT 1 manual level transition interpreted as a immediately level transition order - SN/STM -> TR/L2
#TEST-VAL-SUB026-5548#REF# FCT 2 manual level transition interpreted as a immediately level transition order - SN/STM -> OS/L2

#REQ-UNISIG-SUB026-0287#REF# 5.10.3.15.3
If the driver changes the level from 2 or 3 to any other, the ERTMS/ETCS on-board equipment shall report the new level to the RBC if a
communication session is established. When receiving the level change report, the RBC shall order the communication session to be terminated.
realizes through 4.5.2 - PR  when level change of level due to driver request

second part is only trackside
realised by: #REQ-UNISIG-SUB026-1026:02#REF#

#REQ-UNISIG-SUB026-006336#REF# to.5.10.3.15.3
The position report after the driver has changed the level from 2 or 3 to any other level shall be interpreted as an exit report from a RBC
area.

remark: This means, that the on board unit wait for the termination order from RBC in the same way as described in 3.5.5.1 e).
UNISIG clarification:
the degraded situation isn't described - see UCR 991
TEST APPROACH:
Following aspects have been identified:
transition to ETCS level
1) NTC
2) L0
3) L1
#TEST-VAL-SUB026-7697#REF# FCT 1 Manual level transition L2->NTC RBC does not order termination of connection
#TEST-VAL-SUB026-7695#REF# FCT 2 Manual level transition L2->L0 RBC does not order termination of connection
#TEST-VAL-SUB026-7696#REF# FCT 3 Manual level transition L2->L1 RBC does not order termination of connection

#REQ-UNISIG-SUB026-2211:01#REF# 5.10.4.1
If defined so for the level transition (see table below), the driver shall be requested to acknowledge the transition
a)	when the max safe front end of the train has passed a trackside defined location in rear of the level transition border
b)	upon receipt of the order to switch to the new level immediately
realised by: #REQ-DESIGN-CR-0733:01#REF#

#REQ-DESIGN-CR-0733:01#REF# 5.10.4.1 #REQ-UNISIG-SUB026-2211:01#REF#
If a level transition was received by trackside and if the acknowledgement is defined for this level transition  (see table below), the driver
shall be requested to acknowledge the transition
- when the max safe front end of the train passes a trackside defined location in rear of the level transition border
OR
- upon receipt of the order to switch to the new level immediately.
UNISIG clarification: is only relevant for an order from trackside. A manual level transition is'nt acknowledged.
TEST APPROACH:
The following aspects have been identified:
1 ) NTC->NTC
1.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
1.2) receipt of the order to switch to the new level immediately
2 ) NTC->L0
2.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
2.2) receipt of the order to switch to the new level immediately
3 ) NTC->L1
3.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
3.2) receipt of the order to switch to the new level immediately
4 ) NTC->L2
4.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
4.2) receipt of the order to switch to the new level immediately
5 ) NTC->L3
5.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
5.2) receipt of the order to switch to the new level immediately
6 ) L0->NTC
6.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
6.2) receipt of the order to switch to the new level immediately
7) L1->NTC
7.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
7.2) receipt of the order to switch to the new level immediately
8) L1->L0
8.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
8.2) receipt of the order to switch to the new level immediately
9) L2->NTC
9.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
9.2) receipt of the order to switch to the new level immediately
10) L2->L0
10.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
10.2) receipt of the order to switch to the new level immediately
11) L3->NTC
11.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
11.2) receipt of the order to switch to the new level immediately
12) L3->L0
12.1) max safe front end of the train passes a trackside defined location in rear of the level transition border
12.2) receipt of the order to switch to the new level immediately
#TEST-VAL-SUB026-3B71#REF# FCT 1.1, 3.2, 4.2, 7.2, 9.1 Acknowledgement of level transition
#TEST-VAL-SUB026-4454#REF# FCT 1.2 SN/STM - selection of NID_STM
#TEST-VAL-SUB026-5093#REF# FCT 2.1, 9.2 Acknowledgement of level transition
#TEST-VAL-SUB026-3B70#REF# FCT 2.2, 6.2, 8.1 Acknowledgement of level transition
#TEST-VAL-SUB026-5094#REF# FCT 3.1 Acknowledgment request at level transition NTC to L1
#TEST-VAL-SUB026-5116#REF# FCT 4.1, 7.1 Quittierungsaufforderung bei level transtion von LSTM nach L2
#TEST-VAL-SUB026-5130#REF# FCT 5.1 Quittierungsaufforderung bei level transtion von LSTM nach L3
#TEST-VAL-SUB026-3B73#REF# FCT 5.2, 11.1, 11.2, 12.1, 12.2 Acknowledgement of level transition
#TEST-VAL-SUB026-5089#REF# FCT 6.1 Acknowledgment request at level transition L0 to NTC
#TEST-VAL-SUB026-5510#REF# FCT 8.2 Acknowledgement with L1->L0 and no acknowledgement with L0->L2, L2->L1 and L1->L2.
#TEST-VAL-SUB026-5712#REF# FCT 10.1 Session termination in L0
#TEST-VAL-SUB026-3616#REF# FCT 10.2 level transition L2->L0 RBC does not order termination of connection

#REQ-UNISIG-SUB026-0838#REF# 5.10.4.1.1
Exception: An ERTMS/ETCS on-board equipment in NL mode shall not require an acknowledgement from the driver.
realised by: #REQ-DESIGN-CR-0101:01#REF#

#REQ-UNISIG-SUB026-0318:01#REF# 5.10.4.2
If the driver has not yet acknowledged within the driver acknowledgement time (refer to Appendix A.3.1) after the level transition, a service
brake command shall be initiated.
#TEST-VAL-SUB026-5097#REF# FCT basic function Driver ignores the acknowledgement of level transition

#REQ-UNISIG-SUB026-0839#REF# 5.10.4.3
The driver shall then acknowledge the level transition in order to release the service brake command.
#TEST-VAL-SUB026-5097#REF# FCT basic function Driver ignores the acknowledgement of level transition

#REQ-UNISIG-SUB026-0840#REF# 5.10.4.4
For the following transitions marked as “YES”, the level transition announcement shall define the location from where an acknowledgement is
required:

TEST APPROACH:
The following aspects have been identified:
1 ) NTC->NTC
2 ) NTC->L0
3 ) NTC->L1
4 ) NTC->L2
5 ) NTC->L3
6 ) L0->NTC
7 ) L0->L1
8 ) L0->L2
9 ) L0->L3
10 ) L1->NTC
11) L1->L0
12) L1->L2
13) L1->L3
14) L2->NTC
15) L2->L0
16) L2->L1
17) L2->L3
18) L3->NTC
19) L3->L0
20) L3->L1
21) L3->L2
#TEST-VAL-SUB026-4454#REF# FCT 1 SN/STM - selection of NID_STM
#TEST-VAL-SUB026-5093#REF# FCT 2, 14 Acknowledgement of level transition
#TEST-VAL-SUB026-5094#REF# FCT 3 Acknowledgment request at level transition NTC to L1
#TEST-VAL-SUB026-5116#REF# FCT 4, 10 Quittierungsaufforderung bei level transtion von LSTM nach L2
#TEST-VAL-SUB026-5130#REF# FCT 5 Quittierungsaufforderung bei level transtion von LSTM nach L3
#TEST-VAL-SUB026-5089#REF# FCT 6 Acknowledgment request at level transition L0 to NTC
#TEST-VAL-SUB026-5088#REF# FCT 7 Keine Quittierungsaufforderung bei level transition von L0 nach L1
#TEST-VAL-SUB026-5510#REF# FCT 8, 11, 12, 16 Acknowledgement with L1->L0 and no acknowledgement with L0->L2, L2->L1 and L1->L2.
#TEST-VAL-SUB026-3B73#REF# FCT 9, 18, 19 Acknowledgement of level transition
#TEST-VAL-SUB026-7714#REF# FCT 13, 20, 21 Level transition announcement to and from L3
#TEST-VAL-SUB026-3616#REF# FCT 15 level transition L2->L0 RBC does not order termination of connection
#TEST-VAL-SUB026-3B72#REF# FCT 17 Acknowledgement of level transition not needed from L0,L1,L2,L3 to L1,L2,L3

Chapter 5.11

#REQ-UNISIG-SUB026-0842:01#REF# 5.11.2.2




.

--- FINALISED ---
Procedure Train Trip - S10, A025:
From which modes a change to mode train trip is possible and the reason for these changes are defined in the mode transition table (see chapter
4.6).

------
Procedure Train Trip - A035:
The handling of stored information when entering to mode Train Trip and the accepatance of new information in mode trip are defined in the
tables 4.8.4 and 4.10.
realised by: #REQ-DESIGN-CR-0173:01#REF#
realised by: #REQ-DESIGN-CR-0175#REF#
realised by: #REQ-DESIGN-CR-0176:01#REF#
realised by: #REQ-UNISIG-SUB026-010135#REF#
realised by: #REQ-UNISIG-SUB026-010136#REF#
realised by: #REQ-DESIGN-CR-0132:02#REF#
realised by: #REQ-DESIGN-CR-0179:01#REF#
realised by: #REQ-DESIGN-CR-0181:01#REF#
realised by: #REQ-UNISIG-SUB026-3693:01#REF#
realised by: #REQ-DESIGN-CR-0133#REF#
realised by: #REQ-DESIGN-CR-0160:01#REF#
realised by: #REQ-DESIGN-CR-0135:02#REF#
realised by: #REQ-DESIGN-CR-0136:01#REF#
realised by: #REQ-DESIGN-CR-0137:02#REF#

#REQ-DESIGN-CR-0173:01#REF# 5.11.2.A030 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - A030:
The on-board equipment reports the mode change to Train Trip to the RBC.
When a PR is sended by a mode change is defined in 3.6.5.1.4 b) and 4.5.2 line "report train position when modes changes to ..."

Clarification: 
The restriction to Level 2/3 is disagreed with 3.6.5.1.4
realised by: #REQ-UNISIG-SUB026-1020:01#REF#

#REQ-DESIGN-CR-0175#REF# 5.11.2.S050 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - S050:
The ERTMS/ETCS on-board equipment awaits standstill. While braking a border to a level 0 or NTC area may be passed.
The triggering of emergency brake is defined in 4.4.13.1.2
TEST APPROACH:
The following aspects have been identified:
1) While braking a border to a level 0 or NTC area may be passed
1.1) NTC
1.2) L0
2) transition border announced but border BG not found
3) no level transition (normal operation)
#TEST-VAL-SUB026-4H31#REF# FCT 1.1 mode/level transition SH/L1->TR/L1->TR/STM->SH/STM
#TEST-VAL-SUB026-4124#REF# FCT 1.2 Mode transition SR->TR[54] TR->UN[62]
#TEST-VAL-SUB026-5112#REF# FCT 2 Kanten der TR-Prozedur testen. Zustand A150.
#TEST-VAL-SUB026-5109#REF# FCT 3 TR-Procedure L2 without Emergency Message

#REQ-DESIGN-CR-0176:01#REF# 5.11.2.S060 #REQ-UNISIG-SUB026-0206#REF#
#REQ-UNISIG-SUB026-0842:01#REF#
#REQ-UNISIG-SUB026-3302#REF#
Procedure Train Trip - S060:
If the train has come to standstill, the on-board equipment shall display the "Request for driver acknowledgement to Train Trip" to
the driver.
#TEST-VAL-SUB026-5109#REF# FCT basic function TR-Procedure L2 without Emergency Message

#REQ-UNISIG-SUB026-010135#REF# 5.11.2.A140 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - A140:
If
- the driver has acknowledged the Train Trip
AND
- the ERTMS/ETCS on-board equipment is in level 0 or NTC
AND
- no valid train data are stored on board

the mode shall change to SH.
is conformed to mode transition TR->SH with condition[68]
realised by: #REQ-UNISIG-SUB026-007068#REF#

#REQ-UNISIG-SUB026-010136#REF# 5.11.2.A145 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - A145:
If
- the driver has acknowledged the Train Trip
AND
- the ERTMS/ETCS on-board equipment is in level 0
AND
- valid train data are stored on board

the mode shall change to UN and the process shall END.
is conformed to mode transition TR->UN with condition[62]
realised by: #REQ-UNISIG-SUB026-2250:01#REF#

#REQ-DESIGN-CR-0132:02#REF# 5.11.2.A150 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - A150:
If
- the driver has acknowledged the Train Trip
AND
- the ERTMS/ETCS on-board equipment is in level NTC
AND
- valid train data are stored on board

the mode shall change to SN and the process shall END.
is conformed to mode transition TR->SN with condition[63]
realised by: #REQ-UNISIG-SUB026-2259#REF#

#REQ-DESIGN-CR-0179:01#REF# 5.11.2.A105 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - A105:
If the driver has acknowledged the Train Trip and the ERTMS/ETCS on-board equipment is in level 1,2 or 3, the ERTMS/ETCS on-board equipment
revokes the emergency brake command and the mode shall change to PT.
the part of revoke the EB is defined in 3.14.1.3.
The mode cange to PT is defined in the mode transition TR->PT
realised by: #REQ-UNISIG-SUB026-0087#REF#
realised by: #REQ-UNISIG-SUB026-2252#REF#

#REQ-DESIGN-CR-0181:01#REF# 5.11.2.A115 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - A115:
If the mode change to POST TRIP and the ERTMS/ETCS on-board equipment is in level 2/3, the new mode shall be reported to the RBC.
When a PR is sended by a mode change is defined in 3.6.5.1.4 b) and 4.5.2 line "report train position when modes changes to ..."

Clarification: 
The restriction to Level 2/3 does not agree with 3.6.5.1.4
realised by: #REQ-UNISIG-SUB026-1020:01#REF#

#REQ-UNISIG-SUB026-3693:01#REF# 5.11.2.S120 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - S120:
The on board unit shall wait for the acknowledgement mode Post Trip from the RBC, if
- the level is 2 or 3
AND
- a position report with Level 2/3 and mode POST TRIP is reported to the RBC

remark:
The case, that the obu changes to level 2/3 in mode PT have to be taken into account also.
Message 6 is meant

for degraded situations see 5.11.4

UNISIG clarification:
obu have to be waited also, if the level is changed from L1 to L2 in mode PT
TEST APPROACH:
The following aspects have been identified:
1) Position report send when entering PT
2) Position report send when entering L2/3
3) Position report send when establishing communication session
#TEST-VAL-SUB026-5109#REF# FCT 1 TR-Procedure L2 without Emergency Message
#TEST-VAL-SUB026-5725#REF# FCT 2 Accepted information depending on mode exception [1] valid for RBC messages in PT/L1
#TEST-VAL-SUB026-4H77#REF# FCT 3 Transition to PT/L2 while connection not yet established

#REQ-DESIGN-CR-0133#REF# 5.11.2.S130 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - S130:
If the RBC recognized the exit from Train Trip and at least one emergency stop is pending, the ERTMS/ETCS on-board equipment shall wait until
the RBC revokes all pending emergency stops.
realised by: #REQ-DESIGN-CR-0160:01#REF#

#REQ-DESIGN-CR-0160:01#REF# 5.11.2.S140 #REQ-UNISIG-SUB026-0842:01#REF#
#REQ-DESIGN-CR-0133#REF#
Procedure Train Trip - S140:
The ERTMS/ETCS on-board equipment shall offer the possibility to the driver to select "start" (only if train data has been previously
entered), or to select SH, when
- in level 1 the mode is changed to Post Trip
OR
- in level 2/3 the RBC has recognized the exit from Train Trip AND all emergency stops are revoked.
TEST APPROACH:
The following aspects have been identified:
1) Level 1
1.1) selection of START
1.1.1) dependency on Train Data
1.2) selection of SH
2) Level 2/3
2.1) selection of START
2.1.1) dependency on pending Emergency Stop
2.1.2) dependency on pending Recognition of Exit from Trip
2.1.3) dependency on Train Data
2.2) selection of SH
2.2.1) dependency on pending Emergency Stop
2.2.2) dependency on pending Recognition of Exit from Trip
#TEST-VAL-SUB026-4505#REF# FCT 1.1.1 PT/L1 -> SR/L1 via START acknowledgment of SR
#TEST-VAL-SUB026-4042#REF# FCT 1.2 Transition from PT/L1 to SH/L1
#TEST-VAL-SUB026-5803#REF# FCT 2.1.1 TRIP procedure with several pending emergency stop
#TEST-VAL-SUB026-5109#REF# FCT 2.1.2, 2.2.2 TR-Procedure L2 without Emergency Message
#TEST-VAL-SUB026-7054#REF# FCT 2.1.3 PT/L2 no train data available, START SH
#TEST-VAL-SUB026-4A56#REF# FCT 2.2.1 Driver choices in PT before/after Revocation of an Emergency Stop Message
#TEST-VAL-SUB026-4201#REF# EET error expectation Auswahlmöglichkeiten am DMI im Mode Post TRIP(zuvor keine Verbindung)

#REQ-DESIGN-CR-0312:01#REF# 5.11.2.E145
Procedure Train Trip - E145:
If the mode is Post Trip and the driver selects SH (E145), the process shall continue in the same ways as the procedure “Shunting initiated by
the driver”. If the SH request is refused by the RBC (E165) the process shall return to S140. Otherwise the process shall END.
could be realized with Shunting dialogue in ERA SRS DMI. If Shunting is refused the dialogue is go back to the Default Window.
TEST APPROACH:
The following aspects have been identified:
1) transition to SH
1.1) L1
1.2) L2/3
2) SH request is refused by RBC
#TEST-VAL-SUB026-4042#REF# FCT 1.1 Transition from PT/L1 to SH/L1
#TEST-VAL-SUB026-5003#REF# FCT 1.2 PT->SH[6]
#TEST-VAL-SUB026-5012#REF# FCT 2 Shunting initiated by driver (L2, PT) rejected by RBC

#REQ-DESIGN-CR-0135:02#REF# 5.11.2.S150 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - E155, S150:
- If the ERTMS/ETCS on-board equipment is in Level 2/3, mode PT
AND
- the driver has selected "Start"

The ERTMS/ETCS on-board equipment shall send an MA request to the RBC and wait.
a) If an SR authorisation is received from RBC (E26), the process shall go to S160
b) If an MA allowing OS/LS/SH is received from RBC (E175), the process shall go to S170
c) If an MA allowing FS is received from RBC (E170), the mode shall change to FS (refer to SRS chapter 4, transitions between modes: transition
from PT to FS) and the process shall END.
clarification:
The mode change to FS is defined in mode transition condition [31]
TEST APPROACH:
The following aspects have been identified:
1) SR authorisation is received from RBC (E26), the process shall go to S160
2) MA allowing OS/LS/SH is received from RBC (E175), the process shall go to S170
2.1) OS
2.2) LS
2.3) SH
3)  MA allowing FS is received from RBC (E170), the mode shall change to FS
#TEST-VAL-SUB026-5109#REF# FCT 1 TR-Procedure L2 without Emergency Message
#TEST-VAL-SUB026-4654#REF# FCT 2.1 PT->OS[15]
#TEST-VAL-SUB026-4558#REF# FCT 2.2 linking information when entering LS, L2 LS->SB[28]->LS[70]->TR[66] ->PT->LS[70]
#TEST-VAL-SUB026-4938#REF# FCT 2.3 Mode transition SR->TR[54], SH->TR[49], PT->SH[50], PT->SR[37], PT->OS[15]
#TEST-VAL-SUB026-3159#REF# FCT 3 Transition to TR at EOA/LOA

#REQ-DESIGN-CR-0136:01#REF# 5.11.2.S160 #REQ-UNISIG-SUB026-0842:01#REF#
#REQ-UNISIG-SUB026-3588:01#REF#
#REQ-UNISIG-SUB026-010418#REF#
Procedure Train Trip - E150, E26, S160:
If
- the ERTMS/ETCS on-board equipment is in Level 1, mode PT AND the driver has selected "Start"
OR
- the ERTMS/ETCS on-board equipment is in Level 2/3, mode PT AND a SR authorisation is received from RBC

The ERTMS/ETCS on-board equipment shall request an acknowledgement from the driver for running in SR mode. When the driver acknowledges (E180),
the mode shall change to SR (refer to SRS chapter 4, transitions between modes: transition from PT to SR) and the process shall END.
TEST APPROACH:
The following aspects have been identified:
1) current level L1
2) current level L2/3
#TEST-VAL-SUB026-4041#REF# FCT 1 From PT to Start, L1
#TEST-VAL-SUB026-5109#REF# FCT 2 TR-Procedure L2 without Emergency Message

#REQ-DESIGN-CR-0137:02#REF# 5.11.3.S170 #REQ-UNISIG-SUB026-0842:01#REF#
Procedure Train Trip - S170:
If
- the ERTMS/ETCS on-board equipment is in Level 2/3, mode PT
AND
- a MA allowing OS/LS/SH is received from RBC

the ERTMS/ETCS on-board equipment shall request an acknowledgement from the driver for running in OS/LS/SH mode. When the driver acknowledges
(E185), the mode shall change to OS/LS/SH (refer to SRS chapter 4, transitions between modes: transition from PT to OS/LS/SH) and the process
shall END.
realizes through SH-/OS-/LS-Procedure (see 5.7.4.1, 5.9.5.1, 5.19.5.1)
realised by: #REQ-DESIGN-CR-0061#REF#
realised by: #REQ-DESIGN-CR-0054#REF#
realised by: #REQ-UNISIG-SUB026-3529#REF#

#REQ-UNISIG-SUB026-006376#REF# 5.11.4.1.1
In case a communication session is established and no reply is received from the RBC within a fixed waiting time (see appendix to chapter 3,
List of Fixed Value Data) after reporting the mode change, the report shall be repeated with the fixed waiting time after each repetition.
realised by: #REQ-UNISIG-SUB026-0844:01#REF#

#REQ-UNISIG-SUB026-0844:01#REF# 5.11.4.1.1 #REQ-UNISIG-SUB026-006376#REF#
#REQ-UNISIG-SUB026-006378#REF#
#REQ-DESIGN-CR-0093:01#REF#
The Post Trip position report shall be repeated with a defined waiting time (see fixed value) after each repetition, in case
- a communication session is open
AND
- no reply is received from the RBC
AND
- the train is in level 2 or 3
AND
- the mode is furthermore Post Trip

If no reply is received from the RBC after a defined number of repetitions (see fixed value), obu shall terminate the session.
clarification: with leaving level2/3 or mode PT this part of the procedure "Train Trip" is finished
TEST APPROACH:
The following aspects have been identified:
1) no response from RBC (repeated with a defined waiting time)
2) level dependency
3) mode dependency
4) defined number of repetitions excided
#TEST-VAL-SUB026-5099#REF# FCT 1 RBC sends M6 after repeated M136(PT)
#TEST-VAL-SUB026-7030#REF# FCT 2, 3 PT position report repetition in case of mode/level change
#TEST-VAL-SUB026-3473#REF# FCT 4 OBU reports transition to PT - no response from RBC

#REQ-UNISIG-SUB026-006378#REF# 5.11.4.1.2
After a defined number of repetitions(see appendix to chapter 3, List of Fixed Value Data) and if no reply is received within the fixed waiting
time from the last sending of the mode change report, the ERTMS/ETCS onboard equipment shall terminate the communication session.
realised by: #REQ-UNISIG-SUB026-0844:01#REF#

#REQ-DESIGN-CR-0138#REF# 5.11.4.2
Nominally, accidental loss of an already open session (that can occur at any step) has not been taken into account for the design of the
flowchart. However, should such a fault occur in any step while ERTMS/ETCS on-board equipment is in level 2/3 and in PT mode, the driver shall
have the possibility to select "Override" and the process shall go to the procedure "Override"
realised by: #REQ-DESIGN-CR-0559#REF#

#REQ-DESIGN-CR-0559#REF# 5.11.4.2 #REQ-DESIGN-CR-0138#REF#
If valid train data are available and the general conditions for selecting "Override" are fulfilled (see section 5), in PT mode the
driver shall always have the possibility to select "Override" and the process shall than go to the procedure "Override"
(i.e. not only in case of the accidental loss of an already open session).
UNISIG clarification:
override is only with valid train data possible

the conditions for selecting override are defined in ERA SRS DMI - 11.2.2.4

The restriction  L2/3 is not defined there.
TEST APPROACH:
The following aspects have been identified:
1) train data available
1.1) S120
1.2) S130
1.3) S140
1.4) S150
2) train data not available

Note: The driver has to acknowledge the proposed mode in S160 and S170 override can hence not be selected.
#TEST-VAL-SUB026-5805#REF# FCT 1.1, 1.2 PT(S120)->SR, PT(S130)->SR
#TEST-VAL-SUB026-4116#REF# FCT 1.3 Override in PT
#TEST-VAL-SUB026-5806#REF# FCT 1.4 PT(S150) override
#TEST-VAL-SUB026-5592#REF# FCT 2 OBU can't send a PR after mode change SH->TR
#TEST-VAL-SUB026-5133#REF# EET CFX00033400 Verlust der Funkverbindung während Prozedur Train Trip
#TEST-VAL-SUB026-4201#REF# EET CFX00035791 Auswahlmöglichkeiten am DMI im Mode Post TRIP(zuvor keine Verbindung)
#TEST-VAL-SyAnfSpezCR-0013#REF# EET error expectation Override activation in PT S150

Chapter 5.12

#REQ-UNISIG-SUB026-006400#REF# 5.12.2.3
When the driver closes the desk A, the ERTMS/ETCS on-board equipment shall immediately go to Stand-By mode, which is considered as an end of
mission (see “End of Mission” procedure)
realised by: #REQ-UNISIG-SUB026-2230#REF#
realised by: #REQ-DESIGN-CR-0072:01#REF#

#REQ-UNISIG-SUB026-0321#REF# 5.12.2.5 #REQ-UNISIG-SUB026-006451#REF#
When the driver closes a desk and opens the other one of the same engine, the ERTMS/ETCS on-board equipment shall be able to calculate the new
train position data (train front position, train orientation), by use of the previous data.
#TEST-VAL-SUB026-5102#REF# FCT basic function Calculation of train position after desk change

#REQ-UNISIG-SUB026-0862#REF# 5.12.3.3.3
Level 2,3: The ERTMS/ETCS on-board equipment of engine B shall open a communication session (if possible) and report the mode change to the RBC.
realised by: #REQ-UNISIG-SUB026-0158#REF#

#REQ-UNISIG-SUB026-006447#REF# 5.12.4.2.1
Before closing the desk A, the driver enables the function “Continue Shunting on desk closure”. When the driver closes the desk A, the
ERTMS/ETCS on-board equipment shall immediately go to Passive Shunting mode.
realised by: #REQ-UNISIG-SUB026-010227#REF#

#REQ-UNISIG-SUB026-006449#REF# 5.12.4.2.2
When the driver opens the desk B, the ERTMS/ETCS on-board equipment shall immediately switch back to Shunting mode.
realised by: #REQ-UNISIG-SUB026-010226#REF#

#REQ-UNISIG-SUB026-006451#REF# 5.12.4.3
When the driver closes a desk and opens the other one of the same engine, the ERTMS/ETCS on-board equipment shall be able to calculate the new
train position data (train front position, train orientation), by use of the previous data.
realised by: #REQ-UNISIG-SUB026-0321#REF#

Chapter 5.13

#REQ-UNISIG-SUB026-006459#REF# 5.13.1.3
While the train is at standstill inside the reversing permitted area, the driver shall be informed that reversing is possible
is also defined in 3.15.4.7
realised by: #REQ-DESIGN-CR-0325#REF#

#REQ-UNISIG-SUB026-0870#REF# 5.13.1.4 #REQ-UNISIG-SUB026-3281#REF#
If the ERTMS/ETCS onboard detects the driver’s intention to reverse (e.g. from a direction controller in reverse position), the ERTMS/ETCS
on-board equipment shall ask the driver to acknowledge transition to RV mode.
#TEST-VAL-SUB026-3169#REF# FCT basic function Reversing

#REQ-UNISIG-SUB026-0324#REF# 5.13.1.5
If the driver acknowledges, the on-board equipment shall switch to RV mode
realised by: #REQ-UNISIG-SUB026-2291#REF#

Chapter 5.15

#REQ-UNISIG-SUB026-0883#REF# 5.15.1.4
If the message from the border balise group is not (yet) received, the handover shall still be executed when the train with its max safe front
end passes the border location according to the announcement information.
realised by: #REQ-UNISIG-SUB026-0887#REF#
realised by: #REQ-UNISIG-SUB026-0891#REF#

#REQ-DESIGN-CR-0111#REF# 5.15.1.5
The on-board equipment shall manage only one RBC/RBC transition at a time, therefore a new transition order shall replace a previously received
order.
realised by: #REQ-DESIGN-CR-0561:01#REF#
realised by: #REQ-DESIGN-CR-0562:01#REF#
realised by: #REQ-DESIGN-CR-0564:01#REF#
realised by: #REQ-DESIGN-CR-0565:01#REF#

#REQ-DESIGN-CR-0561:01#REF# to.5.15.1.5 #REQ-DESIGN-CR-0111#REF#
#ANA-UNISIG-CR0309-0001:02#REF#
If the on-board equipment performs a RBC/RBC transition order and receives a new RBC/RBC transition order with the same RBC ID (in connection
with Country ID), but with a different distance,
the new distance shall be taken over only, when the current border location is not yet passed with max safe front end.
Otherwise the new distance shall be ignored.
UNISIG clarification: new HO with same RBC ID, but with different distance
TEST APPROACH:
The following aspects have been identified:
1) one mobile RBC/RBC handover
1.1) RBC border passed
1.2) RBC border not passed
1.2.1) D_RBCTR increased 
1.2.2) D_RBCTR decreased
2) two mobile RBC/RBC handover
2.1) RBC border passed
2.2) RBC border not passed
2.2.1) D_RBCTR increased 
2.2.2) D_RBCTR decreased
#TEST-VAL-SUB026-5440#REF# FCT 1.1, 1.2.2 RBC transition updated by new RBC transition order to same RBC (shorter distance, 1 mobile)
#TEST-VAL-SUB026-5441#REF# FCT 1.2.1 RBC transition updated by new RBC transition order to same RBC (increased distance, 1 mobile)
#TEST-VAL-SUB026-5442#REF# FCT 2.1, 2.2.2 RBC transition updated by new RBC transition order to same RBC (decreased distance, 2 mobile)
#TEST-VAL-SUB026-5444#REF# FCT 2.2.1 RBC transition updated by new RBC transition order to same RBC (increased distance, 2 mobile)
#TEST-VAL-SUB026-5439#REF# EET error expectation RBC transition updated by new RBC transition order to same RBC (distance changed several times, 1 mobile)
#TEST-VAL-SUB026-5443#REF# EET error expectation RBC transition updated by new RBC transition order to same RBC (distance changed several times, 2 mobile)

#REQ-UNISIG-SUB026-008016:01#REF# to.5.15.1.5 #ANA-UNISIG-CR0309-0001:02#REF#
Case: Two communication sessions can be handled simultaneously
If the on-board equipment performs a RBC/RBC transition order and receives a new RBC/RBC transition order
- with the same RBC ID (in connection with Country ID)
AND
- with the same RBC telephone number than before
AND
- no session is established or no session establishment is currently executed to the Accepting RBC,
a new attempt for session establishment shall be started.
TEST APPROACH:
The following aspects have been identified:
1) no session is established or no session establishment is currently executed to the ACC-RBC
2) session to ACC-RBC established
3) session establishment is currently executed to the ACC-RBC
#TEST-VAL-SUB026-8202#REF# FCT 1 OBU performs a two mobile RBC/RBC transition and receives a new RBC/RBC transition order with same data, no connection to ACC-RBC
#TEST-VAL-SUB026-8203#REF# FCT 2 OBU performs a two mobile RBC/RBC transition and receives a new RBC/RBC transition order with same data, connection to ACC-RBC established
#TEST-VAL-SUB026-8204#REF# FCT 3 OBU performs a two mobile RBC/RBC transition and receives a new RBC/RBC transition order with same data, connection to ACC-RBC establishing

#REQ-DESIGN-CR-0562:01#REF# to.5.15.1.5 #REQ-DESIGN-CR-0111#REF#
#ANA-UNISIG-CR0309-0001:02#REF#
If the on-board equipment performs a RBC/RBC transition order and receives a new RBC/RBC transition order
- with the same RBC ID (in connection with Country ID)
but
- with a different RBC telephone number
AND
- the establishment of the communication session (incl. setting up the safe connection) has not been started,
the on-board equipment shall replace the RBC telephone number.
Otherwise the new RBC telephone number shall be ignored.
UNISIG clarification: new HO with same RBC ID, but with a different telephone number
TEST APPROACH:
The following aspects have been identified:
1) establishment of the communication session has not been started
1.1) one mobile RBC/RBC handover
1.2) two mobile RBC/RBC handover
2) establishment of the communication session has been started
#TEST-VAL-SUB026-8205#REF# FCT 1.1 Reception of new RBC transition order with different RBC telephone, establishment of the communication session has not been started
#TEST-VAL-SUB026-5448#REF# FCT 1.2 , CFX00040154 Reception of new RBC transition order with different RBC telephone number network registration not finshed yet
#TEST-VAL-SUB026-8206#REF# FCT 2 Reception of new RBC transition order with different RBC telephone, establishment of the communication session ongoing

#REQ-DESIGN-CR-0564:01#REF# to.5.15.1.5 #REQ-DESIGN-CR-0111#REF#
#ANA-UNISIG-CR0309-0001:02#REF#
If the on-board equipment performs a RBC/RBC transition order and receives a new RBC/RBC transition order
with a different RBC ID (associated with Country ID),
the ongoing transition shall be aborted and the new transition shall be performed.

remark: The abort of the current RBC/RBC transition order includes the cancellation of the EXIT procedure to the handing over RBC.
UNISIG clarification: new HO with different RBC ID
TEST APPROACH:
The following aspects have been identified:
1) one mobile RBC/RBC handover
1.1) RBC border passed
1.2) RBC border not passed
2) two mobile RBC/RBC handover
2.1) RBC border passed
2.2) RBC border not passed
#TEST-VAL-SUB026-8207#REF# FCT 1.1 Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID (border passed)
#TEST-VAL-SUB026-5438#REF# FCT 1.2 Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID (border not passed)
#TEST-VAL-SUB026-8209#REF# FCT 2.1 , CFX00040152 Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID (border passed)
#TEST-VAL-SUB026-8210#REF# FCT 2.2 Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID (border not passed)
#TEST-VAL-SUB026-4789#REF# EET error expectation RBC transition order within rbc transition buffer
#TEST-VAL-SUB026-8208#REF# EET error expectation Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID from border BG
#TEST-VAL-SUB026-8211#REF# EET error expectation RBC transition order within rbc transition buffer

#REQ-DESIGN-CR-0565:01#REF# to.5.15.1.5 #REQ-DESIGN-CR-0111#REF#
#ANA-UNISIG-CR0309-0001:02#REF#
If
- the on-board equipment performs a RBC transition order and receives a new RBC transition order with a RBC ID (associated with a Country ID)
which is the same as the RBC ID (associated with Country ID) of the "Handing Over" RBC
AND
- the supervision is not already changed to the "Accepting RBC",
the ongoing transition shall be aborted only.

remark: When the supervision has already changed to the "Accepting RBC" REQ-DESIGN-CR-0564 is applied.
UNISIG clarification: new HO with  RBC ID = HO RBC
TEST APPROACH:
The following aspects have been identified:
1) one mobile RBC/RBC handover (Note: a one mobile RBC/RBC handover ends with the train supervision change)
1.1) RBC border passed 
1.2) RBC border not passed
2) two mobile RBC/RBC handover
2.1) after transfer of train supervision to the ACC-RBC
2.2) before transfer of train supervision to the ACC-RBC
#TEST-VAL-SUB026-8212#REF# FCT 1.1 Abortion of RBC transition order due to reception of new RBC transition order to HO-RBC (border passed)
#TEST-VAL-SUB026-8214#REF# FCT 1.2 Abortion of RBC transition order due to reception of new RBC transition order to HO-RBC (border not passed)
#TEST-VAL-SUB026-8215#REF# FCT 2.1 Abortion of RBC transition order due to reception of new RBC transition order to HO-RBC (border passed)
#TEST-VAL-SUB026-8216#REF# FCT 2.2 Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID (border not passed)
#TEST-VAL-SUB026-8213#REF# EET error expectation Handling of stored RBC data in case of abortion of RBC transition order due to reception of new RBC transition order to HO-RBC
#TEST-VAL-SUB026-8229#REF# EET error expectation RTO buffer deleted due to aborion of RBC transition

#REQ-UNISIG-SUB026-006528#REF# to.5.15.1.5 #ANA-UNISIG-RBCHandover-0016#REF#
If the on-board equipment performs a RBC/RBC transition order and receives a new RBC/RBC transition order
- with the same RBC ID (in connection with Country ID)
but
- with Q_SLEEPSESSION=0
this shall neither lead to the abortion of an already started communication session establishment to the ACC-RBC nor to the termination of an
already established communication session.
TEST APPROACH:
The parameter Q_SLEEPSESSION is evaluated in the mode SL only the verification focuses hence on the mode SL.
Following aspects have been identified:
1) Q_SLEEPSESSION changes from 1 to 0
1.1) communication session being established
1.2) communication session established
2) Q_SLEEPSESSION changes from 0 to 1
#TEST-VAL-SUB026-8289#REF# FCT 1.1, 1.2, 2 Evaluation of new RBC/RBC transition order with changed Q_SLEEPSESSION during HO to same RBC in SL
#TEST-VAL-SUB026-8290#REF# EET error expectation Evaluation of new RBC/RBC transition order with changed Q_SLEEPSESSION during HO to same RBC in FS

#REQ-UNISIG-SUB026-0886#REF# 5.15.2.2.2.1 #REQ-UNISIG-SUB026-3348#REF#
#REQ-UNISIG-SUB026-003555#REF#
A radio communication session with the Accepting RBC is opened by the on-board equipment based on the RBC transition order received from the
“Handing Over” RBC or from balise group (refer to chapter 3, section "management of radio communication").
scenario: Two communication sessions can be handled simultaneously
TEST APPROACH:
The following aspects have been identified:
1) from BG
2) from RBC
3) RBC/RBC handover includes radio network change
4) border not passed
5) border already passed
#TEST-VAL-SUB026-4A78#REF# FCT 1 Manage RBC Handover; SR
#TEST-VAL-SUB026-4A74#REF# FCT 2, 4 Manage RBC Handover; OS
#TEST-VAL-SUB026-3989#REF# FCT 3 RadioNetworkId in RBC-RBC handover (2 mobiles)
#TEST-VAL-SUB026-4017#REF# FCT 5 Received immediately RBC Transition Order, RBC-ID and RBC-Phonenumber of the accepting RBC memorized at once

#REQ-UNISIG-SUB026-006553#REF# to.5.15.2.2.2.1 #ANA-UNISIG-SessionEstablishment-0008#REF#
Two communication sessions can be handled simultaneously:
If a RBC transition order is received
AND
the second mobile is occupied with a session to another not supervised RBC,
this existing communication session shall be terminated and then the session to the Accepting RBC shall be established.
TEST APPROACH:
The following aspects have been identified:
1) second mobile is occupied with a session to another not supervised RBC
2) second mobile is occupied with a session to the ACC-RBC
#TEST-VAL-SUB026-8209#REF# FCT 1 Abortion of RBC transition order due to reception of new RBC transition order with different RBC ID (border passed)
#TEST-VAL-SUB026-8215#REF# FCT 2 Abortion of RBC transition order due to reception of new RBC transition order to HO-RBC (border passed)

#REQ-UNISIG-SUB026-0887#REF# 5.15.2.2.4.1 #REQ-UNISIG-SUB026-3348#REF#
#REQ-UNISIG-SUB026-0883#REF#
#REQ-UNISIG-SUB026-3076#REF#
When the train reaches the border with its max safe front end, the ERTMS/ETCS on-board equipment sends a position report both to the “Handing
Over” RBC and to the “Accepting” RBC.
scenario: Two communication sessions can be handled simultaneously
#TEST-VAL-SUB026-4A74#REF# FCT basic function Manage RBC Handover; OS
#TEST-VAL-SUB026-3352#REF# EET error expectation Evaluation of HO border - movement in the direction opposite to the train orientation
#TEST-VAL-SUB026-5485#REF# EET error expectation RBC transition position reports - max safe front and min safe rear end jump over RBC transition border
#TEST-VAL-SUB026-5486#REF# EET error expectation RBC transition position reports - max safe front and min safe rear end pass RBC transition border twice

#REQ-UNISIG-SUB026-0888#REF# 5.15.2.2.5.1
As soon as the on-board has sent to the “Accepting” RBC the position report, it considers to be supervised by the “Accepting” RBC i.e. it uses
information received from the “Accepting” RBC.
realised by: #REQ-UNISIG-SUB026-3570:02#REF#

#REQ-UNISIG-SUB026-0889#REF# 5.15.2.2.6.1 #REQ-UNISIG-SUB026-3348#REF#
#REQ-UNISIG-SUB026-0892#REF#
#REQ-UNISIG-SUB026-3074#REF#
When the min safe rear end of the train passes the location of the border, the ERTMS/ETCS on-board equipment sends a position report to the
“Handing Over” RBC.
TEST APPROACH:
The following aspects were identified:
1) only one communication session can be handled 
2) two communication session can be handled simultaneously
#TEST-VAL-SUB026-3984#REF# FCT 1 RadioNetworkId in RBC-RBC handover (1 mobile)
#TEST-VAL-SUB026-3989#REF# FCT 2 RadioNetworkId in RBC-RBC handover (2 mobiles)
#TEST-VAL-SUB026-5452#REF# EET error expectation Two mobile RBC/RBC transition - HO-RBC terminates session in front of transition location
#TEST-VAL-SUB026-5485#REF# EET error expectation RBC transition position reports - max safe front and min safe rear end jump over RBC transition border
#TEST-VAL-SUB026-5486#REF# EET error expectation RBC transition position reports - max safe front and min safe rear end pass RBC transition border twice

#REQ-UNISIG-SUB026-0891#REF# 5.15.3.2.3.1 #REQ-UNISIG-SUB026-3348#REF#
#REQ-UNISIG-SUB026-0883#REF#
#REQ-UNISIG-SUB026-3076#REF#
When the train with its max safe front end reaches the border, the ERTMS/ETCS on-board equipment sends a position report to the “Handing Over”
RBC.
scenario: only one communication session can be handled
#TEST-VAL-SUB026-5104#REF# FCT basic function One mobile RBC/RBC handover without border BG

#REQ-UNISIG-SUB026-0892#REF# 5.15.3.2.4.1 #REQ-UNISIG-SUB026-3348#REF#
#REQ-UNISIG-SUB026-3074#REF#
As requested by the RBC transition order, when the min safe rear end of the train passes the location of the border, the on-board equipment
sends a position report to the “Handing Over” RBC.
Justification:
Sending of this PR is independent from using one or two mobiles. (realized by 5.15.2.2.6.1)
realised by: #REQ-UNISIG-SUB026-0889#REF#

#REQ-UNISIG-SUB026-0894#REF# 5.15.3.2.5.1 #REQ-UNISIG-SUB026-3348#REF#
#REQ-UNISIG-SUB026-003555#REF#
When the ERTMS/ETCS on-board equipment receives the session termination order from the “Handing Over” RBC, it terminates the session with the
“Handing over” RBC and opens a session with the “Accepting” RBC (refer to chapter 3, management of radio communication).
scenario: only one communication session can be handled
TEST APPROACH:
The following aspects have been identified:
1) session termination order from HO-RBC before passing border with min safe rear end
2) session termination order from HO-RBC after passing border with min safe rear end
#TEST-VAL-SUB026-7181#REF# FCT 1 One mobile RBC/RBC handover HO-RBC orders session termination infront of RBC border
#TEST-VAL-SUB026-4849#REF# FCT 2 One mobile RBC transition, T_NVCONTACT before and after supervision change

#REQ-UNISIG-SUB026-0895#REF# 5.15.3.2.6.1
When the ERTMS/ETCS on-board equipment has established a communication session with the “Accepting” RBC and sent to the “Accepting” RBC a
position report, it considers to be supervised by the “Accepting” RBC, i.e. it accepts only information received from the “Accepting” RBC.
realised by: #REQ-UNISIG-SUB026-3570:02#REF#

#REQ-UNISIG-SUB026-010373#REF# 5.15.4.3
If the ERTMS/ETCS on-board equipment is not able to terminate the session with the “Handing Over” RBC: In case a communication session is
established and no request to terminate the session is received from the “Handing Over” RBC within a fixed waiting time (see appendix to chapter
3, List of Fixed Value Data) after sending the position report (see 5.15.2.2.6), the position report shall be repeated with the fixed waiting
time after each repetition.
realised by: #REQ-UNISIG-SUB026-0980:01#REF#

#REQ-UNISIG-SUB026-0980:01#REF# 5.15.4.3 #REQ-UNISIG-SUB026-006650#REF#
#REQ-DESIGN-CR-0093:01#REF#
#REQ-UNISIG-SUB026-010373#REF#
The position report "exited from an Handing Over RBC area" shall be repeated with a defined waiting time (see fixed value) after each
repetition, in case
- a communication session to the Handing Over RBC is still open
AND
- no request to terminate the session to the Handing Over RBC is received from trackside.

If no request to terminate the session to the Handing Over RBC is received from trackside after a defined number of repetitions (see fixed
value), obu shall terminate the session.
TEST APPROACH:
The following aspects have been identified:
1) one mobile RBC/RBC handover
2) two mobile RBC/RBC handover
#TEST-VAL-SUB026-5107#REF# FCT 1 HO-RBC does not order session termination
#TEST-VAL-SUB026-4A74#REF# FCT 2 Manage RBC Handover; OS
#TEST-VAL-SUB026-5454#REF# EET error expectation One mobile RBC transition degraded situation, HO-RBC does not order termination of communication session and T_NVCONTACT expiry

#REQ-UNISIG-SUB026-006650#REF# 5.15.4.4
After a defined number of repetitions (see appendix to chapter 3, List of Fixed Value Data), and if no reply is received within the fixed
waiting time from the last sending of the position report, the ERTMS/ETCS onboard equipment shall terminate the communication session.
realised by: #REQ-UNISIG-SUB026-0980:01#REF#

#REQ-UNISIG-SUB026-3570:02#REF# to.5.15 #REQ-UNISIG-SUB026-0888#REF#
#REQ-UNISIG-SUB026-0895#REF#
#ANA-UNISIG-RBCHandover-0001:03#REF#
With the first sent position report to the "Accepting" RBC after the train reaches the handover border with its max safe front end,
obu shall change the supervision to the "Accepting" RBC.
This requirement is valid for both HO with one and 2 mobiles
TEST APPROACH:
The following aspects have been identified:
1) one mobile RBC/RBC handover
1.1) PR send before passing border with min safe rear end
1.2) PR send after passing border with min safe rear end
2) two mobile RBC/RBC handover
2.1) session to ACC-RBC established before passing border with max safe front end
2.1.1) safe connection up
2.1.2) safe connection down
2.2) session establishment to ACC-RBC not finished when passing border with max safe front end
3) RBC/RBC handover in SL
3.1) Q_SLEEPSESSION=0
3.2) Q_SLEEPSESSION=1
3.2.1) one mobile RBC/RBC handover
3.2.2) two mobile RBC/RBC handover
4) fallback from two mobile to one mobile
5) second mobile becomes available during RBC/RBC handover 
#TEST-VAL-SUB026-8218#REF# FCT 1.1 Change of supervision to the ACC-RBC, one mobile RBC transition
#TEST-VAL-SUB026-5104#REF# FCT 1.2 One mobile RBC/RBC handover without border BG
#TEST-VAL-SUB026-8219#REF# FCT 2.1.1 Change of supervision to ACC-RBC, two mobile RBC transition
#TEST-VAL-SUB026-8220#REF# FCT 2.1.2 Change of supervision to ACC-RBC, two mobile RBC transition, safe connection to ACC-RBC down
#TEST-VAL-SUB026-8222#REF# FCT 2.2 Change of supervision to ACC-RBC, two mobile RBC transition, session establishment to ACC-RBC ongoing when passing RBC border
#TEST-VAL-SUB026-8223#REF# FCT 3.1 Change of supervision to ACC-RBC in SL Q_SLEEPSESSION=0
#TEST-VAL-SUB026-8225#REF# FCT 3.2.1 Change of supervision to ACC-RBC in SL Q_SLEEPSESSION=1, one mobiles available
#TEST-VAL-SUB026-8224#REF# FCT 3.2.2 Change of supervision to ACC-RBC in SL Q_SLEEPSESSION=1, two mobiles available
#TEST-VAL-SUB026-8226#REF# FCT 4 RBC transition, fallback from two mobile to one mobile
#TEST-VAL-SUB026-8227#REF# FCT 5 Second mobile becomes available during RBC transition
#TEST-VAL-SUB026-4849#REF# EET CFX00040177 One mobile RBC transition, T_NVCONTACT before and after supervision change
#TEST-VAL-SUB026-8217#REF# EET error expectation Test the test environment
#TEST-VAL-SUB026-8228#REF# EET error expectation T_NVCONTACT supervision based on current OBU time of supervision change to ACC-RBC

#REQ-UNISIG-SUB026-007079:01#REF# to.5.15 #ANA-UNISIG-RBCHandover-0009:02#REF#
A new attempt of session establishment to the Accepting RBC shall be started in case of two communication session can be handled simultaneously,
if
- the handover border is reached with max safe front end
AND
- no communication session to the Accepting RBC is established or in establishing.
TEST APPROACH:
The following aspects have been identified:
1) communication session to ACC-RBC established
2) no communication session to ACC-RBC established or being established
3) establishment of safe connection ongoing
4) safe connection established communication session not established yet
#TEST-VAL-SUB026-7183#REF# FCT 1 Supervision of the disconnect delay time, if another RBC becomes the supervised RBC
#TEST-VAL-SUB026-7191#REF# FCT 2 Order to establish communication session to ACC-RBC during two mobile HO
#TEST-VAL-SUB026-8200#REF# FCT 3 Passing RBC transition border in two mobile HO, safe connection establishment to ACC-RBC ongoing
#TEST-VAL-SUB026-8201#REF# FCT 4 Passing RBC transition border in two mobile HO, session establishment to ACC-RBC ongoing

#REQ-UNISIG-SUB026-008015:01#REF# to.5.15 #ANA-UNISIG-RBCHandover-0009:02#REF#
In case of only one communication session can be handled, the session establishment to the "Accepting" RBC shall be started, when
- the train passed the border with max safe front end
AND
-  the session to "Handing Over" RBC is terminated or doesn't exist.
TEST APPROACH:
The following aspects have been identified:
1) no session to HO-RBC when passing RBC border
1.1) session to HO-RBC never exist
1.2) session terminated from track
1.3) session terminated due to safe connection outage
2) session to HO-RBC terminated after passing RBC border
2.1) session terminated from track
2.2) session terminated due to safe connection outage RBC border with max save front end
#TEST-VAL-SUB026-7197#REF# FCT 1.1 Session establishment to ACC-RBC, no session to HO-RBC
#TEST-VAL-SUB026-7181#REF# FCT 1.2 One mobile RBC/RBC handover HO-RBC orders session termination infront of RBC border
#TEST-VAL-SUB026-7198#REF# FCT 1.3 Session establishment to ACC-RBC, session to HO-RBC terminated
#TEST-VAL-SUB026-3B49#REF# FCT 2.1 Safe Radio Connection indication: RTO(one mobile) lose safe radio connection with ACC-RBC before HO executed
#TEST-VAL-SUB026-7199#REF# FCT 2.2 Session establishment to ACC-RBC, session to HO-RBC terminated after passing the RBC border
#TEST-VAL-SUB026-4849#REF# EET error expectation One mobile RBC transition, T_NVCONTACT before and after supervision change

#REQ-UNISIG-SUB026-007848#REF# to.5.15 #ANA-UNISIG-RBCHandover-0005:02#REF#
If the train is in Mode SLEEPING and runs backward, the PR to entering the ACC RBC area shall be sent, when the train pass the RBC border with
min safe rear end.
The PR to leaving the HO RBC area shall be sent, when the train pass the RBC border with max safe front end.
TEST APPROACH:
The following aspects have been identified:
1) one mobile
2) two mobile
#TEST-VAL-SUB026-5277#REF# FCT 1 Handover position reports in SL (Q_SLEEPSESSION = 1), one mobile
#TEST-VAL-SUB026-5275#REF# FCT 2 Handover position reports in SL (Q_SLEEPSESSION = 1) - two mobiles
#TEST-VAL-SUB026-7583#REF# EET CFX00035641 Evaluation D_RBCTR, D_LEVELTR and D_VALIDNV (from Balise) in SL
#TEST-VAL-SUB026-7584#REF# EET CFX00035641 Evaluation D_RBCTR, D_LEVELTR and D_VALIDNV (from RBC) in SL

#REQ-UNISIG-SUB026-010568#REF# to.5.15 #ANA-UNISIG-RBCHandover-0012#REF#
If the train receives a session establishment command during a handover, the handover procedure shall be aborted.

Exceptions:
- a session establishment command to the Accepting RBC shall be ignored
- a session establishment command to the Handing Over RBC shall be executed independent of the handover procedure and an existing session to the
Accepting RBC, if available, until the handover border is reached with max safe front end.

remark:
A session establishment command to the Handing Over RBC after the handover border is reaced with max safe front end is to be executed according
to 3.5.3.5.2 and the clarifications to 3.5.3.5.2.
UNISIG clarification:
a clarification is necessary
TEST APPROACH:
The following aspects have been identified:
1) order to establish a communication session to HO-RBC
1.1) RBC border passed
1.1.1) one mobile RBC/RBC handover
1.1.2) two mobile RBC/RBC handover
1.2) RBC border not passed
1.2.1) one mobile RBC/RBC handover
1.2.2) two mobile RBC/RBC handover
2) order to establish a communication session to ACC-RBC
2.1) one mobile RBC/RBC handover
2.2) two mobile RBC/RBC handover
3) order to establish a communication session to other RBC
3.1) one mobile RBC/RBC handover
3.2) two mobile RBC/RBC handover
#TEST-VAL-SUB026-7192#REF# FCT 1.1.1, 1.2.1 Order to establish communication session to HO-RBC during one mobile HO
#TEST-VAL-SUB026-7193#REF# FCT 1.1.2, 1.2.2 Order to establish communication session to HO-RBC during two mobile HO
#TEST-VAL-SUB026-7176#REF# FCT 2.1 Order to establish communication session to ACC-RBC during one mobile HO
#TEST-VAL-SUB026-7191#REF# FCT 2.2 Order to establish communication session to ACC-RBC during two mobile HO
#TEST-VAL-SUB026-7194#REF# FCT 3.1 Order to establish communication session to RBC not involved in current RBC/RBC handover - two mobile HO
#TEST-VAL-SUB026-7195#REF# FCT 3.2 Order to establish communication session to RBC not involved in current RBC/RBC handover - two mobile HO
#TEST-VAL-SUB026-7196#REF# EET error expectation Order to establish communication session during one mobile HO, HO-RBC unknown

#REQ-UNISIG-SUB026-010621#REF# to.5.15 #ANA-UNISIG-RBCHandover-0013#REF#
If the train receives and accepts both a session establishment command and a handover command in the same message/telegram, the session
establishment command shall be executed at first.

Exception:
If D_RBCTR=0, the handover command shall be ignored.
UNISIG clarification:
a clarification is necessary
TEST APPROACH:
The following aspects have been identified:
1) D_RBCTR>0
1.1) one mobile RBC/RBC handover
1.2) two mobile RBC/RBC handover
2) D_RBCTR=0
2.1) one mobile RBC/RBC handover
2.2) two mobile RBC/RBC handover
3) session establishment command executed at first
#TEST-VAL-SUB026-7187#REF# FCT 1.1, 2.1 Reception of session establishment order to HO-RBC and RBC transition order in one message - one mobile
#TEST-VAL-SUB026-7188#REF# FCT 1.2, 2.2 Reception of session establishment order to HO-RBC and RBC transition order in one message - two mobile
#TEST-VAL-SUB026-7190#REF# FCT 3 Reception of session establishment order and RBC transition order in one message - one mobile
#TEST-VAL-SUB026-7189#REF# EET error expectation Reception of session establishment order and RBC transition order in one message - two mobiles

#REQ-UNISIG-SUB026-010629#REF# to.5.15 #ANA-UNISIG-RBCHandover-0015#REF#
If the driver selects level 2 or 3 during a handover execution again, the handover procedure shall be aborted.
UNISIG clarification:
a clarification is necessary
#TEST-VAL-SUB026-7180#REF# FCT basic function Session establishment after termination order from driver

Chapter 5.16

#REQ-UNISIG-SUB026-006656#REF# 5.16.1.1
In case the LX is not protected, the ERTMS/ETCS on-board equipment (in FS, LS or OS mode) shall temporarily supervise the LX start location as
both the EOA and SvL (instead of the EOA and SvL given by the MA), with no release speed.
#TEST-VAL-SUB026-5976#REF# FCT FS Speed and distance supervision function in FS
#TEST-VAL-SUB026-5978#REF# FCT LS Speed and distance supervision function in LS
#TEST-VAL-SUB026-5977#REF# FCT OS Speed and distance supervision function in OS
#TEST-VAL-SUB026-7859#REF# EET error expectation LX start location in front of LoA, behind LoA, behind SvL and between EoA and Svl

#REQ-UNISIG-SUB026-006658#REF# 5.16.1.2
The supervision of the LX start location as both the EOA and SvL shall be substituted by the inclusion of the LX speed restriction in the MRSP
under conditions depending on whether stopping in rear of the LX start location is required or not. The conditions of this substitution are
specified in 5.16.2 or 5.16.3.
realised by: #REQ-UNISIG-SUB026-006672#REF#
realised by: #REQ-UNISIG-SUB026-006678#REF#
realised by: #REQ-UNISIG-SUB026-006680#REF#

#REQ-UNISIG-SUB026-006660#REF# 5.16.1.3
The start location of the LX speed restriction depends on the substitution conditions, which are specified in 5.16.2 or 5.16.3. The end location
of the LX speed restriction shall be the LX end location.
realised by: #REQ-UNISIG-SUB026-010590#REF#
realised by: #REQ-UNISIG-SUB026-006672#REF#
realised by: #REQ-UNISIG-SUB026-006680#REF#

#REQ-UNISIG-SUB026-010590#REF# to.5.16.1.3 #REQ-UNISIG-SUB026-006660#REF#
The LX speed restriction shall be supervised until the train has passed the LX end location with its min safe front end.
UNISIG clarification: the end condition min safe front end is derived from 5.16.1.5 b
#TEST-VAL-SUB026-7644#REF# FCT basic function LX information overwritten by new received LX with same ID

#REQ-UNISIG-SUB026-006662#REF# 5.16.1.4 #REQ-UNISIG-SUB026-010417#REF#
When approaching a non protected LX, the on-board equipment shall inform the driver about the status of the LX, as soon as:
a)	either the EOA or the SvL related to the LX start location becomes the Most Restrictive Displayed Target (see 3.13.10.4.2), or
b)	the ERTMS/ETCS on-board equipment substitutes the supervision of the LX start location as both the EOA and SvL by the inclusion of the
LX speed restriction in the MRSP.
#TEST-VAL-SUB026-7646#REF# FCT basic function LX not protected message displayed on the DMI

#REQ-UNISIG-SUB026-006666#REF# 5.16.1.5
Indication given to the driver shall remain displayed until one of the following conditions is met:
a)	information “LX is protected” is received on-board;
b)	train has passed the LX end location with its min safe front end.
#TEST-VAL-SUB026-7645#REF# FCT a LX supervision is stopped when LX becomes protected
#TEST-VAL-SUB026-7644#REF# FCT b LX information overwritten by new received LX with same ID

#REQ-UNISIG-SUB026-006672#REF# 5.16.2.1 #REQ-UNISIG-SUB026-006658#REF#
#REQ-UNISIG-SUB026-006660#REF#
Once the train has stopped with its estimated front end inside the stopping area, given by trackside, the ERTMS/ETCS on-board equipment shall no
longer supervise the LX start location as both the EOA and SvL (i.e. the ones given by the MA shall be again supervised) and shall immediately
include the LX speed restriction in the MRSP, starting from the estimated train front end.
UNISIG clarification:
If the train has stopped beyond the LX start location but no trip is executed due to EoA supervision, the function is continued analog as the
train has stopped inside the stopping area.
#DSC-UNISIG-SUB026-006674#REF#

Figure 10: Approaching a non protected LX with stopping required
#TEST-VAL-SUB026-7644#REF# FCT basic function LX information overwritten by new received LX with same ID

#REQ-UNISIG-SUB026-006678#REF# 5.16.3.1 #REQ-UNISIG-SUB026-006658#REF#
In case stopping in rear of the non protected LX is not required, the LX start location shall be supervised as both the EOA and SvL until the
train reaches the location of the braking to target Permitted speed supervision limit calculated for the LX speed (see 3.13.9.3.5.11&12 for
the calculation of this location).

#DSC-UNISIG-SUB026-006682#REF#

Figure 11: Approaching a non protected LX with stopping not required
TEST APPROACH:
The following aspects were identified:
1) FLOI is SBI1
2) FLOI is SBI2
#TEST-VAL-SUB026-7661#REF# FCT 1, 2 Supervision LX not protected with no stop required when FLOI is SBI2

#REQ-UNISIG-SUB026-006680#REF# 5.16.3.2 #REQ-UNISIG-SUB026-006658#REF#
#REQ-UNISIG-SUB026-006660#REF#
As soon as the estimated or the max safe front end (depending whether the FLOI at LX speed is the SBI1 or the SBI2) reaches the location of the
Permitted speed supervision limit calculated for the LX speed, the ERTMS/ETCS on-board equipment shall no longer supervise the LX start location
as both the EOA and SvL (i.e. the ones given by the MA shall be again supervised) and shall immediately include the LX speed restriction in the
MRSP, starting from the train front end (estimated or max safe), which has reached the concerned Permitted speed supervision limit location.

#DSC-UNISIG-SUB026-006682#REF#

Figure 11: Approaching a non protected LX with stopping not required
TEST APPROACH:
The following aspects were identified:
1) FLOI is SBI1
2) FLOI is SBI2
#TEST-VAL-SUB026-7661#REF# FCT 1, 2 Supervision LX not protected with no stop required when FLOI is SBI2

#REQ-UNISIG-SUB026-006681#REF# to.5.16.3.2
The supervision of the LX start location shall be ended when the following conditions are fulfilled:
-  the location of the permitted speed supervision limit calculated for the LX speed is reached
AND
- the current speed is lower than or equal to the LX speed restriction.
UNISIG clarification: result of the discussion with Alstom
#TEST-VAL-SUB026-7146#REF# FCT basic function Supervision of the LX start location (Q_STOPLX=0)

Chapter 5.17

#REQ-UNISIG-SUB026-006702#REF# 5.17.2.2 #REQ-UNISIG-SUB026-010422#REF#



the procedure should not be realized

Chapter 5.18

#REQ-UNISIG-SUB026-3412#REF# 5.18.2.2
“Lower pantograph announcement” shall be displayed to the driver when the max safe front end of the train reaches a location (point C) in rear
of the beginning of the powerless section (point D).

#DSC-UNISIG-SUB026-006771#REF#

Figure 13: Passing a powerless section with pantograph to be lowered
#TEST-VAL-SUB026-5569#REF# FCT basic function Indication of TC 'Powerless section, lower pantograph' - default UNISIG values

#REQ-UNISIG-SUB026-3413#REF# 5.18.2.2.1
This location (point C) shall be determined by the ERTMS/ETCS on-board equipment taking into account the time necessary for performing the
required actions and the current train speed.

#DSC-UNISIG-SUB026-006771#REF#

Figure 13: Passing a powerless section with pantograph to be lowered
#TEST-VAL-SUB026-5569#REF# FCT basic function Indication of TC 'Powerless section, lower pantograph' - default UNISIG values

#REQ-UNISIG-SUB026-010342#REF# to.5.18.2..2.1 #REQ-UNISIG-SUB040-3041:01#REF#
#ANA-UNISIG-TrackCondition-0020#REF#
The parameterized fixed time value for the TC "powerless section with pantograph to be lowered" shall be taken into account as
necessary time for calculation the starting point of the “Lower pantograph announcement”.
#TEST-VAL-SUB026-5569#REF# FCT default UNISIG value Indication of TC 'Powerless section, lower pantograph' - default UNISIG values
#TEST-VAL-SUB026-3B83#REF# FCT non-UNISIG value Indication of TC 'Powerless section, lower pantograph', non-UNISIG values

#REQ-UNISIG-SUB026-3415#REF# 5.18.2.2.2
The displayed “Lower pantograph announcement” information shall also indicate if the related functionality is executed
  automatically, or
  if the driver is requested to act.
Rel. 8.0: 
the decision is now realized in the asw
realised by: #REQ-UNISIG-SUB026-010324#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-010324#REF# 5.18.2.2.2 #REQ-UNISIG-SUB026-3415#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication "if the related functionality is executed automatically or if the driver
is requested to act" for the Information “Lower pantograph announcement”.
#TEST-VAL-SUB026-7748#REF# FCT automatic execution Indication of TC 'Powerless section, lower pantograph', automatic execution
#TEST-VAL-SUB026-3B83#REF# FCT driver action Indication of TC 'Powerless section, lower pantograph', non-UNISIG values

#REQ-UNISIG-SUB026-3414#REF# 5.18.2.3
When the max safe front end of the train reaches the start location (point D) of the powerless section:
  “Lower pantograph announcement” shall no longer be displayed to the driver,
  “Lowered Pantograph” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006771#REF#

Figure 13: Passing a powerless section with pantograph to be lowered
#TEST-VAL-SUB026-5569#REF# FCT basic function Indication of TC 'Powerless section, lower pantograph' - default UNISIG values

#REQ-UNISIG-SUB026-3423#REF# 5.18.2.5
When the min safe front end of the train reaches the “Powerless section” end location point E):
  “Lowered Pantograph” information shall no longer be displayed to the driver
  “Raise pantograph” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006771#REF#

Figure 13: Passing a powerless section with pantograph to be lowered
#TEST-VAL-SUB026-5569#REF# FCT basic function Indication of TC 'Powerless section, lower pantograph' - default UNISIG values

#REQ-UNISIG-SUB026-3424#REF# 5.18.2.5.1
The displayed “Raise pantograph” information shall also indicate if the related functionality is executed
  automatically, or
  if the driver is requested to act.
realised by: #REQ-UNISIG-SUB026-010325#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-010325#REF# 5.18.2.5.1 #REQ-UNISIG-SUB026-3424#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication "if the related functionality is executed automatically or if the driver
is requested to act" for the Information “Raise pantograph”.
#TEST-VAL-SUB026-7748#REF# FCT automatic execution Indication of TC 'Powerless section, lower pantograph', automatic execution
#TEST-VAL-SUB026-3B83#REF# FCT driver action Indication of TC 'Powerless section, lower pantograph', non-UNISIG values

#REQ-UNISIG-SUB026-3425:01#REF# 5.18.2.6 #REQ-UNISIG-SUB026-3407#REF#
The “Raise pantograph” information shall remain displayed for a fixed time (see Appendix A3.1) after the minimum safe rear end of the train has
passed the end of the “Powerless section”.

#DSC-UNISIG-SUB026-006771#REF#

Figure 13: Passing a powerless section with pantograph to be lowered
#TEST-VAL-SUB026-5569#REF# FCT default UNISIG value Indication of TC 'Powerless section, lower pantograph' - default UNISIG values
#TEST-VAL-SUB026-3B83#REF# FCT non-UNISIG value Indication of TC 'Powerless section, lower pantograph', non-UNISIG values

#REQ-UNISIG-SUB026-3430#REF# 5.18.3.2
“Neutral section announcement” shall be displayed to the driver when the max safe front end of the train reaches a location (point C) in rear of
the beginning of the powerless section.

#DSC-UNISIG-SUB026-006803#REF#

Figure 14: Passing a powerless section with main power switch to be switched off
#TEST-VAL-SUB026-5570#REF# FCT basic function Indication of TC 'Powerless section, switch off main power switch', default configuration

#REQ-UNISIG-SUB026-3429#REF# 5.18.3.2.1
This location (point C) shall be determined by the ERTMS/ETCS on-board equipment taking into account the time necessary for performing the
required actions and the current train speed.

#DSC-UNISIG-SUB026-006803#REF#

Figure 14: Passing a powerless section with main power switch to be switched off
#TEST-VAL-SUB026-5570#REF# FCT basic function Indication of TC 'Powerless section, switch off main power switch', default configuration

#REQ-UNISIG-SUB026-010343#REF# to.5.18.3.2.1 #REQ-UNISIG-SUB040-3041:01#REF#
The parameterized fixed time value for the TC "Passing a powerless section with main power switch to be switched off" shall be taken
into account as necessary time for calculation the starting point of the “Neutral section announcement”.
#TEST-VAL-SUB026-5570#REF# FCT default UNISIG value Indication of TC 'Powerless section, switch off main power switch', default configuration
#TEST-VAL-SUB026-3B84#REF# FCT non-UNISIG value Indication of TC 'Powerless section, switch off main power switch', non-UNISIG values

#REQ-UNISIG-SUB026-3431#REF# 5.18.3.2.2
The displayed “Neutral section announcement” information shall also indicate if the related functionality is executed
  automatically, or
  if the driver is requested to act.
realised by: #REQ-UNISIG-SUB026-010326#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-010326#REF# 5.18.3.2.2 #REQ-UNISIG-SUB026-3431#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication "if the related functionality is executed automatically or if the driver
is requested to act" for the Information “Neutral section announcement”.
#TEST-VAL-SUB026-7749#REF# FCT automatic execution Indication of TC 'Powerless section, switch off main power switch', automatic execution, non-UNISIG values
#TEST-VAL-SUB026-3B84#REF# FCT driver action Indication of TC 'Powerless section, switch off main power switch', non-UNISIG values

#REQ-UNISIG-SUB026-3432#REF# 5.18.3.3
When the max safe front end of the train reaches the starting location (point D) of the powerless section:
  “Neutral section announcement” shall no longer be displayed to the driver,
  “Neutral section” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006803#REF#

Figure 14: Passing a powerless section with main power switch to be switched off
#TEST-VAL-SUB026-5570#REF# FCT basic function Indication of TC 'Powerless section, switch off main power switch', default configuration

#REQ-UNISIG-SUB026-3433#REF# 5.18.3.4
When the min safe front end of the train reaches the “Powerless section” end location point E):
  “Neutral section” information shall no longer be displayed to the driver
  “End of Neutral section” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006803#REF#

Figure 14: Passing a powerless section with main power switch to be switched off
#TEST-VAL-SUB026-5570#REF# FCT basic function Indication of TC 'Powerless section, switch off main power switch', default configuration

#REQ-UNISIG-SUB026-3434#REF# 5.18.3.4.1
The displayed “End of Neutral section” information shall also indicate if the related functionality is executed
  Automatically, or
  if the driver is requested to act.
realised by: #REQ-UNISIG-SUB026-010327#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-010327#REF# 5.18.3.4.1 #REQ-UNISIG-SUB026-3434#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication "if the related functionality is executed automatically or if the driver
is requested to act" for the Information “End of Neutral section”.
#TEST-VAL-SUB026-7749#REF# FCT automatic execution Indication of TC 'Powerless section, switch off main power switch', automatic execution, non-UNISIG values
#TEST-VAL-SUB026-3B84#REF# FCT driver action Indication of TC 'Powerless section, switch off main power switch', non-UNISIG values

#REQ-UNISIG-SUB026-3435:01#REF# 5.18.3.5 #REQ-UNISIG-SUB026-3407#REF#
The “End of Neutral section” information shall remain displayed for a fixed time (see Appendix A.3.1) after the minimum safe rear end of the
train has passed the end of the “Powerless section”.

#DSC-UNISIG-SUB026-006803#REF#

Figure 14: Passing a powerless section with main power switch to be switched off
#TEST-VAL-SUB026-5570#REF# FCT default UNISIG value Indication of TC 'Powerless section, switch off main power switch', default configuration
#TEST-VAL-SUB026-3B84#REF# FCT non-UNISIG value Indication of TC 'Powerless section, switch off main power switch', non-UNISIG values

#REQ-UNISIG-SUB026-006809#REF# 5.18.4.2 #REQ-UNISIG-SUB026-006820#REF#
As long as there are non stopping areas stored on-board, the ERTMS/ETCS on-board equipment shall continuously check the current speed and
position of the train whether a full service brake command would stop the train within the closest non stopping area. This shall be achieved
taking into account two virtual SBI supervision limits (SBID and SBIG), calculated at the estimated speed from two SBD curves of which the feet
are the start location of the non stopping area (point D) and a location (point G) at train length distance in advance of the end location of
the non stopping area:
a)	If the max safe front end is in rear of the first SBI supervision limit (SBID) no information related to this non stopping area shall be
displayed
b)	If the max safe front end is in advance of first SBI supervision limit and the min safe front end in rear of the second SBI supervision
limit, the non stopping area related information shall be displayed to the driver.
c)	If the min safe front end is in advance of the second SBI supervision limit (SBIG), no information related to this non stopping area
shall be displayed and the next non stopping area stored on-board, if any, shall be checked.

#DSC-UNISIG-SUB026-006824#REF#

Figure 15: Passing a non stopping area
#TEST-VAL-SUB026-7746#REF# FCT basic function Indication of TC 'Non Stopping Area'
#TEST-VAL-SUB026-7789#REF# EET error expectation Revocation of indications related to TC 'Non Stopping Area' based on varying train speed

#REQ-UNISIG-SUB026-006814#REF# 5.18.4.3
When the max safe front end reaches the first SBI supervision limit  (point C), the “Non stopping area announcement” shall be displayed to the
driver.

#DSC-UNISIG-SUB026-006824#REF#

Figure 15: Passing a non stopping area
#TEST-VAL-SUB026-7746#REF# FCT basic function Indication of TC 'Non Stopping Area'

#REQ-UNISIG-SUB026-006816#REF# 5.18.4.4
When the max safe front end reaches the start location (point D) of the non stopping area:
  “Non stopping area announcement” shall no longer be displayed
  “Non stopping area” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006824#REF#

Figure 15: Passing a non stopping area
#TEST-VAL-SUB026-7746#REF# FCT basic function Indication of TC 'Non Stopping Area'

#REQ-UNISIG-SUB026-006820#REF# 5.18.4.5
When the min safe front end reaches the second SBI supervision limit (point F), the non stopping area information shall no longer be displayed.
correspond to 5.18.4.2 c
#DSC-UNISIG-SUB026-006824#REF#

Figure 15: Passing a non stopping area
realised by: #REQ-UNISIG-SUB026-006809#REF#

#REQ-UNISIG-SUB026-3442#REF# 5.18.5.2
When the max safe front end of the train passes the start location (point D) of the radio hole area, the “radio hole” indication shall be
displayed to the driver.

#DSC-UNISIG-SUB026-006834#REF#

Figure 16: Passing an announced radio hole
#TEST-VAL-SUB026-3B69#REF# FCT basic function Indication of TC Radio Hole

#REQ-UNISIG-SUB026-3443#REF# 5.18.5.3
When the min safe rear end of the train passes the end location (point E) of the radio hole area, the “radio hole” indication to the driver
shall be removed.

#DSC-UNISIG-SUB026-006834#REF#

Figure 16: Passing an announced radio hole
#TEST-VAL-SUB026-3B69#REF# FCT basic function Indication of TC Radio Hole

#REQ-UNISIG-SUB026-3445#REF# 5.18.6.2
“Close air conditioning intake announcement” information shall be displayed to the driver when the max safe front end of the train reaches a
location (point C) in rear of the beginning of the “air tightness” area.

#DSC-UNISIG-SUB026-006868#REF#

Figure 17: Passing an air tightness area
#TEST-VAL-SUB026-5560#REF# FCT basic function Indication of TC 'Air tightness', default configuration

#REQ-UNISIG-SUB026-3446#REF# 5.18.6.2.1 #REQ-UNISIG-SUB040-3043:01#REF#
This location (point C) shall be determined by the ERTMS/ETCS on-board equipment taking into account the time necessary for performing the
required actions and the current train speed.

#DSC-UNISIG-SUB026-006868#REF#

Figure 17: Passing an air tightness area
#TEST-VAL-SUB026-5560#REF# FCT basic function Indication of TC 'Air tightness', default configuration

#REQ-UNISIG-SUB026-010344#REF# to.5.18.6.2.1 #REQ-UNISIG-SUB040-3043:01#REF#
The parameterized fixed time value for the TC "air tightness" shall be taken into account as necessary time for calculation the
starting point of the “Close air conditioning intake announcement”.
#TEST-VAL-SUB026-5560#REF# FCT default UNISIG value Indication of TC 'Air tightness', default configuration
#TEST-VAL-SUB026-3B85#REF# FCT non-UNISIG value Indication of TC 'Air tightness', non-UNISIG values

#REQ-UNISIG-SUB026-3447#REF# 5.18.6.2.2
The displayed “Close air conditioning intake announcement” information shall also indicate if the related functionality is executed
  automatically, or
  if the driver is requested to act.
realised by: #REQ-UNISIG-SUB026-010328#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-010328#REF# 5.18.6.2.2 #REQ-UNISIG-SUB026-3447#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication "if the related functionality is executed automatically or if the driver
is requested to act" for the Information “Close air conditioning intake announcement”.
#TEST-VAL-SUB026-7750#REF# FCT automatic execution Indication of TC 'Air tightness', automatic execution
#TEST-VAL-SUB026-3B85#REF# FCT driver action Indication of TC 'Air tightness', non-UNISIG values

#REQ-UNISIG-SUB026-3448#REF# 5.18.6.3
When the max safe front end of the train reaches the start location (point D) of the air tightness area:
  “Close air conditioning intake announcement” information shall no longer be displayed.
  “Air conditioning intake closed” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006868#REF#

Figure 17: Passing an air tightness area
#TEST-VAL-SUB026-5560#REF# FCT basic function Indication of TC 'Air tightness', default configuration

#REQ-UNISIG-SUB026-3449#REF# 5.18.6.4
When the min safe rear end of the train reaches the end location (point E) of the air tightness area:
  “Air conditioning intake closed” information shall no longer be displayed;
  “Open air conditioning intake” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006868#REF#

Figure 17: Passing an air tightness area
#TEST-VAL-SUB026-5560#REF# FCT basic function Indication of TC 'Air tightness', default configuration

#REQ-UNISIG-SUB026-3450#REF# 5.18.6.4.1
The displayed “Open air conditioning intake” information shall also indicate if the related functionality is executed
  automatically, or
  If the driver is requested to act.
realised by: #REQ-UNISIG-SUB026-010329#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-010329#REF# 5.18.6.4.1 #REQ-UNISIG-SUB026-3450#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication "if the related functionality is executed automatically or if the driver
is requested to act" for the Information “Open air conditioning intake”.
#TEST-VAL-SUB026-7750#REF# FCT automatic execution Indication of TC 'Air tightness', automatic execution
#TEST-VAL-SUB026-3B85#REF# FCT driver action Indication of TC 'Air tightness', non-UNISIG values

#REQ-UNISIG-SUB026-3451:01#REF# 5.18.6.5 #REQ-UNISIG-SUB026-3407#REF#
The “Open Air Conditioning intake” information shall remain displayed for a fixed time (see Appendix A.3.1) after the minimum safe rear end of
the train has passed the end of the “Air tightness area”.

#DSC-UNISIG-SUB026-006868#REF#

Figure 17: Passing an air tightness area
#TEST-VAL-SUB026-5560#REF# FCT default UNISIG value Indication of TC 'Air tightness', default configuration
#TEST-VAL-SUB026-3B85#REF# FCT non-UNISIG value Indication of TC 'Air tightness', non-UNISIG values

#REQ-UNISIG-SUB026-3460:01#REF# 5.18.7.2
The procedure shows the case of the regenerative brake. Regarding eddy current brake for SB as well as EB and magnetic shoe brake, the procedure
is identical except that the displayed indications refer respectively eddy current brake or magnetic shoe brake.
realised by: #REQ-UNISIG-SUB026-3454:01#REF#
realised by: #REQ-UNISIG-SUB026-3455:02#REF#
realised by: #REQ-UNISIG-SUB026-3457:01#REF#
realised by: #REQ-UNISIG-SUB026-3458:01#REF#

#REQ-UNISIG-SUB026-3715#REF# 5.18.7.3
“Inhibition of Regenerative Brake announcement” information shall be displayed to the driver when the max safe front end of the train reaches a
location (Point C) in rear of the beginning of the regenerative brake inhibition area.

#DSC-UNISIG-SUB026-006892#REF#

Figure 18: Passing an area where Regenerative Brake shall be inhibited
realised by: #REQ-UNISIG-SUB026-3454:01#REF#

#REQ-UNISIG-SUB026-3454:01#REF# 5.18.7.3 #REQ-UNISIG-SUB026-3460:01#REF#
#REQ-UNISIG-SUB026-3715#REF#
An announcement of a track condition of type "switch of ..." shall be displayed to the driver when the max safe front end of the train
reaches a location (Point C) in rear of the beginning of this track condition area.
TEST APPROACH:
The following aspects have been identified:
1) eddy current brake EB
2) eddy current brake SB
3) magnetic shoe brake
4) regenerative brake
#TEST-VAL-SUB026-3B89#REF# FCT 1 Indication of TC eddy current brake - EB, default configuration
#TEST-VAL-SUB026-5564#REF# FCT 2 Indication of TC eddy current brake - SB, default configuration
#TEST-VAL-SUB026-5565#REF# FCT 3 Indication of TC magnetic shoe brake, default configuration
#TEST-VAL-SUB026-5563#REF# FCT 4 Indication of TC inhibition of regenerative brake, default configuration

#REQ-UNISIG-SUB026-3716#REF# 5.18.7.3.1
The displayed “Inhibition of Regenerative Brake announcement” information shall also indicate if the related functionality is executed
  automatically, or
  if the driver is requested to act.
realised by: #REQ-UNISIG-SUB026-3455:02#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-3455:02#REF# 5.18.7.3.1 #REQ-UNISIG-SUB026-3460:01#REF#
#REQ-UNISIG-SUB026-3716#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication, if the related functionality is executed automatically or if the driver is
requested to act" for the Information “switch of ... announcement”.
TEST APPROACH:
The following aspects have been identified:
1) eddy current brake EB
1.1) automatic execution
1.2) driver action
2) eddy current brake SB
2.1) automatic execution
2.2) driver action
3) magnetic shoe brake
3.1) automatic execution
3.2) driver action
4) regenerative brake
4.1) automatic execution
4.2) driver action
#TEST-VAL-SUB026-7753#REF# FCT 1.1 Indication of TC inhibition of eddy current brake EB, automatic execution
#TEST-VAL-SUB026-3B92#REF# FCT 1.2 Indication of TC inhibition of eddy current brake EB, non-UNISIG values
#TEST-VAL-SUB026-7752#REF# FCT 2.1 Indication of TC inhibition of eddy current brake SB, automatic execution
#TEST-VAL-SUB026-3B90#REF# FCT 2.2 Indication of TC inhibition of eddy current brake SB, non-UNISIG values
#TEST-VAL-SUB026-7754#REF# FCT 3.1 Indication of TC inhibition of magnetic shoe brake, automatic execution
#TEST-VAL-SUB026-3B91#REF# FCT 3.2 Indication of TC inhibition of magnetic shoe brake, non-UNISIG values
#TEST-VAL-SUB026-7751#REF# FCT 4.1 Indication of TC inhibition of regenerative brake, automatic execution
#TEST-VAL-SUB026-3B86#REF# FCT 4.2 Indication of TC inhibition of regenerative brake, non-UNISIG values

#REQ-UNISIG-SUB026-3456#REF# 5.18.7.3.2 #REQ-UNISIG-SUB040-3043:01#REF#
This location (point C) shall be determined by the On-Board equipment taking into account the time necessary for performing the required actions
and the current train speed.

#DSC-UNISIG-SUB026-006892#REF#

Figure 18: Passing an area where Regenerative Brake shall be inhibited
TEST APPROACH:
The following aspects have been identified:
1) eddy current brake EB
2) eddy current brake SB
3) magnetic shoe brake
4) regenerative brake
#TEST-VAL-SUB026-3B89#REF# FCT 1 Indication of TC eddy current brake - EB, default configuration
#TEST-VAL-SUB026-5564#REF# FCT 2 Indication of TC eddy current brake - SB, default configuration
#TEST-VAL-SUB026-5565#REF# FCT 3 Indication of TC magnetic shoe brake, default configuration
#TEST-VAL-SUB026-5563#REF# FCT 4 Indication of TC inhibition of regenerative brake, default configuration

#REQ-UNISIG-SUB026-010345#REF# to.5.18.7.3.2 #REQ-UNISIG-SUB040-3043:01#REF#
The parameterized fixed time value for the TC "Switch off regenerative/eddy current (service/emergency)/magnetic shoe brake" shall be
taken into account as necessary time for calculation the starting point of the “switch of ... announcement”.
TEST APPROACH:
The following aspects were identified:
1) UNISIG default configuration
1.1) eddy current brake EB 
1.2) eddy current brake SB
1.3) magnetic shoe brake 
1.4) regenerative brake 
2) non-UNISIG configuration
2.1) eddy current brake EB 
2.2) eddy current brake SB
2.3) magnetic shoe brake 
2.4) regenerative brake 
#TEST-VAL-SUB026-3B89#REF# FCT 1.1 Indication of TC eddy current brake - EB, default configuration
#TEST-VAL-SUB026-5564#REF# FCT 1.2 Indication of TC eddy current brake - SB, default configuration
#TEST-VAL-SUB026-5565#REF# FCT 1.3 Indication of TC magnetic shoe brake, default configuration
#TEST-VAL-SUB026-5563#REF# FCT 1.4 Indication of TC inhibition of regenerative brake, default configuration
#TEST-VAL-SUB026-3B92#REF# FCT 2.1 Indication of TC inhibition of eddy current brake EB, non-UNISIG values
#TEST-VAL-SUB026-3B90#REF# FCT 2.2 Indication of TC inhibition of eddy current brake SB, non-UNISIG values
#TEST-VAL-SUB026-3B91#REF# FCT 2.3 Indication of TC inhibition of magnetic shoe brake, non-UNISIG values
#TEST-VAL-SUB026-3B86#REF# FCT 2.4 Indication of TC inhibition of regenerative brake, non-UNISIG values

#REQ-UNISIG-SUB026-3717#REF# 5.18.7.4
When the max safe front end of the train reaches the start location (point D) of the regenerative brake inhibition area:
  Indication “Inhibition of Regenerative Brake announcement” shall no longer be displayed,
  Indication “Inhibition of Regenerative Brake” shall be displayed to the driver.

#DSC-UNISIG-SUB026-006892#REF#

Figure 18: Passing an area where Regenerative Brake shall be inhibited
realised by: #REQ-UNISIG-SUB026-3457:01#REF#

#REQ-UNISIG-SUB026-3457:01#REF# 5.18.7.4 #REQ-UNISIG-SUB026-3460:01#REF#
#REQ-UNISIG-SUB026-3717#REF#
When the max safe front end of the train reaches the start location (point D) of a track condition area of type "switch of ...":
∙ Indication of the announcement shall no longer be displayed,
∙ Indication of the track condition shall be displayed to the driver.
TEST APPROACH:
The following aspects have been identified:
1) eddy current brake EB
2) eddy current brake SB
3) magnetic shoe brake
4) regenerative brake
#TEST-VAL-SUB026-3B89#REF# FCT 1 Indication of TC eddy current brake - EB, default configuration
#TEST-VAL-SUB026-5564#REF# FCT 2 Indication of TC eddy current brake - SB, default configuration
#TEST-VAL-SUB026-5565#REF# FCT 3 Indication of TC magnetic shoe brake, default configuration
#TEST-VAL-SUB026-5563#REF# FCT 4 Indication of TC inhibition of regenerative brake, default configuration

#REQ-UNISIG-SUB026-3718#REF# 5.18.7.5
When the min safe rear end of the train reaches the end location (point E) of the regenerative brake inhibition area the indication “Inhibition
of Regenerative Brake” information shall no longer be displayed.

#DSC-UNISIG-SUB026-006892#REF#

Figure 18: Passing an area where Regenerative Brake shall be inhibited
realised by: #REQ-UNISIG-SUB026-3458:01#REF#

#REQ-UNISIG-SUB026-3458:01#REF# 5.18.7.5 #REQ-UNISIG-SUB026-3460:01#REF#
#REQ-UNISIG-SUB026-3718#REF#
When the min safe rear end of the train reaches the end location (point E) of a track condition area of type "switch of ..." the
indication of this track condition shall no longer be displayed.
TEST APPROACH:
The following aspects have been identified:
1) eddy current brake EB
2) eddy current brake SB
3) magnetic shoe brake
4) regenerative brake
#TEST-VAL-SUB026-3B89#REF# FCT 1 Indication of TC eddy current brake - EB, default configuration
#TEST-VAL-SUB026-5564#REF# FCT 2 Indication of TC eddy current brake - SB, default configuration
#TEST-VAL-SUB026-5565#REF# FCT 3 Indication of TC magnetic shoe brake, default configuration
#TEST-VAL-SUB026-5563#REF# FCT 4 Indication of TC inhibition of regenerative brake, default configuration

#REQ-UNISIG-SUB026-006900#REF# 5.18.8.2
On driver request, the ERTMS/ETCS on-board equipment shall enable/disable the display of the tunnel stopping area related information (initial
state: disabled).
is realized with ERA SRS DMI

#REQ-UNISIG-SUB026-006902#REF# 5.18.8.3
As long as the display of the tunnel stopping areas is enabled (point C) and there are tunnel stopping areas stored on-board, the ERTMS/ETCS
on-board equipment shall continuously check the current speed and position of the train to determine whether the driver can stop the train with
the full service brake before reaching the end of the closest tunnel stopping area. This shall be achieved taking into account a virtual
Permitted supervision limit (with no contribution of the GUI curve, if any), calculated at the estimated speed from an SBD curve of which the
foot is the end location of the tunnel stopping area:
a)	If the train front end is in rear of the Permitted supervision limit, the tunnel stopping area related information shall be displayed to
the driver.
b)	If the train front end is in advance of the Permitted supervision limit, no information related to this tunnel stopping area shall be
displayed and the next tunnel stopping area stored on-board, if any, shall be checked.

#DSC-UNISIG-SUB026-006914#REF#

Figure 19: Advising a tunnel stopping area
#TEST-VAL-SUB026-7745#REF# FCT basic function Indication of TC 'Tunnel Stopping Area'
#TEST-VAL-SUB026-7767#REF# EET error expectation Indication of TC 'Tunnel Stopping Area', varying train speed
#TEST-VAL-SUB026-7790#REF# EET error expectation Indication of TSA when two TSA exist close to each other

#REQ-UNISIG-SUB026-006906#REF# 5.18.8.4
Before the train reaches the start location (point D) of the tunnel stopping area, the “tunnel stopping area announcement” shall be displayed to
the driver. This shall include the indication of the remaining distance to the start location of the tunnel stopping area.

#DSC-UNISIG-SUB026-006914#REF#

Figure 19: Advising a tunnel stopping area
#TEST-VAL-SUB026-7745#REF# FCT basic function Indication of TC 'Tunnel Stopping Area'

#REQ-UNISIG-SUB026-006908#REF# 5.18.8.5
When the train front end reaches the start location (point D) of the tunnel stopping area:
  “Tunnel stopping area announcement” shall no longer be displayed
  “Tunnel stopping area” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-006914#REF#

Figure 19: Advising a tunnel stopping area
#TEST-VAL-SUB026-7745#REF# FCT basic function Indication of TC 'Tunnel Stopping Area'

#REQ-UNISIG-SUB026-006920#REF# 5.18.9.2
“Sound horn” shall be displayed to the driver when the estimated front end of the train reaches a location (point C) in rear of the beginning of
the “sound horn” area (point D).

#DSC-UNISIG-SUB026-006928#REF#

Figure 20: Sounding the Horn
#TEST-VAL-SUB026-7724#REF# FCT basic function Indication of TC 'Sound horn', default configuration

#REQ-UNISIG-SUB026-006922#REF# 5.18.9.2.1 #REQ-UNISIG-SUB026-010110#REF#
This location shall be determined by the ERTMS/ETCS on-board equipment taking into account the time necessary for the driver to perform the
required action (see Appendix A.3.1) and the current train speed.
#TEST-VAL-SUB026-7724#REF# FCT basic function Indication of TC 'Sound horn', default configuration

#REQ-UNISIG-SUB026-006924#REF# 5.18.9.3
When the estimated front end of the train reaches the end location (point E) of the “sound horn” area, the indication “Sound horn” information
shall no longer be displayed.

#DSC-UNISIG-SUB026-006928#REF#

Figure 20: Sounding the Horn
#TEST-VAL-SUB026-7724#REF# FCT basic function Indication of TC 'Sound horn', default configuration

#REQ-UNISIG-SUB026-010313#REF# 5.18.10.2
“Change of traction system announcement” shall be displayed to the driver when the max safe front end of the train reaches a location (point C)
in rear of the location of change of traction system (point F).

#DSC-UNISIG-SUB026-010320#REF#

Figure 21: Changing the traction system
#TEST-VAL-SUB026-5566#REF# FCT basic function Indication of TC change of traction system, default configuration

#REQ-UNISIG-SUB026-010314#REF# 5.18.10.3
This location (point C) shall be determined by the ERTMS/ETCS on-board equipment taking into account the time necessary for performing the
required actions and the current train speed.
the relevant time is defined in Subset 40, 4.2.4.7.1
#DSC-UNISIG-SUB026-010320#REF#

Figure 21: Changing the traction system
#TEST-VAL-SUB026-5566#REF# FCT basic function Indication of TC change of traction system, default configuration

#REQ-UNISIG-SUB026-010348#REF# to.5.18.10.3.2 #REQ-UNISIG-SUB040-3041:01#REF#
The parameterized fixed time value for the TC "Change of traction system" shall be taken into account as necessary time for
calculation the starting point of the “Change of traction system announcement”.
#TEST-VAL-SUB026-5566#REF# FCT default UNISIG value Indication of TC change of traction system, default configuration
#TEST-VAL-SUB026-3B87#REF# FCT non-UNISIG value Indication of TC change of traction system, non-UNISIG values

#REQ-UNISIG-SUB026-010315#REF# 5.18.10.4
The displayed “Change of traction system announcement” information shall also indicate if the related functionality is executed
  automatically, or
  if the driver is requested to act.
realised by: #REQ-UNISIG-SUB026-010323#REF#
realised by: #REQ-UNISIG-SUB026-010322#REF#

#REQ-UNISIG-SUB026-010323#REF# 5.18.10.4 #REQ-UNISIG-SUB026-010315#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
The relevant parameterized value shall be used for the indication "if the related functionality is executed automatically or if the driver
is requested to act" for the Information “Change of traction system announcement”.
#TEST-VAL-SUB026-7755#REF# FCT automatic execution Indication of TC change of traction system, automatic execution, non-UNISIG values
#TEST-VAL-SUB026-3B87#REF# FCT driver action Indication of TC change of traction system, non-UNISIG values

#REQ-UNISIG-SUB026-3428:01#REF# 5.18.10.5
When the max safe front end of the train reaches the “Change of traction system” location (point F):
∙	the “Change of traction system announcement” information shall no longer be displayed to the driver,
∙	the “New traction system” information shall be displayed to the driver.

#DSC-UNISIG-SUB026-010320#REF#

Figure 21: Changing the traction system
#TEST-VAL-SUB026-5566#REF# FCT basic function Indication of TC change of traction system, default configuration

#REQ-UNISIG-SUB026-010318#REF# 5.18.10.6 #REQ-UNISIG-SUB026-3407#REF#
The “New traction system” information shall remain displayed for a fixed time (see Appendix A3.1) after the minimum safe rear end of the train
has passed the “Change of traction system” location (point F).

#DSC-UNISIG-SUB026-010320#REF#

Figure 21: Changing the traction system
#TEST-VAL-SUB026-5566#REF# FCT default UNISIG value Indication of TC change of traction system, default configuration
#TEST-VAL-SUB026-3B87#REF# FCT non-UNISIG value Indication of TC change of traction system, non-UNISIG values

#REQ-UNISIG-SUB026-010322#REF# to.5.18 #REQ-UNISIG-SUB026-3415#REF#
#REQ-UNISIG-SUB026-3424#REF#
#REQ-UNISIG-SUB026-3431#REF#
#REQ-UNISIG-SUB026-3434#REF#
#REQ-UNISIG-SUB026-3447#REF#
#REQ-UNISIG-SUB026-3450#REF#
#REQ-UNISIG-SUB026-3716#REF#
#REQ-UNISIG-SUB026-010315#REF#
#ANA-UNISIG-TrackCondition-0019#REF#
A parameterizable value for indication "automatically or driver is requested to act" shall be provided for each of the following track
conditions:
• Powerless section, lower pantograph
• Powerless section, switch off main power switch
• Air tightness
• Switch off regenerative brake
• Switch off eddy current brake for SB
• Switch off eddy current brake for EB
• Switch off magnetic shoe brake
• Change of traction system

"driver is requested to act" shall be set as default value.
TEST APPROACH:
The following aspects have been identified:
1) Powerless section, lower pantograph
1.1) automatic execution
1.2) driver action
2) Powerless section, switch off main power switch
2.1) automatic execution
2.2) driver action
3) Air tightness
3.1) automatic execution
3.2) driver action
4) Switch off regenerative brake
4.1) automatic execution
4.2) driver action
5) Switch off eddy current brake for SB
5.1) automatic execution
5.2) driver action
6) Switch off eddy current brake for EB
6.1) automatic execution
6.2) driver action
7) Switch off magnetic shoe brake
7.1) automatic execution
7.2) driver action
8) Change of traction system
8.1) automatic execution
8.2) driver action
#TEST-VAL-SUB026-7748#REF# FCT 1.1 Indication of TC 'Powerless section, lower pantograph', automatic execution
#TEST-VAL-SUB026-3B83#REF# FCT 1.2 Indication of TC 'Powerless section, lower pantograph', non-UNISIG values
#TEST-VAL-SUB026-7749#REF# FCT 2.1 Indication of TC 'Powerless section, switch off main power switch', automatic execution, non-UNISIG values
#TEST-VAL-SUB026-3B84#REF# FCT 2.2 Indication of TC 'Powerless section, switch off main power switch', non-UNISIG values
#TEST-VAL-SUB026-7750#REF# FCT 3.1 Indication of TC 'Air tightness', automatic execution
#TEST-VAL-SUB026-3B85#REF# FCT 3.2 Indication of TC 'Air tightness', non-UNISIG values
#TEST-VAL-SUB026-7751#REF# FCT 4.1 Indication of TC inhibition of regenerative brake, automatic execution
#TEST-VAL-SUB026-3B86#REF# FCT 4.2 Indication of TC inhibition of regenerative brake, non-UNISIG values
#TEST-VAL-SUB026-7752#REF# FCT 5.1 Indication of TC inhibition of eddy current brake SB, automatic execution
#TEST-VAL-SUB026-3B90#REF# FCT 5.2 Indication of TC inhibition of eddy current brake SB, non-UNISIG values
#TEST-VAL-SUB026-7753#REF# FCT 6.1 Indication of TC inhibition of eddy current brake EB, automatic execution
#TEST-VAL-SUB026-3B92#REF# FCT 6.2 Indication of TC inhibition of eddy current brake EB, non-UNISIG values
#TEST-VAL-SUB026-7754#REF# FCT 7.1 Indication of TC inhibition of magnetic shoe brake, automatic execution
#TEST-VAL-SUB026-3B91#REF# FCT 7.2 Indication of TC inhibition of magnetic shoe brake, non-UNISIG values
#TEST-VAL-SUB026-7755#REF# FCT 8.1 Indication of TC change of traction system, automatic execution, non-UNISIG values
#TEST-VAL-SUB026-3B87#REF# FCT 8.2 Indication of TC change of traction system, non-UNISIG values

#REQ-UNISIG-SUB026-3581#REF# to.5.18 #ANA-UNISIG-TrackCondition-0003#REF#
If  track conditions of the same type are overlapped in the announce-/quitting area, the track condition shall be indicated in the actual order
with the following priority:
1. tc is active
2. track condition is announced
3. track condition is left
The prioritisation is necessary, because a overlapping of the announce/raise area is possible.
#TEST-VAL-SUB026-7757#REF# FCT basic function Priority of informations to display for TC 'Powerless section, lower pantograph'
#TEST-VAL-SUB026-7758#REF# EET error expectation Priority of TC display information when new TC of same type is received
#TEST-VAL-SUB026-7790#REF# EET error expectation Indication of TSA when two TSA exist close to each other

Chapter 5.19

#REQ-UNISIG-SUB026-3669#REF# 5.19.2.1
In a level 1 area, the beginning of the Limited Supervision area can be the balise (group) that gives the Mode Profile. When the train passes
the balise group and receives this information, the ERTMS/ETCS on-board equipment shall immediately switch to Limited Supervision mode.
Justification: 
The reference to level 1 is not relevant for obu.
realised by: #REQ-UNISIG-SUB026-3671:01#REF#

#REQ-UNISIG-SUB026-3670#REF# 5.19.2.2
In a level 2 or 3 area, the ERTMS/ETCS on-board equipment can receive a mode profile giving a Limited Supervision area which the train has
already entered with its max safe front end. In this case, the ERTMS/ETCS on-board equipment shall immediately switch to Limited Supervision
mode.
Justification: 
The reference to level 2/3 is not relevant for obu.
realised by: #REQ-UNISIG-SUB026-3671:01#REF#

#REQ-UNISIG-SUB026-3671:01#REF# to.5.19.2.1.and 5.19.2.2 #REQ-UNISIG-SUB026-3669#REF#
#REQ-UNISIG-SUB026-3670#REF#
The obu shall immediately switch to Limited Supervision mode, if
- a mode profile giving a Limited Supervision area is received and max safe front end of the train is already inside this area
AND
- the mode is not SB and PT.
TEST APPROACH:
The following aspects have been identified:
1) D_MAMODE > 0
2) D_MAMODE = 0
#TEST-VAL-SUB026-5652#REF# FCT 1 Reception of MP LS max safe front end of the train is already inside this area
#TEST-VAL-SUB026-4549#REF# FCT 2 Mode transition L2 SR->LS[72]->SR[37]
#TEST-VAL-SUB026-5457#REF# EET CFX00040274 Multiple mode transition LS/OS

#REQ-UNISIG-SUB026-3515#REF# 5.19.2.3 #REQ-UNISIG-SUB026-3507#REF#
The driver must acknowledge the Limited Supervision mode. A request of acknowledgement shall be displayed to the driver.
TEST APPROACH:
The following aspects have been identified:
1) D_MAMODE > 0
2) D_MAMODE = 0
#TEST-VAL-SUB026-4549#REF# FCT 1 Mode transition L2 SR->LS[72]->SR[37]
#TEST-VAL-SUB026-4547#REF# FCT 2 Adhesions factor from track side in LS, L1 FS->LS[72]

#REQ-UNISIG-SUB026-3516#REF# 5.19.2.4 #REQ-UNISIG-SUB026-007978#REF#
If the driver has not acknowledged after the driver acknowledgement time (refer to Appendix A.3.1), the service brake command shall be
triggered. The brake command is released when the driver acknowledges, except if brakes are also applied for another reason(s).
realised by: #REQ-UNISIG-SUB026-3527#REF#

#REQ-UNISIG-SUB026-3517#REF# 5.19.2.7
If the ERTMS/ETCS on-board equipment is already in LS mode when receiving the LS mode profile, no further acknowledgement shall be requested
from the driver.
Justification:
This requirement define the case, that the same mode profile is received again.
TEST APPROACH:
The following aspects have been identified:
1) D_MAMODE > 0
2) D_MAMODE = 0
3) special case overlapping MP
#TEST-VAL-SUB026-5773#REF# FCT 1 OBU is already in LS mode when receiving the LS mode profile
#TEST-VAL-SUB026-5775#REF# FCT 2 No further LS acknowledgement request in LS Mode
#TEST-VAL-SUB026-5774#REF# FCT 3 Two overlapping MP-LS area (different V_MAMODE)

#REQ-UNISIG-SUB026-3519:01#REF# 5.19.3.2
A request for acknowledgement shall be displayed to the driver when the following conditions are fulfilled:
a)	 The distance between the estimated front end of the train and the beginning of Limited Supervision area is shorter than a value,
contained in the mode profile.
b)	The speed is lower than the Limited Supervision mode speed limit (national value, or value given in the mode profile).
c)	The current mode is not Limited Supervision
TEST APPROACH:
The following aspects have been identified:
1) The distance between the estimated front end of the train and the beginning of Limited Supervision area is shorter than a value, contained in
the mode profile.
2) The speed is lower than the Limited Supervision mode speed limit
2.1) national value
2.2) value given in the mode profile
3) The current mode is not Limited Supervision 
#TEST-VAL-SUB026-5248#REF# FCT 1 Once the LS acknowledgment request is displayed, it is not taken back if the train speed exceeds V_MAMODE
#TEST-VAL-SUB026-5250#REF# FCT 2.1 No LS acknowledgment request when entering acknowledgment window if train speed exceeds V_NVLIMSUPERV (V_MAMODE=127)
#TEST-VAL-SUB026-5238#REF# FCT 2.2 No LS acknowledgment request when entering acknowledgment window if train speed exceeds V_MAMODE (/=127)
#TEST-VAL-SUB026-3818#REF# FCT 3 , CFX00039908 Entry into LS acknowledgment window for further LS area in LS (gap between LS areas)

#REQ-UNISIG-SUB026-3521#REF# 5.19.3.4
Once the acknowledgement request is displayed, it is not taken back if the train leaves the “rectangle of acknowledgement” (for example: because
the train accelerates).
TEST APPROACH:
The following aspects have been identified:
1) speed condition not fulfilled anymore 
2) location condition not fulfilled anymore 
3) condition for mode change not valid any more
#TEST-VAL-SUB026-5248#REF# FCT 1 Once the LS acknowledgment request is displayed, it is not taken back if the train speed exceeds V_MAMODE
#TEST-VAL-SUB026-5249#REF# FCT 2 Once the LS acknowledgment request is displayed, it is not taken back if the train sets back out of ack window
#TEST-VAL-SUB026-5255#REF# FCT 3 LS acknowledgment request if acknowledgment would not lead to a transition to LS

#REQ-UNISIG-SUB026-3523:01#REF# 5.19.3.5
Until the ERTMS/ETCS on-board equipment has switched to LS mode, according to the mode profile, the beginning of the Limited Supervision area
shall be temporarily considered either as the EOA (keeping the SvL given by the MA) or as both the EOA and SvL (instead of the EOA and SvL given
by the MA), with no Release Speed.
UNISIG clarification:
"with no release speed" is valid for both conditions
TEST APPROACH:
The speed and distance monitoring evaluates the targets mode independent refer to SUBSET-026 3.13. The actual brake curve calculation is tested
by the appropriated module tests. The test outlined here has to be ensured that the EoA, SvL and release speed provided to the module BC agree
with the requirement.
The following aspects have been identified:
1) Q_MAMODE dependency (black box)
2) EOA and SvL depending on Q_MAMODE (BC input)
3) no release speed
#TEST-VAL-SUB026-5764#REF# FCT 1 Start of LS area supervision
#TEST-VAL-SUB026-5760#REF# FCT 2 LS area start considered either as the EOA (keeping the SvL given by the MA) or as both the EOA and SvL depending on Q_MAMODE
#TEST-VAL-SUB026-5768#REF# FCT 3 Start of MP-LS supervised without release speed

#REQ-UNISIG-SUB026-3524#REF# 5.19.3.6 #REQ-UNISIG-SUB026-3507#REF#
When the driver acknowledges the Limited Supervision mode, the ERTMS/ETCS on-board equipment shall immediately switch to the Limited Supervision
mode.

#DSC-UNISIG-SUB026-006975#REF#

Figure 23: Transition to LS mode after driver acknowledgement
#TEST-VAL-SUB026-4551#REF# FCT basic function TSR when entering LS, TSR in LS; OS->LS[70]

#REQ-UNISIG-SUB026-3525#REF# 5.19.3.7 #REQ-UNISIG-SUB026-0582#REF#
If the max safe front end of the train reaches the beginning of the Limited Supervision area according the mode profile and the driver has not
yet acknowledged, the ERTMS/ETCS on-board equipment shall switch immediately to LS mode and a request for acknowledgement shall be displayed to
the driver (refer to SRS chapter 4, transitions between modes).
#TEST-VAL-SUB026-4553#REF# FCT basic function Mode transition L1 OS->LS[74]->OS[15]

#REQ-UNISIG-SUB026-3526#REF# 5.19.3.8 #REQ-UNISIG-SUB026-007978#REF#
If, in this case, the driver does not acknowledge within the driver acknowledgement time (refer to Appendix A.3.1) after the change to LS mode,
the service brake command shall be triggered. The command shall be released as soon as the driver acknowledges (unless the command was triggered
also for other reasons).
realised by: #REQ-UNISIG-SUB026-3527#REF#

#REQ-UNISIG-SUB026-3527#REF# 5.19.3.8 #REQ-UNISIG-SUB026-3516#REF#
#REQ-UNISIG-SUB026-3526#REF#
#ANA-UNISIG-ModeProfile-0002#REF#
If the driver does not acknowledge within the driver acknowledgement time (refer to Appendix A3.1) after the change to LS mode, the service
brake command shall be triggered. The command shall be released as soon as the driver acknowledges (unless the command was triggered also for
other reasons) or the acknowledgement is not possible anymore.
realizes 5.19.2.4 and 5.19.3.8
TEST APPROACH:
The following aspects have been identified:
1) LS mode requested for a further location 
2) LS mode requested for a further current location
3) Brake command was triggered also for other reasons
#TEST-VAL-SUB026-5772#REF# FCT 1 T_ACK supervision in LS
#TEST-VAL-SUB026-4552#REF# FCT 2 Mode transition L2 OS->LS[72]->OS[40]
#TEST-VAL-SUB026-5771#REF# FCT 3 Brake due to missing LS acknowledgment and over speed in LS

#REQ-UNISIG-SUB026-3528#REF# 5.19.4.1
The mode profile with regards to an LS area is only evaluated in levels 1,2,3, although the mode profile may have been received in level 0
(Unfitted mode) or NTC (SN mode). A transition to Limited Supervision mode can therefore earliest occur at a transition of level: from level 0
or NTC to level 1 or 2 or 3.
realised by: #REQ-UNISIG-SUB026-3484#REF#

#REQ-UNISIG-SUB026-3529#REF# 5.19.5.1 #REQ-UNISIG-SUB026-1102:01#REF#
#REQ-DESIGN-CR-0137:02#REF#
When performing a SoM or a Train Trip procedure and when the current level is 2 or 3, the ERTMS/ETCS on-board equipment can receive a mode
profile giving an Limited Supervision area which the train has already entered with its max safe front end. In this case, the ERTMS/ETCS
on-board equipment shall first require an acknowledgement from the driver.
realizes through SoM (S25) and Post Trip Procedure (S170)
realised by: #REQ-UNISIG-SUB026-3697#REF#

#REQ-UNISIG-SUB026-3697#REF# 5.19.5.1 #REQ-UNISIG-SUB026-3529#REF#
#REQ-UNISIG-SUB026-3507#REF#
#REQ-UNISIG-SUB026-010419#REF#
#ANA-UNISIG-Procedure-0001#REF#
If a mode profile requiring Limited Supervision is accepted in the modes SB or PT and the train has already entered the mode profile area with
its max safe front end, the ERTMS/ETCS on-board equipment shall first require an ackowledgement from the driver.

Remark: The mode change to Limited Supervision is execute after the ackowledgement from the driver (see condition[70] in 4.6.3).
gilt auch bei Erhalt eines Modeprofils vor Betätigen der Start-Taste
TEST APPROACH:
The following aspects have been identified:
1) PT
1.1) START selected
1.2) START not selected
2) SB
2.1) START selected
2.2) START not selected
#TEST-VAL-SUB026-4558#REF# FCT 1.1, 2.2 linking information when entering LS, L2 LS->SB[28]->LS[70]->TR[66] ->PT->LS[70]
#TEST-VAL-SUB026-4560#REF# FCT 1.2 mode transition LS->TR[65], PT->LS[70]->UN[21]
#TEST-VAL-SUB026-5559#REF# FCT 2.1 transition from SB to LS [70], SoM beyond S20

#REQ-UNISIG-SUB026-3530#REF# 5.19.5.2
When the driver acknowledges, the ERTMS/ETCS on-board equipment shall perform the transition to Limited Supervision mode.
realizes through 4.6.3, condition[70]
realised by: #REQ-UNISIG-SUB026-3396#REF#

#REQ-UNISIG-SUB026-3531#REF# 5.19.6.1.1 #REQ-UNISIG-SUB026-0583#REF#
The ERTMS/ETCS on-board equipment exits the Limited Supervision mode when the min safe front end of the train passes the end of the Limited
supervision area.
#TEST-VAL-SUB026-4544#REF# FCT basic function Pkt 72 M_MODETEXTDISPLAY = LS, L1 FS->LS[70]->FS[32]

#REQ-UNISIG-SUB026-3532#REF# 5.19.6.3.2
When exiting the Limited Supervision area, the ERTMS/ETCS on-board equipment switches either to Full Supervision, On Sight or to Shunting mode
(refer to SRS chapter 4, transitions between modes).
realizes through mode transition table 4.6.2/4.6.3
realised by: #REQ-UNISIG-SUB026-3372#REF#
realised by: #REQ-UNISIG-SUB026-3373#REF#
realised by: #REQ-UNISIG-SUB026-3375:01#REF#

Chapter 6

Chapter 6.5

TEST APPROACH:
The coding of packets as well as the acceptance check according to the requirements outlined hereafter is realized centrally by the software
module packet handler (PH). 
The requirements are thoroughly tested by PH module verification.
The quality of the module tests is ensured by review of the module test specification and test implementation as part of the module review. The
result of the review is documented in /ESBO_UUE/ --> reference ID ESBO_VerBer.
		
#REQ-UNISIG-SUB026-010336#REF# 6.5.1.5.3
Section 7.4.2.0 (Packet Number 0: Virtual Balise Cover marker) shall not apply.
realised by: #REQ-UNISIG-SUB026-010566#REF#

#REQ-UNISIG-SUB026-010566#REF# to.6.5.1.5.3 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010336#REF#
If the information "Virtual Balise Cover marker" (Packet 0) is received with ETCS Language version 1.x, this information shall be
ignored and interpreted as a data consistency error.
#ANALYSE-VALUNISIG-5324#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007121#REF# 6.5.1.5.4
Table 7.4.2.1.1 (Packet Number 3: National Values) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-0332:01#REF#

#REQ-UNISIG-SUB026-0332:01#REF# to.6.5.1.5.4 #REQ-UNISIG-SUB026-007121#REF#
#REQ-UNISIG-SUB026-007262#REF#
If Packet Number 3 (National Values) is received with ETCS Language version 1.x, the following structure shall be used for decoding:


Q_NVSRBKTRG is equivalent to Q_NVSBFBPERM in baseline 3. Therefore e separat definition of Q_NVSRBKTRG is not necessary.
#ANALYSE-VALUNISIG-4781#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007124#REF# 6.5.1.5.5
Section 7.4.2.3.1 (Packet Number 13: Staff Responsible distance Information from loop) shall not apply.
realised by: #REQ-UNISIG-SUB026-010337#REF#

#REQ-UNISIG-SUB026-010337#REF# to.6.5.1.5.5 #REQ-UNISIG-SUB026-007124#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the information "Staff Responsible distance Information from loop" (Packet 13) is received with ETCS Language version 1.x, this
information shall be ignored and interpreted as a data consistency error.
#ANALYSE-VALUNISIG-5319#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007126#REF# 6.5.1.5.6
Table 7.4.2.7 (Packet Number 27: International Static Speed Profile) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010196#REF#

#REQ-UNISIG-SUB026-010196#REF# to.6.5.1.5.6 #REQ-UNISIG-SUB026-007126#REF#
#REQ-UNISIG-SUB026-007262#REF#
If Packet Number 27 (International Static Speed Profile) is received with ETCS Language version 1.x, the following structure shall be used for
decoding:


#ANALYSE-VALUNISIG-4786#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007129#REF# 6.5.1.5.7
Table 7.4.2.8 (Packet Number 39: Track Condition Change of traction system) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010352#REF#

#REQ-UNISIG-SUB026-010352#REF# to.6.5.1.5.7 #REQ-UNISIG-SUB026-007129#REF#
#REQ-UNISIG-SUB026-007262#REF#
If Packet Number 39 (Track Condition Change of traction system) is received with ETCS Language version 1.x, the  following structure shall be
used for decoding:


#ANALYSE-VALUNISIG-5307#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010351#REF# 6.5.1.5.8
Section 7.4.2.8.1 (Packet Number 40: Track Condition Change of allowed current consumption) shall not apply.
realised by: #REQ-UNISIG-SUB026-007105#REF#

#REQ-UNISIG-SUB026-007105#REF# to.6.5.1.5.8 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010351#REF#
If the information "Track Condition Change of allowed current consumption" (Packet 40) is received with ETCS Language version 1.x,
this information shall be ignored and interpreted as a data consistency error.
#ANALYSE-VALUNISIG-5308#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007131#REF# 6.5.1.5.9
Table 7.4.2.11 (Packet Number 44: Data used by applications outside the ERTMS/ETCS system) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010197#REF#

#REQ-UNISIG-SUB026-010197#REF# to.6.5.1.5.9 #REQ-UNISIG-SUB026-007131#REF#
#REQ-UNISIG-SUB026-007262#REF#
If Packet Number 44 (Data used by applications outside the ERTMS/ETCS system) is received with ETCS Language version 1.x, the following
structure shall be used for decoding:


#ANALYSE-VALUNISIG-5309#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007136#REF# 6.5.1.5.10
Table 7.4.2.13 (Packet Number 51: Axle Load Speed Profile) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010198#REF#

#REQ-UNISIG-SUB026-010198#REF# to.6.5.1.5.10 #REQ-UNISIG-SUB026-007136#REF#
#REQ-UNISIG-SUB026-007262#REF#
If Packet Number 51 (Axle Load Speed Profile) is received with ETCS Language version 1.x, the following structure shall be used for decoding:


#ANALYSE-VALUNISIG-4804#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007137#REF# 6.5.1.5.11
Section 7.4.2.13.1 (Packet Number 52: Permitted Braking Distance Information) shall not apply.
realised by: #REQ-UNISIG-SUB026-010276#REF#

#REQ-UNISIG-SUB026-010276#REF# to.6.5.1.5.11 #REQ-UNISIG-SUB026-007137#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the information "Permitted Braking Distance" (Packet 52) is received with ETCS Language version 1.x, this information shall be
ignored and interpreted as a data consistency error.
#ANALYSE-VALUNISIG-4796#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007141#REF# 6.5.1.5.12
Section 7.4.2.16.1 (Packet Number 64: Inhibition of revocable TSRs from balises in L2/3) shall not apply.
realised by: #REQ-UNISIG-SUB026-010330#REF#

#REQ-UNISIG-SUB026-010330#REF# to.6.5.1.5.12 #REQ-UNISIG-SUB026-007141#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the information "Inhibition of revocable TSRs from balises in L2/3 (packet 64)" (Packet 64) is received with ETCS Language version
1.x, this information shall be ignored and interpreted as a data consistency error.
#ANALYSE-VALUNISIG-4813#REF# FCT The acceptance criteria depending on the used system version are realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007143#REF# 6.5.1.5.13
Section 7.4.2.20.1 (Packet Number 69: Track Condition Station Platforms) shall not apply.
realised by: #REQ-UNISIG-SUB026-010532#REF#

#REQ-UNISIG-SUB026-010532#REF# to.6.5.1.5.13 #REQ-UNISIG-SUB026-007143#REF#
If the information "Track Condition Station Platforms" (Packet 69) is received with ETCS Language version 1.x, this information shall
be ignored and interpreted as a data consistency error.
#ANALYSE-VALUNISIG-5310#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010353#REF# 6.5.1.5.14
Table 7.4.2.21 (Packet Number 70: Route Suitability data) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010354#REF#

#REQ-UNISIG-SUB026-010354#REF# to.6.5.1.5.14 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010353#REF#
If Packet Number 70 (Route Suitability data) is received with ETCS Language version 1.x, the following structure shall be used for decoding:


#ANALYSE-VALUNISIG-5277#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007145#REF# 6.5.1.5.15
Table 7.4.2.23 (Packet Number 72: Packet for sending plain text messages) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010529#REF#

#REQ-UNISIG-SUB026-010529#REF# 6.5.1.5.15 #REQ-UNISIG-SUB026-007145#REF#
#REQ-UNISIG-SUB026-007262#REF#
If Packet Number 72 (Packet for sending plain text messages) is received with ETCS Language version 1.x, the following structure shall be used
for decoding:


#ANALYSE-VALUNISIG-5300#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007148#REF# 6.5.1.5.16
Section 7.4.2.24 (Packet Number 76: Packet for sending fixed text messages) shall not apply.
realised by: #REQ-UNISIG-SUB026-010530#REF#

#REQ-UNISIG-SUB026-010530#REF# 6.5.1.5.16 #REQ-SRS-004528#REF#
#REQ-UNISIG-SUB026-007148#REF#
#REQ-UNISIG-SUB026-007262#REF#
#ANA-UNISIG-Versionmanagement-0010#REF#
If Packet Number 76 (Packet for sending plain text messages) is received with ETCS Language version 1.x, the following structure shall be used
for decoding:


UNISIG clarification:
difference to Subset 26, version 3.3.0 - P76 should be accepted and perform in version 1.x too
#ANALYSE-VALUNISIG-5301#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010518#REF# 6.5.1.5.17
Table 7.4.2.25 (Packet Number 79: Geographical Position Information) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-007134#REF#

#REQ-UNISIG-SUB026-007134#REF# to.6.5.1.5.17 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010518#REF#
If Packet Number 79 (Geographical Position Information) is received with ETCS Language version 1.x, the following structure shall be used for
decoding:


#ANALYSE-VALUNISIG-5311#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007151#REF# 6.5.1.5.18
Table 7.4.2.26 (Packet Number 80: Mode profile) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010200#REF#

#REQ-UNISIG-SUB026-010200#REF# to.6.5.1.5.18 #REQ-UNISIG-SUB026-007151#REF#
#REQ-UNISIG-SUB026-007262#REF#
If Packet Number 80 (Mode profile) is received with ETCS Language version 1.x, the following structure shall be used for decoding:


#ANALYSE-VALUNISIG-4795#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007154#REF# 6.5.1.5.19
Section 7.4.2.26.1 (Packet Number 88: Level Crossing information) shall not apply.
realised by: #REQ-UNISIG-SUB026-010338#REF#

#REQ-UNISIG-SUB026-010338#REF# to.6.5.1.5.19 #REQ-UNISIG-SUB026-007154#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the information "Level Crossing information" (Packet 88) is received with ETCS Language version 1.x, this information shall be
ignored and interpreted as a data consistency error.
#ANALYSE-VALUNISIG-5312#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007156#REF# 6.5.1.5.20
Section 7.4.2.37.1 (Packet Number 143: Session Management with neighbouring Radio Infill Unit) shall not apply.
realised by: #REQ-UNISIG-SUB026-007089#REF#

#REQ-UNISIG-SUB026-007089#REF# to.6.5.1.5.20 #REQ-UNISIG-SUB026-007156#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the information "Session Management with neighbouring Radio Infill Unit" (Packet 143) is received with ETCS Language version 1.x,
this information shall be ignored and interpreted as a data consistency error.
Radio Infill isn't realized. Therefore Information to activation RIU functionality are ignored only.

#REQ-UNISIG-SUB026-010519#REF# 6.5.1.5.21
Added section 7.4.2.37.3 (Packet Number 200: Virtual Balise Cover marker) shall apply:
Packet Number 200: Virtual Balise Cover marker

realised by: #REQ-UNISIG-SUB026-010559#REF#

#REQ-UNISIG-SUB026-010559#REF# to.6.5.1.5.21 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010519#REF#
Packet 200 (Virtual Balise Cover marker) with the following structure shall be accepted only with ETCS Language version 1.x:


#ANALYSE-VALUNISIG-5313#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007158#REF# 6.5.1.5.22
Added section 7.4.2.37.4 (Packet Number 203: National Values for braking curves) shall apply:
Packet Number 203: National Values for braking curves





realised by: #REQ-UNISIG-SUB026-007572:03#REF#

#REQ-UNISIG-SUB026-007572:03#REF# to.6.5.1.5.22 #REQ-UNISIG-SUB026-007070#REF#
#REQ-UNISIG-SUB026-007082#REF#
#REQ-UNISIG-SUB026-007158#REF#
#REQ-UNISIG-SUB026-007262#REF#
Packet 203 (National Values for braking curves) with the following structure shall be accepted only with ETCS Language version 1.x:


Description Downloads a subset of National Values to the train, used for braking curves. This subset is a complement to the National Values
included in packet 3.	      

Transmitted by	Balise, RBC
Transmitted by	Balise, RBC	  

Content Variable	Length	Comment
Content Variable	Length	Comment   

	NID_PACKET	8
NID_PACKET	8		  

	Q_DIR	2
Q_DIR	2		  

	L_PACKET	13
L_PACKET	13		  

	Q_NVGUIPERM	1
Q_NVGUIPERM	1		  

	Q_NVSBFBPERM	1
Q_NVSBFBPERM	1		  

	Q_NVINHSMICPERM 1
Q_NVINHSMICPERM 1		  

	A_NVMAXREDADH1	6
A_NVMAXREDADH1	6		  

	A_NVMAXREDADH2	6
A_NVMAXREDADH2	6		  

	A_NVMAXREDADH3	6
A_NVMAXREDADH3	6		  

	M_NVAVADH	5
M_NVAVADH	5		  

	M_NVEBCL	4
M_NVEBCL	4		  

	Q_NVKINT	1
Q_NVKINT	1		  

	Q_NVKVINTSET	2	Only if Q_NVKINT = 1, Q_NVKVINTSET and the following variables follow
Q_NVKVINTSET	2	Only if Q_NVKINT = 1, Q_NVKVINTSET and the following variables follow	  

		A_NVP12 6	Only if Q_NVKVINTSET = 1
A_NVP12 6	Only if Q_NVKVINTSET = 1	  

		A_NVP23 6	Only if Q_NVKVINTSET = 1
A_NVP23 6	Only if Q_NVKVINTSET = 1	  

	V_NVKVINT	7	= 0km/h
V_NVKVINT	7	= 0km/h   

	M_NVKVINT	7	Valid between  V_NVKVINT and V_NVKVINT(1)
If Q_NVKVINTSET = 1, gives the correction factor if maximum emergency brake deceleration is lower than A_NVP12
M_NVKVINT	7	Valid between  V_NVKVINT and V_NVKVINT(1)
If Q_NVKVINTSET = 1, gives the correction factor if maximum emergency brake deceleration is lower than A_NVP12

M_NVKVINT	7	Only if Q_NVKVINTSET = 1
Valid between V_NVKVINT and V_NVKVINT(1)
Gives the correction factor if maximum emergency brake deceleration is higher than A_NVP23
N_ITER	5
N_ITER	5		  

	V_NVKVINT(n)	7
V_NVKVINT(n)	7		  

	M_NVKVINT(n)	7	Valid between V_NVKVINT(n) and V_NVKVINT(n+1)
If Q_NVKVINTSET = 1, gives the correction factor if maximum emergency brake deceleration is lower than A_NVP12
M_NVKVINT(n)	7	Valid between V_NVKVINT(n) and V_NVKVINT(n+1)
If Q_NVKVINTSET = 1, gives the correction factor if maximum emergency brake deceleration is lower than A_NVP12	  

		M_NVKVINT(n)	7	Only if Q_NVKVINTSET = 1
Valid between V_NVKVINT(n) and V_NVKVINT(n+1)
Gives the correction factor if maximum emergency brake deceleration is higher than A_NVP23
M_NVKVINT(n)	7	Only if Q_NVKVINTSET = 1
Valid between V_NVKVINT(n) and V_NVKVINT(n+1)
Gives the correction factor if maximum emergency brake deceleration is higher than A_NVP23	  

	N_ITER	5
N_ITER	5		  

	Q_NVKVINTSET(k) 2
Q_NVKVINTSET(k) 2		  

		A_NVP12(k)	6	Only if Q_NVKVINTSET(k) = 1
A_NVP12(k)	6	Only if Q_NVKVINTSET(k) = 1	  

		A_NVP23(k)	6	Only if Q_NVKVINTSET(k) = 1
A_NVP23(k)	6	Only if Q_NVKVINTSET(k) = 1	  

	V_NVKVINT(k)	7	= 0km/h
V_NVKVINT(k)	7	= 0km/h

M_NVKVINT(k)	7	Valid between V_NVKVINT(k) and V_NVKVINT(k,1)
If Q_NVKVINTSET(k) = 1, gives the correction factor if maximum emergency brake deceleration is lower than A_NVP12(k)	  

		M_NVKVINT(k)	7	Only if Q_NVKVINTSET(k) = 1
Valid between V_NVKVINT(k) and V_NVKVINT(k,1)
Gives the correction factor if maximum emergency brake deceleration is higher than A_NVP23(k)
M_NVKVINT(k)	7	Only if Q_NVKVINTSET(k) = 1
Valid between V_NVKVINT(k) and V_NVKVINT(k,1)
Gives the correction factor if maximum emergency brake deceleration is higher than A_NVP23(k)	  

	N_ITER(k)	5
N_ITER(k)	5		  

	V_NVKVINT(k,m)	7
V_NVKVINT(k,m)	7		  

	M_NVKVINT(k,m)	7	Valid between V_NVKVINT(k,m) and V_NVKVINT(k,m+1)
If Q_NVKVINTSET(k) = 1, gives the correction factor if maximum emergency brake deceleration is lower than A_NVP12(k)
M_NVKVINT(k,m)	7	Valid between V_NVKVINT(k,m) and V_NVKVINT(k,m+1)
If Q_NVKVINTSET(k) = 1, gives the correction factor if maximum emergency brake deceleration is lower than A_NVP12(k)	  

		M_NVKVINT(k,m)	7	Only if Q_NVKVINTSET(k) = 1
Valid between V_NVKVINT(k,m) and V_NVKVINT(k,m+1)
Gives the correction factor if maximum emergency brake deceleration is higher than A_NVP23(k)
M_NVKVINT(k,m)	7	Only if Q_NVKVINTSET(k) = 1
Valid between V_NVKVINT(k,m) and V_NVKVINT(k,m+1)
Gives the correction factor if maximum emergency brake deceleration is higher than A_NVP23(k)	  

	L_NVKRINT	5	= 0m
L_NVKRINT	5	= 0m	  

	M_NVKRINT	5	Valid between L_NVKRINT and L_NVKRINT(1)
M_NVKRINT	5	Valid between L_NVKRINT and L_NVKRINT(1)	  

	N_ITER	5
N_ITER	5		  

	L_NVKRINT(l)	5
L_NVKRINT(l)	5

M_NVKRINT(l)	5	Valid between L_NVKRINT(l) and L_NVKRINT(l+1)	  

	M_NVKTINT	5
M_NVKTINT	5
#ANALYSE-VALUNISIG-4780#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5615#REF# EET error expectation M_VERSION dependent acceptance of P203

#REQ-UNISIG-SUB026-010355#REF# 6.5.1.5.23
Added section 7.4.2.37.5 (Packet Number 206: Track Condition) shall apply:
Packet Number 206: Track Condition

realised by: #REQ-UNISIG-SUB026-010356:01#REF#

#REQ-UNISIG-SUB026-010356:01#REF# to.6.5.1.5.23 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-007271#REF#
#REQ-UNISIG-SUB026-010355#REF#
Packet 206 (Track Condition) with the following structure shall be accepted only with ETCS Language version 1.x:


realizes also remark [17] from 6.6.3.2.2
#ANALYSE-VALUNISIG-5314#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010520#REF# 6.5.1.5.24
Added section 7.4.2.37.6 (Packet Number 207: Route Suitability Data) shall apply:
Packet Number 207: Route Suitability Data

realised by: #REQ-UNISIG-SUB026-010538#REF#

#REQ-UNISIG-SUB026-010538#REF# to.6.5.1.5.24 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-007271#REF#
#REQ-UNISIG-SUB026-010520#REF#
Packet 207 (Route Suitability) with the following structure shall be accepted onlywith ETCS Language version 1.x:


realizes also remark [18] from 6.6.3.2.2
#ANALYSE-VALUNISIG-7694#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010521#REF# 6.5.1.5.25
Added section 7.4.2.37.7 (Packet Number 239: Track Condition Change of traction system) shall apply:
Packet Number 239: Track Condition Change of traction system

realised by: #REQ-UNISIG-SUB026-010560#REF#

#REQ-UNISIG-SUB026-010560#REF# to.6.5.1.5.25 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-007271#REF#
#REQ-UNISIG-SUB026-010521#REF#
Packet 239 (Track Condition Change of traction system) with the following structure shall be accepted only with ETCS Language version 1.x:


realizes also remark [19] from 6.6.3.2.2
#ANALYSE-VALUNISIG-5315#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007163#REF# 6.5.1.5.26
Table 7.5.1.36 (D_VALIDNV) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010339#REF#

#REQ-UNISIG-SUB026-010339#REF# to.6.5.1.5.26 #REQ-UNISIG-SUB026-007163#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the variable D_VAIDLNV is received with ETCS Language version 1.x the following definition shall be used for decoding:


#ANALYSE-VALUNISIG-4418#REF# FCT The functionality is realised by BC. Verification takes place via BC module test.

#REQ-UNISIG-SUB026-007168#REF# 6.5.1.5.27
Added section 7.5.1.62.2 (M_AXLELOAD) shall apply:
M_AXLELOAD

realised by: #REQ-UNISIG-SUB026-010201#REF#

#REQ-UNISIG-SUB026-010201#REF# to.6.5.1.5.27 #REQ-UNISIG-SUB026-007168#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the variable M_AXLELOAD is received with ETCS Language version 1.x the following definition shall be used for decoding:


#ANALYSE-VALUNISIG-4805#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007170#REF# 6.5.1.5.28
Table 7.5.1.70 (M_MAMODE) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-3340#REF#

#REQ-UNISIG-SUB026-3340#REF# to.6.5.1.5.28 #REQ-UNISIG-SUB026-007170#REF#
If the variable M_MAMODE is received with ETCS Language version 1.x the following definition shall be used for decoding:


#ANALYSE-VALUNISIG-7698#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007173#REF# 6.5.1.5.29
Table 7.5.1.73 (M_MODETEXTDISPLAY) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010531#REF#

#REQ-UNISIG-SUB026-010531#REF# to.6.5.1.5.29 #REQ-UNISIG-SUB026-007173#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the variable  M_MODETEXTDISPLAY is received with ETCS Language version 1.x the following definition shall be used for decoding:


#ANALYSE-VALUNISIG-5302#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010522#REF# 6.5.1.5.30
Table 7.5.1.76 (M_POSITION) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010561#REF#

#REQ-UNISIG-SUB026-010561#REF# to.6.5.1.5.30 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010522#REF#
If the variable M_POSITION is received with ETCS Language version 1.x the following definition shall be used for decoding:


#ANALYSE-VALUNISIG-7699#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007176#REF# 6.5.1.5.31
Table 7.5.1.77 (M_TRACKCOND) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010357#REF#

#REQ-UNISIG-SUB026-010357#REF# to.6.5.1.5.31 #REQ-UNISIG-SUB026-007176#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the variable M_TRACKCOND is received with ETCS Language version 1.x the following definition shall be used for decoding:


#ANALYSE-VALUNISIG-5255#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010358#REF# 6.5.1.5.32
Added section 7.5.1.77.1 (M_TRACKCONDBC) shall apply:
M_TRACKCONDBC

realised by: #REQ-UNISIG-SUB026-010359#REF#

#REQ-UNISIG-SUB026-010359#REF# to.6.5.1.5.32 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010358#REF#
M_TRACKCONDBC

can only received with ETCS language 1.x in packet 206
#ANALYSE-VALUNISIG-5256#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007179#REF# 6.5.1.5.34
Table 7.5.1.83 (NC_DIFF) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010400#REF#

#REQ-UNISIG-SUB026-010400#REF# to.6.5.1.5.34 #REQ-UNISIG-SUB026-007179#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the variable NC_DIFF is received with ETCS Language version 1.x the following definition shall be used for decoding:


#ANALYSE-VALUNISIG-5316#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007182#REF# 6.5.1.5.35
Table 7.5.1.138 (Q_TEXTCONFIRM) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010203#REF#

#REQ-UNISIG-SUB026-010203#REF# to.6.5.1.5.35 #REQ-UNISIG-SUB026-007182#REF#
#REQ-UNISIG-SUB026-007262#REF#
If the variable Q_TEXTCONFIRM is received with ETCS Language version 1.x the following definition shall be used for decoding:


Rel. 8.0: REQ-UNISIG-SUB026-3344 has to be renamed
#ANALYSE-VALUNISIG-4779#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010363#REF# 6.5.1.6.2
Clause 8.4.1.4.8 shall be replaced with “Exception 8: A message transmitted by a balise group can contain several packets 200 (Virtual Balise
Cover marker).”
realised by: #REQ-UNISIG-SUB026-010565#REF#

#REQ-UNISIG-SUB026-010364#REF# 6.5.1.6.3
The table under clause 8.4.2.1 shall be replaced with:

VBC function is not realized

=> no driver input, no P6 => a VBC doesn't exists
realised by: #REQ-UNISIG-SUB026-010569#REF#

#REQ-UNISIG-SUB026-010569#REF# to.6.5.1.6.3 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010364#REF#
If a balise telegram is received with ETCS Language version 1.x, packet 0 shall be replaced by packet 200 in the general format balise telegram.
VBC function is not realized

=> P200 is to be ignored
=> the correct position should not be checked.

#REQ-UNISIG-SUB026-007191#REF# 6.5.1.6.5
The table under clause 8.4.4.4.1 shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010579#REF#
realised by: #REQ-UNISIG-SUB026-010582#REF#
realised by: #REQ-UNISIG-SUB026-010206#REF#
realised by: #REQ-UNISIG-SUB026-010580#REF#
realised by: #REQ-UNISIG-SUB026-010581#REF#
realised by: #REQ-UNISIG-SUB026-010571#REF#
realised by: #REQ-UNISIG-SUB026-010572#REF#
realised by: #REQ-UNISIG-SUB026-010574#REF#

#REQ-UNISIG-SUB026-010579#REF# to.6.5.1.6.5 #REQ-UNISIG-SUB026-007191#REF#
If a general message is received from RIU with ETCS Language version 1.x, obu shall accept only the packets 45 and 254 as optional packets.

#REQ-UNISIG-SUB026-010582#REF# to.6.5.1.6.5 #REQ-UNISIG-SUB026-007191#REF#
If a Message "Request To Shorten MA" is received from RBC with ETCS Language version 1.x, obu shall accept only packet 80 as optional
packet.
#ANALYSE-VALUNISIG-5326#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010206#REF# to.6.5.1.6.5 #REQ-UNISIG-SUB026-007191#REF#
If a Message "SH authorised" is received from RBC with ETCS Language version 1.x, obu shall accept only packet 49 and packets, which
are defined in the list of common optional packets, as optional packets.
UNISIG clarification: the same rule as baseline 3 is valid for packets. P49 is accepted  only together with the acceptance of the message. The
other packets are evaluated independent of the message.
#ANALYSE-VALUNISIG-5317#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010580#REF# to.6.5.1.6.5 #REQ-UNISIG-SUB026-007191#REF#
If a Message "MA with Shifted Location Reference" is received from RBC with ETCS Language version 1.x, obu shall accept only the
packets 21, 27,  80 and packets, which are defined in the list of common optional packets, as optional packets.
#ANALYSE-VALUNISIG-5327#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010581#REF# to.6.5.1.6.5 #REQ-UNISIG-SUB026-007191#REF#
If a Message "Infill MA" is received from RIU with ETCS Language version 1.x, obu shall accept only packets 5, 21, 27, 39, 41, 44, 51,
65, 66, 68, 70, 71, 80, 138, 139, 206, 207, 239 as optional packets.
Radio Infill isn't realized.

#REQ-UNISIG-SUB026-007194#REF# 6.5.1.6.6
The table under clause 8.4.4.4.1.1 shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010366#REF#

#REQ-UNISIG-SUB026-010366#REF# to.6.5.1.6.6 #REQ-UNISIG-SUB026-007194#REF#
#ANA-UNISIG-Versionmanagement-0010#REF#
If the ETCS Language version 1.x is used in communication with a RBC, the following packets shall be accepted as common optional packets in the
messages from the RBC:
3, 5, 39, 51, 41, 42, 44, 45, 57, 58, 65, 66, 68, 70, 71, 72, 76, 79, 131, 138, 139, 140, 203, 206, 207, 239.
UNISIG clarification: P76 is also accepted as optional packet in version 1
#ANALYSE-VALUNISIG-5318#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007196#REF# 6.5.1.6.7
Table 8.7.6 (Message 15: Conditional Emergency Stop) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010204#REF#

#REQ-UNISIG-SUB026-010204#REF# to.6.5.1.6.7 #REQ-UNISIG-SUB026-007196#REF#
If the ETCS Language version 1.x is used in communication with a RBC, message 15 (Conditional Emergency Stop) shall be accepted with the
following structure:

#ANALYSE-VALUNISIG-4785#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007200#REF# 6.5.1.6.8
Table 8.7.14 (Message 34: Track Ahead Free Request) shall be replaced with:

realised by: #REQ-UNISIG-SUB026-010205#REF#

#REQ-UNISIG-SUB026-010205#REF# to.6.5.1.6.8 #REQ-UNISIG-SUB026-007200#REF#
If the ETCS Language version 1.x is used in communication with a RBC, message 34 (Track Ahead Free Request) shall be accepted with the following
structure:

#ANALYSE-VALUNISIG-4782#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007213#REF# 6.5.1.7.5
A balise group or RBC message including the packet 203 shall also include the packet 3 (i.e. in a message, the packet 203 cannot be transmitted
without the packet 3).
realised by: #REQ-UNISIG-SUB026-008014#REF#

#REQ-UNISIG-SUB026-008014#REF# to.6.5.1.7.5 #REQ-UNISIG-SUB026-007213#REF#
#REQ-UNISIG-SUB026-007262#REF#
Packet 203 shall be accepted only together with packet 3 in the same message.
#TEST-VAL-SUB026-5619#REF# FCT basic function P203 - valid packet structure

Chapter 6.6

TEST APPROACH:
The translation rules for the interaction with older system versions are centrally realised by the software module packet handler (PH).
Verification takes place via PH module verification.
The quality of the module tests is ensured by review of the module test specification and test implementation as part of the module review. The
result of the review is documented in /ESBO_UUE/ --> reference ID ESBO_VerBer.

The function is hence not tested thoroughly by VER/VAL test cases but by example only.
		
#REQ-UNISIG-SUB026-007243#REF# 6.6.2.1.1
Clause 3.12.3.4.7.2 shall be replaced with: “If the driver acknowledges before the end condition is fulfilled, the on-board equipment shall
consider the driver acknowledgement as always ending the text display, regardless of the end condition defined in 3.12.3.4.3.1”.
realised by: #REQ-UNISIG-SUB026-007245#REF#

#REQ-UNISIG-SUB026-007245#REF# to.6.6.2.1.1 #REQ-UNISIG-SUB026-007243#REF#
If the current operated system version 1.x and the driver acknowledges a text message before the end condition is fulfilled, the on-board
equipment shall consider the driver acknowledgement as always ending the text display, regardless the trackside input for this text message.
#TEST-VAL-SUB026-7793#REF# FCT basic function Text msg acknowledged by driver ends the text display, depending on system version
#TEST-VAL-SUB026-7794#REF# EET error expectation Text msg acknowledged by driver ends the text display, depending on system version

#REQ-UNISIG-SUB026-007262#REF# 6.6.3.1.1
For information received from trackside, the message consistency check shall be achieved taking into account the exceptions to chapters 7 and 8,
as described in sections 6.5.1.5 and 6.5.1.6.
realised by: #REQ-UNISIG-SUB026-010566#REF#
realised by: #REQ-UNISIG-SUB026-0332:01#REF#
realised by: #REQ-UNISIG-SUB026-010337#REF#
realised by: #REQ-UNISIG-SUB026-010196#REF#
realised by: #REQ-UNISIG-SUB026-010352#REF#
realised by: #REQ-UNISIG-SUB026-007105#REF#
realised by: #REQ-UNISIG-SUB026-010197#REF#
realised by: #REQ-UNISIG-SUB026-010198#REF#
realised by: #REQ-UNISIG-SUB026-010276#REF#
realised by: #REQ-UNISIG-SUB026-010330#REF#
realised by: #REQ-UNISIG-SUB026-010354#REF#
realised by: #REQ-UNISIG-SUB026-010529#REF#
realised by: #REQ-UNISIG-SUB026-010530#REF#
realised by: #REQ-UNISIG-SUB026-007134#REF#
realised by: #REQ-UNISIG-SUB026-010200#REF#
realised by: #REQ-UNISIG-SUB026-010338#REF#
realised by: #REQ-UNISIG-SUB026-007089#REF#
realised by: #REQ-UNISIG-SUB026-010559#REF#
realised by: #REQ-UNISIG-SUB026-007572:03#REF#
realised by: #REQ-UNISIG-SUB026-010356:01#REF#
realised by: #REQ-UNISIG-SUB026-010538#REF#
realised by: #REQ-UNISIG-SUB026-010560#REF#
realised by: #REQ-UNISIG-SUB026-010339#REF#
realised by: #REQ-UNISIG-SUB026-010201#REF#
realised by: #REQ-UNISIG-SUB026-010531#REF#
realised by: #REQ-UNISIG-SUB026-010561#REF#
realised by: #REQ-UNISIG-SUB026-010357#REF#
realised by: #REQ-UNISIG-SUB026-010359#REF#
realised by: #REQ-UNISIG-SUB026-010400#REF#
realised by: #REQ-UNISIG-SUB026-010203#REF#
realised by: #REQ-UNISIG-SUB026-010569#REF#
realised by: #REQ-UNISIG-SUB026-008014#REF#
realised by: #REQ-UNISIG-SUB026-010565#REF#
realised by: #REQ-UNISIG-SUB026-010570#REF#

#REQ-UNISIG-SUB026-007270#REF# 6.6.3.2.2
When a level transition or an RBC/RBC handover is announced, the information stored on-board in the transition buffer shall be translated
according to system version operated on-board at the time the information is released from the transition buffer (i.e. the system version
operated by the trackside infrastructure, towards which the train is running).
TEST APPROACH:
The following aspects have been identified:
1) RBC/RBC handover
2) level transition
Only the translation of a P3 coded according to M_VERSION=0x1X depends on the operated system version. The information 'System Version order' is
not buffered. The requirement is hence only relevant for the transition from a system version 2 area to a system version 1. A switch from a
higher to lower system version is possible via 'System Version order' from BG or based on RBC system version only.
The aspect 2 has no functional relevance the verification is hence omitted. 
#TEST-VAL-SUB026-7122#REF# FCT 1 Information stored in the transition buffer translated according to system version operated when information is released from buffer

#REQ-UNISIG-SUB026-007271#REF# 6.6.3.2.3
Depending on the packet, the action can be:
a)	data is unchanged,
b)	data is rejected,
c)	data is translated,
d)	not relevant







[1a] The National Values Q_NVLOCACC, V_NVLIMSUPERV (introduced in system version number X = 2) shall be set to their respective default value
[1b] The National Values Q_NVLOCACC, V_NVLIMSUPERV (introduced in system version number X = 2), if already stored on-board and applicable, shall
not be affected by the content of the packet 3 (i.e. if these National Values were already applicable and 2nd bullet of clause 3.18.2.5 is not
applied, they shall remain applicable with their country identifier(s) previously stored).
[2] If the packet 203 is not received in the same message, the National Values for braking curves Q_NVGUIPERM, Q_NVSBFBPERM, Q_NVINHSMICPERM,
M_NVAVADH, M_NVEBCL, A_NVP12, A_NVP23, V_NVKVINT, M_NVKVINT, L_NVKRINT, M_NVKRINT, M_NVKTINT, A_NVMAXREDADH1, A_NVMAXREDADH2, A_NVMAXREDADH3
(introduced in system version number X.Y = 1.1), if already stored on-board and applicable, shall not be affected by the content of the packet 3
(i.e. if the National Values for braking curves were already applicable and 2nd bullet of clause 3.18.2.5 is not applied, they shall remain
applicable with their country identifier(s) previously stored).
[3] Exception: if N_ITER (following Q_FRONT) ¹ 0, the variables Q_DIFF, NC_CDDIFF (introduced in system version number X = 2) and NC_DIFF (as
specified in system version number X = 2) shall be set according to the following table:




[4] If Q_TRACKINIT = 1, D_TRACKINIT (introduced in system version number X = 2) shall be set to 0
[5] The variable M_AXLELOADCAT (introduced in system version number X = 2) shall be set according to the following table:



[6] Exception: if Q_TEXTCONFIRM ¹ 0, then Q_CONFTEXTDISPLAY and Q_TEXTREPORT (introduced in system version number X = 2) shall be set to 0
[7] The variable Q_MAMODE (introduced in system version number X = 2) shall be set to 1
[8] Exception: If the packet 206 is not received in the same message and if M_TRACKCOND = 1 or 2, then M_TRACKCOND (modified in system version
number X = 2) shall be set to 0
[9] Exception: If the packet 206 is received in the same message, the ERTMS/ETCS on-board shall ignore the packet 68.
[10] Exception: if M_LOC = 011, the packet shall be rejected
[11] Exception: If the packet 207 is not received in the same message and if Q_TRACKINIT = 1, the packet shall not be rejected.
[12] Exception: If the packet 207 is not received in the same message and if the value “10” of the variable Q_SUITABILITY is used with
M_TRACTION equal to one of the values that are listed in the translation table [13], the variables M_VOLTAGE and NID_CTRACTION (introduced in
system version X.Y = 1.1) shall be set according to the translation table [13]. The ERTMS/ETCS on-board shall ignore any other route suitability
information not related to the traction system
[13] If the packet 239 is received in the same message or if M_TRACTION is not equal to one of the values that are listed here below, the
ERTMS/ETCS on-board shall ignore the packet 39. If the packet 239 is not received in the same message and if M_TRACTION is equal to one of the
values that are listed here below the variables M_VOLTAGE and NID_CTRACTION shall be set according to the following table:




[14] Exception: if M_POSITION = 1’048’575, then M_POSITION (modified in system version number X = 2) shall be set to 16’777’215
[15] The variable NID_PACKET shall be set to 0 and both the variables Q_DIR and L_PACKET shall be deleted
[16] The National Values included in the packet 203 shall be appended to the packet 3 received in the same message, in order to form a single
set of National Values, to which apply the distance to start of validity and the list of national area identifiers given in the packet 3.
[17] The variable NID_PACKET shall be set to 68.
[18] The variable NID_PACKET shall be set to 70
[19] The variable NID_PACKET shall be set to 39

--- FINALISED ---
The remarks [17], [18] and [19] are realized with a separate definition for the structure of packet 206, 207 and 239.
realised by: #REQ-UNISIG-SUB026-010356:01#REF#
realised by: #REQ-UNISIG-SUB026-010538#REF#
realised by: #REQ-UNISIG-SUB026-010560#REF#
realised by: #REQ-UNISIG-SUB026-010210:01#REF#
realised by: #REQ-UNISIG-SUB026-010340#REF#
realised by: #REQ-UNISIG-SUB026-008012:01#REF#
realised by: #REQ-UNISIG-SUB026-7272#REF#
realised by: #REQ-UNISIG-SUB026-010215#REF#
realised by: #REQ-UNISIG-SUB026-010216#REF#
realised by: #REQ-UNISIG-SUB026-010217#REF#
realised by: #REQ-UNISIG-SUB026-010583#REF#
realised by: #REQ-UNISIG-SUB026-010398#REF#
realised by: #REQ-UNISIG-SUB026-010399#REF#
realised by: #REQ-UNISIG-SUB026-010310#REF#
realised by: #REQ-UNISIG-SUB026-010362#REF#
realised by: #REQ-UNISIG-SUB026-010361#REF#
realised by: #REQ-UNISIG-SUB026-010472:01#REF#
realised by: #REQ-UNISIG-SUB026-010473#REF#
realised by: #REQ-UNISIG-SUB026-010558#REF#
realised by: #REQ-UNISIG-SUB026-010567#REF#
realised by: #REQ-UNISIG-SUB026-010585#REF#
realised by: #REQ-UNISIG-SUB026-010584#REF#

#REQ-UNISIG-SUB026-010210:01#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 3 (National Values) with ETCS Language version 1.x and the operated system version is 1.x, the National Values
Q_NVLOCACC, V_NVLIMSUPERV shall be set to their respective default value.
6.6.3.2.3 - remark[1a]
#TEST-VAL-SUB026-3B88#REF# FCT basic function Q_NVLOCACC and V_NVLIMSUPERV when receiving P3 version 1.X and operated system version is 1.X

#REQ-UNISIG-SUB026-010340#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 3 (National Values) with ETCS Language version 1.x and the operated system version is 2.x or higher, the National
Values Q_NVLOCACC, V_NVLIMSUPERV, if already stored on-board and applicable, shall not be affected by the content of the packet 3 (i.e. if these
National Values were already applicable and 2nd bullet of clause 3.18.2.5 is not applied, they shall remain applicable with their country
identifier(s) previously stored).
6.6.3.2.3 - remark[1b]
#TEST-VAL-SUB026-5840#REF# FCT basic function Q_NVLOCACC and V_NVLIMSUPERV when receiving P3 M_VERSION 0x10

#REQ-UNISIG-SUB026-008012:01#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If a packet 3 is received in ETCS Language version 1.x without P203 in the same message,  the National Values for braking curves Q_NVGUIPERM,
Q_NVSBFBPERM, Q_NVINHSMICPERM, M_NVAVADH, M_NVEBCL, A_NVP12, A_NVP23, V_NVKVINT, M_NVKVINT, L_NVKRINT, M_NVKRINT, M_NVKTINT, A_NVMAXREDADH1,
A_NVMAXREDADH2, A_NVMAXREDADH3, if already stored on-board and applicable, shall not be affected by the content of the packet 3.

The National Values for braking curves shall remain applicable with their country identifier(s) previously stored.
6.6.3.2.3 - remark[2]
#TEST-VAL-SUB026-5656#REF# FCT basic function Validity of P203 information after receiving new NV without P203

#REQ-UNISIG-SUB026-7272#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
The National Values included in the packet 203 shall be appended to the packet 3 received in the same message, in order to form a single set of
National Values, to which apply the distance to start of validity and the list of national area identifiers given in the packet 3.
6.6.3.2.3 - remark[16]
#TEST-VAL-SUB026-5619#REF# FCT basic function P203 - valid packet structure
#TEST-VAL-SUB026-5657#REF# EET error expectation Discrepancy between BG NID_C and P3/P203 NID_C

#REQ-UNISIG-SUB026-010215#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 27 (Static Speed Profile) with ETCS Language version 1.x, the following mapping rule shall be realized:
If N_ITER (following Q_FRONT) > 0, the variables Q_DIFF, NC_CDDIFF (introduced in system version number X = 2) and NC_DIFF (as specified in
system version number X = 2) shall be set according to the following table:

6.6.3.2.3 - remark[3]
#ANALYSE-VALUNISIG-4787#REF# FCT The translation is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5879#REF# ECT basic function Translation of system version 1 NC_DIFF

#REQ-UNISIG-SUB026-010216#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 51 (Axle Load Speed Profile) with ETCS Language version 1.x, the following mapping rule shall be realized:
If Q_TRACKINIT = 1, D_TRACKINIT (introduced in system version number X = 2) shall be set to 0.
6.6.3.2.3 - remark[4]
#ANALYSE-VALUNISIG-5345#REF# FCT The translation rules for the interaction with older system versions are centrally realised by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010217#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a information with ETCS Language version 1.x, which the variable M_AXLELOAD contains (i.e. Axle Load Speed Profile or Route
Suiteability), the following mapping rule shall be realized:
The variable M_AXLELOADCAT (introduced in system version number X = 2) shall be set according to the following table:

6.6.3.2.3 - remark[5]
#ANALYSE-VALUNISIG-5346#REF# FCT The translation rules for the interaction with older system versions are centrally realised by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010583#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 58 (position report parameters) with ETCS Language version 1.x and M_LOC=3 (binär 011)is set, the information shall be
ignored but this shall be not interpreted as data inconsistency.

A basic diagnostic event shall be tirggered in this case.
6.6.3.2.3 - remark[10]
#ANALYSE-VALUNISIG-7450#REF# FCT The conversion rule is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010398#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 72 (plain text message) with ETCS Language version 1.x, the following mapping rule shall be realized:
if Q_TEXTCONFIRM<>0, then Q_CONFTEXTDISPLAY and Q_TEXTREPORT (introduced in system version number X = 2) shall be set to 0.
6.6.3.2.3 - remark[6]
TEST APPROACH:
The following aspects have been identified:
1) Q_TEXTCONFIRM = 1
2) Q_TEXTCONFIRM = 2
3) Q_TEXTCONFIRM = 3 (spare value for M_VERSION=0x1X)
#ANALYSE-VALUNISIG-5303#REF# FCT The conversion rule is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7963#REF# FCT 1, 2 Q_TEXTCONFIRM different than 0 sent from trackside operating version 1
#TEST-VAL-SUB026-5837#REF# FCT 3 Reception of Q_TEXTCONFIRM 3 from system version 1 device

#REQ-UNISIG-SUB026-010399#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
#ANA-UNISIG-Versionmanagement-0010#REF#
If obu receives a packet 76 (fixed text message) with ETCS Language version 1.x, the following mapping rule shall be realized:
if Q_TEXTCONFIRM<>0, then Q_CONFTEXTDISPLAY and Q_TEXTREPORT (introduced in system version number X = 2) shall be set to 0.
difference to Subset 26, version 3.3.0 - see analysis
TEST APPROACH:
The following aspects have been identified:
1) Q_TEXTCONFIRM = 1
2) Q_TEXTCONFIRM = 2
3) Q_TEXTCONFIRM = 3
#ANALYSE-VALUNISIG-5304#REF# FCT The conversion rule is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7962#REF# FCT 1, 2, 3 Q_TEXTCONFIRM different than 0 sent in P76 from trackside operating version 1

#REQ-UNISIG-SUB026-010310#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 80 (mode profile) with ETCS Language version 1.x, the following mapping rule shall be realized:
The variable Q_MAMODE (introduced in system version number X = 2) shall be set to 1.
6.6.3.2.3 - remark[7]
#ANALYSE-VALUNISIG-7451#REF# FCT The conversion rule is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010362#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 68 (Track Conditions) with ETCS Language version 1.x and a packet 206 is received in the same message, the packet 68
shall be ignored.
6.6.3.2.3 - remark[9] 

Hint:  The packets can be placed in any order.
#ANALYSE-VALUNISIG-5257#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7048#REF# EET error expectation Reception of P68 and P206 within same message

#REQ-UNISIG-SUB026-010361#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 68 (Track Conditions) with ETCS Language version 1.x, the following mapping rule shall be realized:
If M_TRACKCOND = 1 or 2,  M_TRACKCOND (modified in system version number X = 2) shall be set to 0.
6.6.3.2.3 - remark[8]
#ANALYSE-VALUNISIG-5258#REF# FCT The parameter value mapping table system version 1 to system version 2 is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010472:01#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 70 (RouteSuitability) with ETCS Language version 1.x and a packet 207 is received in the same message, the packet 70
shall be ignored.
6.6.3.2.3 - remark[11][12]
#ANALYSE-VALUNISIG-7700#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7706#REF# EET error expectation Handling of P70 v1.x with and without P207

#REQ-UNISIG-SUB026-010473#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a information with ETCS Language version 1.x, which the variable M_TRACTION contains (i.e. Route Suiteability with
Q_SUITABILITY=10 or Traction Power information), the following mapping rule shall be realized:
M_VOLTAGE and NID_CTRACTION (introduced in system version number X = 2) shall be set according to the following table, if M_TRACTION is equal to
one of the values that are listed:


If M_TRACTION is not equal to one of the values that are listed, the information shall be ignored.
This means in case of Route Suitability, that this profile element is handled according to #REQ-UNISIG-SUB026-010558#REF#.
6.6.3.2.3 - remark[13]
#ANALYSE-VALUNISIG-5278#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010558#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 70 (RouteSuitability) with ETCS Language version 1.x and Q_SUITABILITY<>10 (loading gauge or axle load), this
route suitability information shall be ignored but the distance shall be considered for the next route suitability, if available.
6.6.3.2.3 - remark[12] - last sentences 

UNISIG clarification:
a RS unequal Traction System is ignored, but the defined distance is considered for the next RS.
#TEST-VAL-SUB026-7707#REF# FCT basic function Handling of P70 (Route Suitability data) with Q_SUITABILITY<>'10'

#REQ-UNISIG-SUB026-010567#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 39 (Traction System) with ETCS Language version 1.x and a packet 239 is received in the same message, the packet 39
shall be ignored.
6.6.3.2.3 - remark[13]
#ANALYSE-VALUNISIG-7701#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7910#REF# EET error expectation Packet 239 (Track Condition Change of traction system) accepted only with ETCS Language version 1.x
#TEST-VAL-SUB026-7911#REF# EET error expectation Receive P239 and P39 in the same message

#REQ-UNISIG-SUB026-010585#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 79 (Geographicale Position Report) with ETCS Language version 1.x, the value M_Position=1'048'575, if used,
shall be set to 16'777'215.
6.6.3.2.3 - remark[14]
#ANALYSE-VALUNISIG-5344#REF# FCT The conversion rule is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7476#REF# EET error expectation Variable test M_POSITION

#REQ-UNISIG-SUB026-010584#REF# to.6.6.3.2.3 #REQ-UNISIG-SUB026-007271#REF#
If obu receives a packet 200 (Virtual Balise Cover) with ETCS Language version 1.x, the information shall be mapped to the structure of packet
0.
The values Q_DIR and L_PACKET shall not be evaluated and shall be ignored by the mapping.
6.6.3.2.3 - remark[15]

VBC function is not realized

#REQ-UNISIG-SUB026-007301#REF# 6.6.3.3.2
Depending on the received message, the action can be:
a)	data is unchanged,
b)	data is rejected
c)	data is translated,
d)	not relevant





[1] Variable D_REF (introduced in system version number X = 2) shall be set to 0
realised by: #REQ-UNISIG-SUB026-010207#REF#
realised by: #REQ-UNISIG-SUB026-010208#REF#

#REQ-UNISIG-SUB026-010207#REF# to.6.6.3.3.2 #REQ-UNISIG-SUB026-007301#REF#
If the obu receives the message 15 (Conditional Emergency Stop) with ETCS Language version 1.x , the value of D_REF shall be set to 0.
#TEST-VAL-SUB026-5865#REF# FCT basic function Q_EMERGENCYSTOP transmitted to RBC with M_VERSION=0x10

#REQ-UNISIG-SUB026-010208#REF# to.6.6.3.3.2 #REQ-UNISIG-SUB026-007301#REF#
If the obu receives the message 34 (Track Ahead Free Request) with ETCS Language version 1.x , the value of D_REF shall be set to 0.
#TEST-VAL-SUB026-5847#REF# FCT basic function D_REF for M34 M_VERSION 0x10

#REQ-UNISIG-SUB026-007308#REF# 6.6.3.4.2
Clause 3.18.4.5.4 shall be replaced with: “Only if valid Train Data is available: following any entry/modification of the train running number
when a communication session is already established or following the successful establishment of a communication session when valid train
running number is already available, the ERTMS/ETCS on-board equipment shall send the Train Data to the RBC.
realised by: #REQ-UNISIG-SUB026-010452#REF#

#REQ-UNISIG-SUB026-010452#REF# to.6.6.3.4.2 #REQ-UNISIG-SUB026-007308#REF#
If the ETCS Language version 1.x is used with the current supervising  RBC and a changed train running number should be transmitted to this RBC
(see 3.18.4.5.4 and 3.18.4.5.4.1), the obu shall send the changed train running number together with the train data in packet 11 (Validated
train data) in ETCS Language version 1.x and only if the train data are valid.
#TEST-VAL-SUB026-7717#REF# FCT basic function Train Running Number sent to RBC when operated system version is 1.0 and 2.0
#TEST-VAL-SUB026-7718#REF# EET error expectation Valid Train Running Number (from TIU input) sent to RBC when operated system version is 1.0 and 2.0

#REQ-UNISIG-SUB026-010555#REF# to.6.6.3.4.2
If  the ETCS Language version 1.x is used, it shall be ensured that only one packet 11 is sended after a successful establishement of
communication session or during the SoM-Procedure.
UNISIG clarification:
In ETCS Language version 1.x the train running number is sended together with the train data in P11. Therefore is it possible, that two P11 are
sended after a successful session establishment (one with valid train data and one with valid train running number)
TEST APPROACH:
The following aspects have been identified:
1) successful establishment of communication session (not during SoM)
2) during SoM procedure
#TEST-VAL-SUB026-3023#REF# FCT 1 Order to establish communication session with given RBC ID and phone nr
#TEST-VAL-SUB026-7629#REF# FCT 2 Only one P11 sent during SoM when ETCS Language version 1.x is used

#REQ-UNISIG-SUB026-007310#REF# 6.6.3.4.3
Clause 3.18.4.5.4.1 shall be replaced with: “Exception: if the train running number has been received from the RBC, the Train Data shall not be
sent back to the RBC by the ERTMS/ETCS on-board equipment.
realised by: #REQ-UNISIG-SUB026-004186#REF#

#REQ-UNISIG-SUB026-002600#REF# 6.6.3.4.5
Depending on the transmitted message/packet, the action can be:
a)	data is unchanged,
b)	data is deleted (i.e. it is not sent to the receiver)
c)	data is translated,
d)	not relevant (i.e. no corresponding requirement to trigger the sending is applicable)





[1] Exception: if M_MODE (X=2) = 15 (PS), then M_MODE (X=1) = 3 (SH)
Note: if M_MODE (X=2) = 12 (LS), no translation is effected and the value 12 will be understood by RBC X = 1 as SE mode
[2] Exceptions: if M_ERROR (X=2) = 6, then M_ERROR (X=1) = 7; if M_ERROR (X=2) = 7 or 8, then the packet shall be deleted
[3] the packet 11 shall be translated as follows:




[3a] NID_OPERATIONAL shall be set to the value stored on-board
[3b] NC_TRAIN shall be set according to the following table:



[3c] M_LOADINGGAUGE shall be set to 0
[3d] M_AXLELOAD shall be set according to the following table:



[3e] N_ITER shall be set to 0
[4] Q_MARQSTREASON shall be replaced with Q_TRACKDEL (1 bit) as follows: if Q_MARQSTREASON = x1xxx, Q_TRACKDEL shall be set to 1, otherwise
Q_TRACKDEL shall be set to 0
[5] The variable Q_EMERGENCYSTOP (modified in system version number X = 2) shall be set according to the following table:


realised by: #REQ-UNISIG-SUB026-010586#REF#
realised by: #REQ-UNISIG-SUB026-010212#REF#
realised by: #REQ-UNISIG-SUB026-010218#REF#
realised by: #REQ-UNISIG-SUB026-010219#REF#
realised by: #REQ-UNISIG-SUB026-010220#REF#
realised by: #REQ-UNISIG-SUB026-010221#REF#
realised by: #REQ-UNISIG-SUB026-010252#REF#
realised by: #REQ-UNISIG-SUB026-010593#REF#
realised by: #REQ-UNISIG-SUB026-010223#REF#

#REQ-UNISIG-SUB026-010586#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
#ANA-UNISIG-ErrorReport-0002:02#REF#
If obu should send a position report to the RBC with ETCS Language version 1.x, the following mapping shall be considered:
- for Mode Passive Shunting M_MODE=3 (SH) is used

Note: for mode Limited Supervision no translation is effected. Value 12 is used also with ETCS Language version 1.x.
6.6.3.4.5 remark[1]
#ANALYSE-VALUNISIG-7452#REF# FCT The conversion rule is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010212#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
#ANA-UNISIG-ErrorReport-0002:02#REF#
If obu should send an error report (packet 4) to the RBC with ETCS Language version 1.x, the following mapping shall be considered:
- for a safety critical error M_ERROR=7 is used
- for a double linking error M_ERROR=0 is used
- for a double repositioning error no error report is sended.
6.6.3.4.5 remark[2]

UNISIG clarification:
the regulation for doule linking error is not confirmed with the origin - see analysis
#ANALYSE-VALUNISIG-4798#REF# FCT The parameter value mapping table system version 2 to system version 1 is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-3763#REF# EET error expectation OBU informs RBC about detected linking RAMS error (system version X=1)

#REQ-UNISIG-SUB026-010218#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
If obu should send train data (packet 11) to the
RBC with ETCS Language version 1.x, the following packet structure shall be used:

Note: The translation for the particular variables is defined separate.
6.6.3.4.5 remark[3]
#ANALYSE-VALUNISIG-5280#REF# FCT The packet structure/coding and dependency on the system version is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010503#REF# to.6.6.3.4.5
The train data shall be send only to the RBC with ETCS Language version 1.x, if both train data and the train running number are valid.
UNISIG clarification:
is possible in SoM, that train data are validated at first and than the train running number
#TEST-VAL-SUB026-4H94#REF# FCT basic function OBU v2.0 sends Train Data (P11) to RBC with system version 1.x
#TEST-VAL-SUB026-7948#REF# FCT error expectation Train data to RBC v.1.0 at SoM (TRN entered in S1)

#REQ-UNISIG-SUB026-010219#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
If obu should send train data (packet 11) to the RBC with ETCS Language version 1.x, the following mappings shall be considered:
-	NID_OPERATIONAL shall be set to the value stored on-board
-	M_LOADINGGAUGE shall be set to 0
-	N_ITER for M_TRACTION shall be set to 0
6.6.3.4.5 remark [3a, 3c, 3e]
#TEST-VAL-SUB026-4H94#REF# FCT basic function OBU v2.0 sends Train Data (P11) to RBC with system version 1.x

#REQ-UNISIG-SUB026-010591#REF# to.6.6.3.4.5
If the variable NC_TRAIN should be used with ETCS Language version 1.x the following definition shall be used for encoding:

UNISIG clarification:
the 2.3.0d definition of varaiable NC_TRAIN is necessary to sending the train data.  

the new definition of NC_TRAIN cannot used, because spare values are defined from bit position 5.
#ANALYSE-VALUNISIG-5328#REF# FCT The packet structure/coding and acceptance depending on ETCS Language version as well as transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010220#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
If obu should send train data (packet 11) to the RBC with ETCS Language version 1.x, NC_TRAIN shall be set according to the following table:

6.6.3.4.5
remark [3b]
#ANALYSE-VALUNISIG-7695#REF# FCT The parameter value mapping table system version 2 to system version 1 is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4H94#REF# EET error expectation OBU v2.0 sends Train Data (P11) to RBC with system version 1.x

#REQ-UNISIG-SUB026-010221#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
If obu should send train data (packet 11) to the RBC with ETCS Language version 1.x, M_AXLELOAD shall be set according to the following table:

6.6.3.4.5
remark [3d]
#ANALYSE-VALUNISIG-7696#REF# FCT The parameter value mapping table system version 1 to system version 2 is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-4H94#REF# EET error expectation OBU v2.0 sends Train Data (P11) to RBC with system version 1.x

#REQ-UNISIG-SUB026-010252#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
If obu should send a MA Request (message 132) to the RBC with ETCS Language version 1.x, Q_MARQSTREASON shall be replaced with Q_TRACKDEL as
follows:
if Q_MARQSTREASON = x1xxx
Q_TRACKDEL shall be set to 1,
otherwise
Q_TRACKDEL shall be set to 0.
#ANALYSE-VALUNISIG-4799#REF# FCT The parameter value mapping table system version 2 to system version 1 is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010593#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
If the variable Q_TRACKDEL is used with ETCS Language version 1.x the following definition shall be used for encoding:

#ANALYSE-VALUNISIG-5329#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010223#REF# to.6.6.3.4.5 #REQ-UNISIG-SUB026-002600#REF#
If obu should send an Acknowledgement of Emergency Stop (message 147) to the RBC with ETCS Language version 1.x, Q_EMERGENCYSTOP shall be set
according to the following table:


#ANALYSE-VALUNISIG-4797#REF# FCT The parameter value mapping table system version 2 to system version 1 is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

Chapter 7

TEST APPROACH:
Note: The track description is verified via a mode independent test interface if not stated otherwise.
		

Chapter 7.3

#REQ-UNISIG-SUB026-0330#REF# 7.3.2.7
Signed values shall be encoded as 2’s complement.
#ANALYSE-VALUNISIG-5261#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-2310#REF# 7.3.2.10
When transmitting over the different transmission media, the most significant bit shall be transmitted first.
#ANALYSE-VALUNISIG-5260#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-1001#REF# 7.3.3.7
If N_ITER is 0 then no variables follow.
#ANALYSE-VALUNISIG-5259#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

Chapter 7.4

TEST APPROACH:
The coding of packets as well as the acceptance check according to the requirements outlined hereafter is realized centrally by the software
module packet handler (PH). The requirements are thoroughly tested by PH module verification.
The quality of the module tests is ensured by review of the module test specification and test implementation as part of the module review. The
result of the review is documented in /ESBO_UUE/ --> reference ID ESBO_VerBer.

Hence no additional test is needed here.

Hint: The integration test aspect correct processing  of maximal information structure size is covered by the verification test of the parameter
N_ITER.
		
#REQ-UNISIG-SUB026-010587#REF# 7.4.2.0
7.4.2.0
Packet Number 0: Virtual Balise Cover marker

#ANALYSE-VALUNISIG-7533#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007441#REF# 7.4.2.1
Packet Number 2: System Version order

UNISIG clarification:
additional transmission media are loop and RIU
#ANALYSE-VALUNISIG-4667#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-3347:01#REF# 7.4.2.1.1 #REQ-UNISIG-SUB026-007070#REF#
#REQ-UNISIG-SUB026-007082#REF#
Packet Number 3: National Values







#ANALYSE-VALUNISIG-4668#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010496#REF# to.7.4.2.1.1
The following constraints for the national values for the brake model in P3 (system version 2 and higher) and P203 shall be valid:
- only one set of each Q_NVKVINTSET is allowed
(this means, that N_ITER to Q_NVKVINTSET is maximum 1)
- N_ITER to V_NVKVINT and to L_NVKRINT is maximum 4

A deviation from this constraints shall be handled as data inconsistency.
UNISIG clarification:
N_ITER to KVINT are the result of the specification, that only 5 steps are possible.
The constraint to Q_NVKVINTSET is self-explanatory.
TEST APPROACH:
The following aspects have been identified:
1) P3 from trackside operated with system version 2
2) P203 from trackside operated with system version 1.1
#TEST-VAL-SUB026-7958#REF# BVA 1 N_ITER limit for Q_NVKVINTSET, V_NVKVINT and L_NVKRINT in P3 National Values
#TEST-VAL-SUB026-7959#REF# BVA 2 N_ITER limit for Q_NVKVINTSET, V_NVKVINT and L_NVKRINT in P203 National Values for braking curves

#REQ-UNISIG-SUB026-0333#REF# 7.4.2.2
Packet Number 5: Linking

#ANALYSE-VALUNISIG-4669#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007492#REF# 7.4.2.11.3
Packet Number 6: Virtual Balise Cover order

#ANALYSE-VALUNISIG-7534#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0334:02#REF# 7.4.2.3
Packet Number 12: Level 1 Movement Authority

Rel. 8.0
transmission media is changed (without RBC)
#ANALYSE-VALUNISIG-4670#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-002601#REF# 7.4.2.3.1
Packet Number 13: Staff Responsible distance Information from loop

#ANALYSE-VALUNISIG-5262#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0897#REF# 7.4.2.4
Packet Number 15: Level 2/3 Movement Authority

#ANALYSE-VALUNISIG-4672#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0335#REF# 7.4.2.5
Packet Number 16: Repositioning Information

#ANALYSE-VALUNISIG-4673#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0336#REF# 7.4.2.6
Packet Number 21: Gradient Profile

#ANALYSE-VALUNISIG-4674#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0898:01#REF# 7.4.2.7
Packet Number 27: International Static Speed Profile

#ANALYSE-VALUNISIG-4675#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010475#REF# to.7.4.2.6
If the gradient profile is syntactical correct but implausible (e.g., End of Profile marker is not the last profile), the obu shall react with a
data consistency error.
UNISIG clarification: Implausible data are a trackside parametrization error. But the obu needs a reaction, if this error appears.
#ANALYSE-VALUNISIG-5352#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7085#REF# ECT basic function Reception of implausiblee P21/P27

#REQ-UNISIG-SUB026-010592#REF# to.7.4.2.7
If the static speed profile is syntactical correct but implausible (e.g., End of Profile marker is not the last profile, Q_DIFF 1 and 2 for one
NC_DIFF), the obu shall react with a data consistency error.
UNISIG clarification: Implausible data are a trackside parametrization error. But the obu needs a reaction, if this error appears.
#ANALYSE-VALUNISIG-5353#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-7085#REF# ECT basic function Reception of implausiblee P21/P27

#REQ-UNISIG-SUB026-0337:01#REF# 7.4.2.8
Packet Number 39: Track Condition Change of traction system

#ANALYSE-VALUNISIG-5321#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007474#REF# 7.4.2.8.1
Packet Number 40: Track Condition Change of allowed current consumption

#ANALYSE-VALUNISIG-4677#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0338#REF# 7.4.2.9
Packet Number 41: Level Transition Order

#ANALYSE-VALUNISIG-4678#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0339:01#REF# 7.4.2.10
Packet Number 42: Session Management

Rel. 8.0
transmission media is changed from any to balise, RBC
#ANALYSE-VALUNISIG-4679#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0340:01#REF# 7.4.2.11
Packet Number 44: Data used by applications outside the ERTMS/ETCS system.

Rel.8.0
NID_NTC is new
#ANALYSE-VALUNISIG-4680#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0449:01#REF# 7.4.2.11.1
Packet Number 45: Radio Network registration

Rel. 8.0
transmission media is changed from any to balise, RBC, RIU
#ANALYSE-VALUNISIG-4681#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0408:01#REF# 7.4.2.11.2
Packet Number 46: Conditional Level Transition Order

Rel. 8.0
transmission media is changed from any to balise
#ANALYSE-VALUNISIG-4682#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0341#REF# 7.4.2.12
Packet Number 49: List of balises for SH Area

#ANALYSE-VALUNISIG-4684#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0342:01#REF# 7.4.2.13
Packet Number 51: Axle Load Speed Profile

Rel. 8.0
D_TRACKINIT is new
#ANALYSE-VALUNISIG-4685#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007498#REF# 7.4.2.13.1
Packet Number 52: Permitted Braking Distance Information

#ANALYSE-VALUNISIG-4686#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0343#REF# 7.4.2.14
Packet Number 57: Movement Authority Request Parameters

#ANALYSE-VALUNISIG-4687#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0899#REF# 7.4.2.15
Packet Number 58: Position Report Parameters

#ANALYSE-VALUNISIG-4688#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0344#REF# 7.4.2.16
Packet Number 63: List of Balises in SR Authority

#ANALYSE-VALUNISIG-4689#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007513#REF# 7.4.2.16.1
Packet Number 64: Inhibition of revocable TSRs from balises in L2/3

#ANALYSE-VALUNISIG-4690#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0345#REF# 7.4.2.17
Packet Number 65: Temporary Speed Restriction

#ANALYSE-VALUNISIG-4691#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0900#REF# 7.4.2.18
Packet Number 66: Temporary Speed Restriction Revocation

#ANALYSE-VALUNISIG-4692#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0346#REF# 7.4.2.19
Packet Number 67: Track Condition Big Metal Masses

#ANALYSE-VALUNISIG-4693#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0901#REF# 7.4.2.20
Packet Number 68: Track Condition

#ANALYSE-VALUNISIG-4694#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007528#REF# 7.4.2.20.1
Packet Number 69: Track Condition Station Platforms

#ANALYSE-VALUNISIG-4695#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0347:01#REF# 7.4.2.21
Packet Number 70:  Route Suitability Data

Rel. 8.0
M_LINEGAUGE, M_VOLTAGE and NID_CTRACTION new/changed
#ANALYSE-VALUNISIG-4696#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-1184#REF# 7.4.2.22
Packet number 71: Adhesion factor

#ANALYSE-VALUNISIG-4697#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0348:01#REF# 7.4.2.23
Packet Number 72: Packet for sending plain text messages

#ANALYSE-VALUNISIG-4698#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0902:01#REF# 7.4.2.24
Packet Number 76: Packet for sending fixed text messages

#ANALYSE-VALUNISIG-4699#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0187:01#REF# 7.4.2.25 #REQ-DESIGN-CR-0152#REF#
Packet Number 79: Geographical Position Information

Rel. 8.0
transmission media is changed from any to balise, RBC

M_POSITION is changed
#ANALYSE-VALUNISIG-4700#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0349:01#REF# 7.4.2.26
Packet Number 80: Mode profile

#ANALYSE-VALUNISIG-4701#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007549#REF# 7.4.2.26.1
Packet Number 88: Level Crossing information

#ANALYSE-VALUNISIG-4702#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0526#REF# 7.4.2.26.2
Packet Number 90: Track Ahead Free up to level 2/3 transition location

#ANALYSE-VALUNISIG-4703#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0350:01#REF# 7.4.2.27
Packet Number 131: RBC transition order

Rel. 8.0
transmission media is changed from any to balise, RBC
#ANALYSE-VALUNISIG-4704#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0351#REF# 7.4.2.28
Packet Number 132: Danger for Shunting information

#ANALYSE-VALUNISIG-4705#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0352#REF# 7.4.2.29
Packet Number 133: Radio infill area information

#ANALYSE-VALUNISIG-4706#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0353#REF# 7.4.2.30
Packet Number 134: EOLM Packet

#ANALYSE-VALUNISIG-4707#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007570#REF# 7.4.2.31
Packet Number 135: Stop Shunting on desk opening

UNISIG clarification:
this packet can also  used with ETCS Language 1.x. No exclusion is defined in chapter 6.
#ANALYSE-VALUNISIG-4708#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0355:02#REF# 7.4.2.32 #REQ-UNISIG-SUB026-0039#REF#
Packet Number 136: Infill location reference

Rel. 8.0
transmission media is changed from any to balise, loop, RIU
#ANALYSE-VALUNISIG-4709#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0356#REF# 7.4.2.33
Packet Number 137: Stop if in Staff Responsible

#ANALYSE-VALUNISIG-4710#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0357#REF# 7.4.2.34
Packet Number 138: Reversing area information

#ANALYSE-VALUNISIG-4711#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0358#REF# 7.4.2.35 #REQ-UNISIG-SUB026-3107#REF#
Packet Number 139: Reversing supervision information

#ANALYSE-VALUNISIG-4712#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0359#REF# 7.4.2.36
Packet Number 140: Train running number from RBC

#ANALYSE-VALUNISIG-4713#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0360#REF# 7.4.2.37 #REQ-UNISIG-SUB026-3645:01#REF#
Packet Number 141: Default Gradient for Temporary Speed Restriction

#ANALYSE-VALUNISIG-4714#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-009781#REF# 7.4.2.37.1
Packet Number 143: Session Management with neighbouring Radio Infill Unit

#ANALYSE-VALUNISIG-4715#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-009890#REF# 7.4.2.37.2
Packet Number 145: Inhibition of balise group message consistency reaction

#ANALYSE-VALUNISIG-4716#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0396:01#REF# 7.4.2.38
Packet Number 254: Default balise, loop or RIU information

Rel. 8.0
transmission media is changed from any to balise, loop, RIU
#ANALYSE-VALUNISIG-4717#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0362#REF# 7.4.3.1
Packet Number 0: Position Report

#ANALYSE-VALUNISIG-4718#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0904#REF# 7.4.3.2
Packet Number 1: Position Report based on two balise groups

#ANALYSE-VALUNISIG-4719#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0905#REF# 7.4.3.3
Packet Number 3: Onboard telephone numbers

#ANALYSE-VALUNISIG-4720#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0906#REF# 7.4.3.4
Packet Number 4: Error reporting

#ANALYSE-VALUNISIG-4721#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007611#REF# 7.4.3.4.1
Packet Number 5: Train running number

#ANALYSE-VALUNISIG-4722#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0527#REF# 7.4.3.4.2
Packet Number 9: Level 2/3 transition information

#ANALYSE-VALUNISIG-4723#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0186:01#REF# 7.4.3.5
Packet Number 11: Validated train data

#ANALYSE-VALUNISIG-4724#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0363#REF# 7.4.3.6
Packet Number 44: Data used by applications outside the ERTMS/ETCS system.

#ANALYSE-VALUNISIG-4725#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0364:01#REF# 7.4.4.1
Packet Number 255: End of Information

#ANALYSE-VALUNISIG-4726#REF# FCT The packet structure/coding and acceptance depending on transmission media is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

Chapter 7.5

TEST APPROACH:
The coding of parameter according to the requirements as well as translation of the parameter values from/to the internal representation is
realized centrally by the software module packet handler (PH).
This includes the check for spare values.  
The requirements are thoroughly tested by PH module verification. 
The quality of the module tests is ensured by review of the module test specification and test implementation as part of the module review. The
result of the review is documented in /ESBO_UUE/ --> reference ID ESBO_VerBer.

The aim of the test cases outlined here is to verify the provisioning/distribution of the parameter values to/from the packet handler.
The verification is don for each parameter depending on the usage of the packet for the sending and/or receiving direction (sending and
receiving is evaluated as one equivalence class each).
		
#REQ-UNISIG-SUB026-007575#REF# 7.5.0.1 #REQ-UNISIG-SUB026-007054#REF#
7.5.0.1 A_NVMAXREDADH1

#TEST-VAL-SUB026-5631#REF# BVA basic function Variable test A_NVMAXREDADH1

#REQ-UNISIG-SUB026-007576#REF# 7.5.0.2 #REQ-UNISIG-SUB026-007055#REF#
7.5.0.2 A_NVMAXREDADH2

#TEST-VAL-SUB026-5632#REF# BVA basic function Variable test A_NVMAXREDADH2

#REQ-UNISIG-SUB026-007577#REF# 7.5.0.3 #REQ-UNISIG-SUB026-007056#REF#
7.5.0.3 A_NVMAXREDADH3

#TEST-VAL-SUB026-5633#REF# BVA basic function Variable test A_NVMAXREDADH3

#REQ-UNISIG-SUB026-007584#REF# 7.5.0.4
7.5.0.4 A_NVP12

#TEST-VAL-SUB026-5637#REF# BVA basic function Variable test A_NVP12, A_NVP23

#REQ-UNISIG-SUB026-007585#REF# 7.5.0.5
7.5.0.5 A_NVP23

#TEST-VAL-SUB026-5637#REF# BVA basic function Variable test A_NVP12, A_NVP23

#REQ-UNISIG-SUB026-007647#REF# 7.5.1.1
D_ADHESION

#TEST-VAL-SUB026-7401#REF# BVA basic function D_ADHESION and M_ADHESION test

#REQ-UNISIG-SUB026-007650#REF# 7.5.1.2
D_AXLELOAD

#TEST-VAL-SUB026-7402#REF# BVA basic function Variable test D_AXLELOAD

#REQ-UNISIG-SUB026-007653#REF# 7.5.1.2.1
D_CURRENT

#TEST-VAL-SUB026-7762#REF# BVA basic function Variable test D_CURRENT

#REQ-UNISIG-SUB026-007656#REF# 7.5.1.3
D_CYCLOC

#TEST-VAL-SUB026-7403#REF# BVA basic function Variablentest D_CYCLOC

#REQ-UNISIG-SUB026-007659#REF# 7.5.1.4
D_DP

#TEST-VAL-SUB026-7404#REF# BVA basic function Variable test D_DP

#REQ-UNISIG-SUB026-007662#REF# 7.5.1.5
D_EMERGENCYSTOP

#TEST-VAL-SUB026-7405#REF# BVA basic function Variablentest D_EMERGENCYSTOP

#REQ-UNISIG-SUB026-007665#REF# 7.5.1.6
D_ENDTIMERSTARTLOC

#TEST-VAL-SUB026-7406#REF# BVA basic function Variablentest D_ENDTIMERSTARTLOC

#REQ-UNISIG-SUB026-007668#REF# 7.5.1.7
D_GRADIENT

#TEST-VAL-SUB026-7407#REF# BVA basic function Variable test D_GRADIENT

#REQ-UNISIG-SUB026-007671#REF# 7.5.1.8
D_INFILL

#TEST-VAL-SUB026-7408#REF# BVA basic function Variablentest D_INFILL

#REQ-UNISIG-SUB026-007674#REF# 7.5.1.9
D_LEVELTR

#TEST-VAL-SUB026-7409#REF# ECT basic function , CFX00039485 Variablentest D_LEVELTR

#REQ-UNISIG-SUB026-007677#REF# 7.5.1.10
D_LINK

#TEST-VAL-SUB026-7410#REF# BVA basic function , CFX00035445 Variable test D_LINK

#REQ-UNISIG-SUB026-007680#REF# 7.5.1.11
D_LOC

#TEST-VAL-SUB026-7411#REF# BVA basic function Variablentest D_LOC

#REQ-UNISIG-SUB026-007683#REF# 7.5.1.12
D_LOOP

#TEST-VAL-SUB026-7412#REF# ECT basic function Variable test D_LOOP

#REQ-UNISIG-SUB026-007686#REF# 7.5.1.13
D_LRBG

#TEST-VAL-SUB026-8159#REF# BVA max value Variable test D_LRBG - max value
#TEST-VAL-SUB026-8156#REF# BVA min value Variable test D_LRBG - min value
#TEST-VAL-SUB026-7413#REF# BVA special value , CFX00035447 Variablentest D_LRBG

#REQ-UNISIG-SUB026-007689#REF# 7.5.1.13.1
D_LX

#TEST-VAL-SUB026-7656#REF# BVA basic function Variable D_LX

#REQ-UNISIG-SUB026-007692#REF# 7.5.1.14
D_MAMODE

#TEST-VAL-SUB026-7414#REF# BVA basic function Variable test D_MAMODE

#REQ-UNISIG-SUB026-007695#REF# 7.5.1.15
D_NVOVTRP

#TEST-VAL-SUB026-3234#REF# BVA basic function Variablentest D_NVOVTRP

#REQ-UNISIG-SUB026-007698#REF# 7.5.1.16
D_NVPOTRP

#TEST-VAL-SUB026-3239#REF# BVA basic function Variablentest D_NVPOTRP

#REQ-DESIGN-CR-0370#REF# 7.5.1.17
D_NVROLL

#TEST-VAL-SUB026-3229#REF# BVA basic function Variablentest D_NVROLL

#REQ-UNISIG-SUB026-007704#REF# 7.5.1.18
D_NVSTFF

#TEST-VAL-SUB026-3240#REF# BVA basic function Variablentest D_NVSTFF

#REQ-UNISIG-SUB026-007707#REF# 7.5.1.19
D_OL

#TEST-VAL-SUB026-7419#REF# BVA basic function Variable test D_OL

#REQ-UNISIG-SUB026-007710#REF# 7.5.1.19.1
D_PBD

#TEST-VAL-SUB026-4B95#REF# BVA basic function test variable D_PBD

#REQ-UNISIG-SUB026-007713#REF# 7.5.1.19.2
D_PBDSR

#TEST-VAL-SUB026-4B96#REF# BVA basic function test variable D_PBDSR

#REQ-UNISIG-SUB026-3479#REF# 7.5.1.20
D_POSOFF

#TEST-VAL-SUB026-7420#REF# BVA basic function Variablentest D_POSOFF

#REQ-UNISIG-SUB026-007719#REF# 7.5.1.21
D_RBCTR

#TEST-VAL-SUB026-7575#REF# BVA max D_RBCTR Variable test D_RBCTR
#TEST-VAL-SUB026-7421#REF# BVA min/valid D_RBCTR Variablentest D_RBCTR

#REQ-UNISIG-SUB026-007722#REF# 7.5.1.22
D_REF

TEST APPROACH:
The following aspects were identified (D_REF is a part of the following messages):
1) Message 15: Conditional Emergency Stop
2) Message 33: MA with Shifted Location Reference
3) Message 34: Track Ahead Free Request
#TEST-VAL-SUB026-5842#REF# BVA 1, 2 Variable test D_REF
#TEST-VAL-SUB026-5843#REF# BVA 3 Variable test D_REF

#REQ-UNISIG-SUB026-3282#REF# 7.5.1.23
D_REVERSE

#TEST-VAL-SUB026-7578#REF# BVA basic function Variable test D_REVERSE, D_STARTREVERSE, L_REVERSEAREA

#REQ-UNISIG-SUB026-007728#REF# 7.5.1.24
D_SECTIONTIMERSTOPLOC

#TEST-VAL-SUB026-7424#REF# BVA basic function Variablentest D_SECTIONTIMERSTOPLOC

#REQ-UNISIG-SUB026-007731#REF# 7.5.1.25
D_SR

#TEST-VAL-SUB026-7425#REF# BVA basic function Variable test D_SR

#REQ-UNISIG-SUB026-007734#REF# 7.5.1.26
D_STARTOL

#TEST-VAL-SUB026-7426#REF# ECT basic function Variablentest D_STARTOL

#REQ-UNISIG-SUB026-007737#REF# 7.5.1.27
D_STARTREVERSE

#TEST-VAL-SUB026-7578#REF# BVA basic function Variable test D_REVERSE, D_STARTREVERSE, L_REVERSEAREA

#REQ-UNISIG-SUB026-007740#REF# 7.5.1.28
D_STATIC

#TEST-VAL-SUB026-7428#REF# BVA basic function Variable test D_STATIC

#REQ-UNISIG-SUB026-007743#REF# 7.5.1.29
D_SUITABILITY

#TEST-VAL-SUB026-7429#REF# BVA basic function D_SUITABILITY test

#REQ-UNISIG-SUB026-007746#REF# 7.5.1.30
D_TAFDISPLAY

#TEST-VAL-SUB026-5843#REF# BVA basic function Variable test D_REF

#REQ-UNISIG-SUB026-007749#REF# 7.5.1.31
D_TEXTDISPLAY

#TEST-VAL-SUB026-8157#REF# BVA basic function Variable test D_TEXTDISPLAY

#REQ-UNISIG-SUB026-007752#REF# 7.5.1.32
D_TRACKINIT

#TEST-VAL-SUB026-7432#REF# BVA basic function Variable test D_TRACKINIT

#REQ-UNISIG-SUB026-007755#REF# 7.5.1.33
D_TRACKCOND

#TEST-VAL-SUB026-7433#REF# BVA basic function Variable test D_TRACKCOND

#REQ-UNISIG-SUB026-007758#REF# 7.5.1.34
D_TRACTION

#TEST-VAL-SUB026-7434#REF# BVA basic function Variable test D_TRACTION

#REQ-UNISIG-SUB026-007761#REF# 7.5.1.35
D_TSR

#TEST-VAL-SUB026-7435#REF# BVA basic function Variable test D_TSR

#REQ-UNISIG-SUB026-007764#REF# 7.5.1.36
D_VALIDNV

Rel. 8.0:
the value "now" is new
#TEST-VAL-SUB026-7436#REF# BVA min, max Variablentest D_VALIDNV
#TEST-VAL-SUB026-3A99#REF# BVA special value test special value (now) of variable D_VALIDNV

#REQ-UNISIG-SUB026-007767#REF# 7.5.1.37
G_A

#TEST-VAL-SUB026-7437#REF# BVA basic function Variable test G_A

#REQ-UNISIG-SUB026-007770#REF# 7.5.1.37.1
G_PBDSR

#TEST-VAL-SUB026-4B97#REF# BVA basic function test variable G_PBDSR

#REQ-UNISIG-SUB026-007773#REF# 7.5.1.38
G_TSR

#TEST-VAL-SUB026-7438#REF# BVA basic function Variablentest G_TSR

#REQ-UNISIG-SUB026-007777#REF# 7.5.1.39
L_ACKLEVELTR

#TEST-VAL-SUB026-7439#REF# BVA basic function Variable test L_ACKLEVELTR

#REQ-UNISIG-SUB026-007783#REF# 7.5.1.40
L_ACKMAMODE

#TEST-VAL-SUB026-7440#REF# BVA basic function Variablentest L_ACKMAMODE

#REQ-UNISIG-SUB026-007784#REF# 7.5.1.41
L_ADHESION

#TEST-VAL-SUB026-7441#REF# BVA basic function Variable test L_ADHESION

#REQ-UNISIG-SUB026-007785#REF# 7.5.1.42
L_AXLELOAD

#TEST-VAL-SUB026-7442#REF# BVA basic function Variable test L_AXLELOAD

#REQ-UNISIG-SUB026-007788#REF# 7.5.1.43
L_DOUBTOVER

#TEST-VAL-SUB026-7100#REF# EET CFX00035328 L_DOUBTOVER and L_DOUBTUNDER while the train location is unknown.
#TEST-VAL-SUB026-8156#REF# BVA min value Variable test D_LRBG - min value
#TEST-VAL-SUB026-7443#REF# BVA special value, max value Variablentest L_DOUBTOVER and L_DOUBTUNDER

#REQ-UNISIG-SUB026-007791#REF# 7.5.1.44
L_DOUBTUNDER

#TEST-VAL-SUB026-7100#REF# EET CFX00035328 L_DOUBTOVER and L_DOUBTUNDER while the train location is unknown.
#TEST-VAL-SUB026-8156#REF# BVA min value Variable test D_LRBG - min value
#TEST-VAL-SUB026-7443#REF# BVA special value, max value Variablentest L_DOUBTOVER and L_DOUBTUNDER

#REQ-UNISIG-SUB026-007794#REF# 7.5.1.45
L_ENDSECTION

#TEST-VAL-SUB026-7445#REF# BVA basic function Variable test L_ENDSECTION

#REQ-UNISIG-SUB026-007797#REF# 7.5.1.46
L_LOOP

#TEST-VAL-SUB026-7446#REF# ECT basic function Variable test L_LOOP

#REQ-UNISIG-SUB026-007800#REF# 7.5.1.46.1
L_LX

#TEST-VAL-SUB026-7655#REF# BVA basic function Variables NID_LX, L_LX, V_LX

#REQ-UNISIG-SUB026-007803#REF# 7.5.1.47
L_MAMODE

#TEST-VAL-SUB026-7447#REF# BVA basic function Variable test L_MAMODE

#REQ-UNISIG-SUB026-007806#REF# 7.5.1.48
L_MESSAGE

TEST APPROACH:
The minimal value L_MESSAGE=0 can not occur in a valid message as the length of L_MESSAGE is included in the value of L_MESSAGE, hence
L_MESSAGE=0 means the message has consistency error. 
The minimal value L_MESSAGE of a valid message is 10 (e.g. M6, M16).
#TEST-VAL-SUB026-7448#REF# BVA basic function Test of variable L_MESSAGE

#REQ-UNISIG-SUB026-007587#REF# 7.5.1.48.1 #REQ-UNISIG-SUB026-007058#REF#
L_NVKRINT

TEST APPROACH:
The coding of parameter according to the requirements as well as translation of the parameter values from/to the internal representation is
realized centrally by the software module packet handler (PH). (see general test approach for Chapter 7.5). The scope of the test case outlined
here is to verify that the translated values for the  boundary values of the parameter are correctly handled in the software.
#TEST-VAL-SUB026-5640#REF# FCT basic function Variable test L_NVKRINT

#REQ-UNISIG-SUB026-007812#REF# 7.5.1.49
L_PACKET

#TEST-VAL-SUB026-7449#REF# ECT basic function Variablentest L_PACKET

#REQ-UNISIG-SUB026-007815#REF# 7.5.1.49.1
L_PBDSR

#TEST-VAL-SUB026-4B98#REF# BVA basic function test variable L_PBDSR

#REQ-UNISIG-SUB026-007818#REF# 7.5.1.50
L_REVERSEAREA

#TEST-VAL-SUB026-7578#REF# BVA basic function Variable test D_REVERSE, D_STARTREVERSE, L_REVERSEAREA

#REQ-UNISIG-SUB026-007821#REF# 7.5.1.51
L_SECTION

#TEST-VAL-SUB026-7451#REF# BVA basic function L_SECTION

#REQ-UNISIG-SUB026-007824#REF# 7.5.1.51.1
L_STOPLX

#TEST-VAL-SUB026-7657#REF# BVA basic function Variable L_STOPLX

#REQ-UNISIG-SUB026-007828#REF# 7.5.1.52
L_TAFDISPLAY

#TEST-VAL-SUB026-7452#REF# BVA basic function Variablentest L_TAFDISPLAY

#REQ-UNISIG-SUB026-007830#REF# 7.5.1.53
L_TEXT

#TEST-VAL-SUB026-7453#REF# BVA basic function Variablentest L_TEXT

#REQ-UNISIG-SUB026-007833#REF# 7.5.1.54
L_TEXTDISPLAY

#TEST-VAL-SUB026-8158#REF# BVA basic function Variable test L_TEXTDISPLAY

#REQ-UNISIG-SUB026-007839#REF# 7.5.1.55
L_TRACKCOND

#TEST-VAL-SUB026-7455#REF# BVA basic function Variable test L_TRACKCOND

#REQ-DESIGN-CR-0143:01#REF# 7.5.1.56
L_TRAIN

#TEST-VAL-SUB026-7456#REF# BVA basic function , CFX00036570 Variablentest L_TRAIN

#REQ-UNISIG-SUB026-007842#REF# 7.5.1.57
L_TRAININT

TEST APPROACH:
The appropriated L3 feature train integrity is not supported in R8.0. The verification takes place via module test.
#ANALYSE-VALUNISIG-5330#REF# FCT The parameter coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-007844#REF# 7.5.1.58
L_TSR

#TEST-VAL-SUB026-7458#REF# BVA basic function Variable test L_TSR

#REQ-UNISIG-SUB026-007851#REF# 7.5.1.59
M_ACK

#TEST-VAL-SUB026-5793#REF# FCT basic function Variable test M_ACK

#REQ-UNISIG-SUB026-007591#REF# 7.5.1.60
M_ADHESION

#TEST-VAL-SUB026-7401#REF# BVA basic function D_ADHESION and M_ADHESION test

#REQ-DESIGN-CR-0144#REF# 7.5.1.61
M_AIRTIGHT

#TEST-VAL-SUB026-7461#REF# ECT basic function Variablentest M_AIRTIGHT

#REQ-DESIGN-CR-0145:01#REF# 7.5.1.62
M_AXLELOADCAT

TEST APPROACH:
Values will be verified for both receiving and sending situations.
#TEST-VAL-SUB026-3B07#REF# ECT receiving Considering axle load speed restrictions based on train axle load
#TEST-VAL-SUB026-8155#REF# ECT sending Variable test M_AXLELOADCAT - sending

#REQ-UNISIG-SUB026-007860#REF# 7.5.1.62.1
M_CURRENT

#TEST-VAL-SUB026-7761#REF# BVA basic function Variable test M_CURRENT

#REQ-DESIGN-CR-0617#REF# 7.5.1.63
M_DUP

#TEST-VAL-SUB026-7463#REF# FCT basic function Variablentest M_DUP

#REQ-UNISIG-SUB026-3018:01#REF# 7.5.1.64
M_ERROR

UNISIG clarificatiion:
the addition "to be sent when communication links re-established" for M_ERROR=5 is not correct. The dependency error report to safe
conecction is defined in 3.16.4.1.
#TEST-VAL-SUB026-5755#REF# ECT 6, 8 Error report to RBC
#TEST-VAL-SUB026-5754#REF# ECT 0, 1, 2, 3, 4, 5, 7 Error report to RBC

#REQ-UNISIG-SUB026-007869#REF# 7.5.1.65
M_LEVEL

#TEST-VAL-SUB026-7465#REF# ECT basic function Variable test M_LEVEL

#REQ-UNISIG-SUB026-007875#REF# 7.5.1.66
M_LEVELTEXTDISPLAY

UNISIG clarification:
"as long as in the defined level" is not correct, because the level has to be taken before
=> "until the level is leaved".
#TEST-VAL-SUB026-7466#REF# ECT basic function Variablentest M_LEVELTEXTDISPLAY

#REQ-UNISIG-SUB026-007878#REF# 7.5.1.67
M_LEVELTR

#TEST-VAL-SUB026-7467#REF# ECT basic function Variablentest M_LEVELTR

#REQ-UNISIG-SUB026-007881#REF# 7.5.1.67.1
M_LINEGAUGE

#TEST-VAL-SUB026-7708#REF# ECT basic function Variable test M_LINEGAUGE

#REQ-UNISIG-SUB026-007884#REF# 7.5.1.68
M_LOADINGGAUGE

#TEST-VAL-SUB026-7468#REF# ECT basic function Variable test M_LOADINGGAUGE

#REQ-DESIGN-CR-0009#REF# 7.5.1.69
M_LOC

#TEST-VAL-SUB026-7469#REF# ECT basic function Variablentest M_LOC (M_LOC 0, 1, 2, 3, 4, 5, 6, 7)

#REQ-UNISIG-SUB026-3341#REF# 7.5.1.70
M_MAMODE

#TEST-VAL-SUB026-5916#REF# ECT 1 A3.4.1.2 a List of balises for SH area
#TEST-VAL-SUB026-7470#REF# ECT 2, 3 Variablentest M_MAMODE
#TEST-VAL-SUB026-5763#REF# ECT 0 Start of OS area supervision

#REQ-DESIGN-CR-0361#REF# 7.5.1.71
M_MCOUNT

#TEST-VAL-SUB026-7471#REF# ECT basic function Variablentest M_MCOUNT (M_MCOUNT minimal=0, maximal=253), AKT (M_MCOUNT erlaubt=96, fit all=255)

#REQ-UNISIG-SUB026-3342:01#REF# 7.5.1.72
M_MODE

#TEST-VAL-SUB026-4570#REF# FCT IS mode transition LS->IS[1], processing Radio/BG message in IS
#TEST-VAL-SUB026-4550#REF# FCT LS SR mode speed limit and distance when entering LS
#TEST-VAL-SUB026-3047#REF# FCT NL, SL, SB Position report at mode change
#TEST-VAL-SUB026-4244#REF# FCT OS transition FS(L2) -> OS(L2-L1) -> SR
#TEST-VAL-SUB026-5942#REF# FCT PS Reception of several LTO in PS, no supervision safe radio connection
#TEST-VAL-SUB026-4248#REF# FCT PT transition FS(L2) -> TR(L1)[18] -> PT[7] -> SR[37]
#TEST-VAL-SUB026-4363#REF# FCT RV PR at mode change to RV, PR at standstill in RV, determine train speed and location
#TEST-VAL-SUB026-4060#REF# FCT SF Test active functions in mode SF (Pos Report, JRU recording)
#TEST-VAL-SUB026-4393#REF# FCT SH SB->SH[6] - degraded situation RBC does not order termination of connection
#TEST-VAL-SUB026-4241#REF# FCT SN transition FS/L2 - SN/STM - SH/L2
#TEST-VAL-SUB026-4242#REF# FCT SR, FS transition FS -> SR -> FS in level 2
#TEST-VAL-SUB026-4254#REF# FCT TR transition SR(L2) -> SR(L1) -> TR(L1)[65]
#TEST-VAL-SUB026-4251#REF# FCT UN transition FS(L2) -> UN(L0)[21] -> SH[5] -> SB[19]

#REQ-UNISIG-SUB026-3343:01#REF# 7.5.1.73
M_MODETEXTDISPLAY

UNISIG clarification:
"as long as in the defined mode" is not correct, because the mode has to be taken before
=> "until the mode is leaved".
#TEST-VAL-SUB026-7473#REF# ECT 1-11, 13, 15 Variablentest M_MODETEXTDISPLAY
#TEST-VAL-SUB026-4550#REF# ECT 12 SR mode speed limit and distance when entering LS
#TEST-VAL-SUB026-7580#REF# ECT 14 , CFX00035542 Variablentest M_MODETEXTDISPLAY

#REQ-UNISIG-SUB026-007578#REF# 7.5.1.73.1 #REQ-UNISIG-SUB026-007052#REF#
M_NVAVADH

#TEST-VAL-SUB026-5634#REF# BVA basic function Variable test M_NVAVADH

#REQ-UNISIG-SUB026-007905#REF# 7.5.1.74
M_NVCONTACT

#TEST-VAL-SUB026-3237#REF# ECT basic function Variablentest M_NVCONTACT

#REQ-UNISIG-SUB026-007908#REF# 7.5.1.75
M_NVDERUN

#TEST-VAL-SUB026-3785#REF# ECT basic function Effect of M_NVDERUN for availibility of driver choice change driver id

#REQ-UNISIG-SUB026-007579:01#REF# 7.5.1.75.1 #REQ-UNISIG-SUB026-007051:01#REF#
M_NVEBCL

TEST APPROACH:
The coding of parameter according to the requirements as well as translation of the parameter values from/to the internal representation is
realized centrally by the software module packet handler (PH). (see general test approach for Chapter 7.5). The scope of the test case outlined
here is to verify that the translated values for the  boundary values of the parameter are correctly handled in the software.
#TEST-VAL-SUB026-5635#REF# BVA basic function Variable test M_NVEBCL

#REQ-UNISIG-SUB026-007586#REF# 7.5.1.75.2 #REQ-UNISIG-SUB026-007058#REF#
M_NVKRINT

#TEST-VAL-SUB026-5641#REF# BVA basic function Variable test M_NVKRINT

#REQ-UNISIG-SUB026-007588#REF# 7.5.1.75.3 #REQ-UNISIG-SUB026-007058#REF#
#REQ-UNISIG-SUB026-007082#REF#
M_NVKTINT

#TEST-VAL-SUB026-5643#REF# BVA basic function Variable test M_NVKTINT

#REQ-UNISIG-SUB026-007582#REF# 7.5.1.75.4 #REQ-UNISIG-SUB026-007058#REF#
#REQ-UNISIG-SUB026-007070#REF#
M_NVKVINT

#TEST-VAL-SUB026-5639#REF# BVA basic function Variable test M_NVKVINT

#REQ-UNISIG-SUB026-007923#REF# 7.5.1.75.5
M_PLATFORM

P69 is ignored without decoding, because TC Station Platform isn't realized. 
So this information doesn't needed.

#REQ-DESIGN-CR-0618:01#REF# 7.5.1.76
M_POSITION

#TEST-VAL-SUB026-7921#REF# BVA basic function Testing variable M_POSITION

#REQ-DESIGN-CR-0601:01#REF# 7.5.1.77
M_TRACKCOND

#TEST-VAL-SUB026-7049#REF# ECT basic function Variable test M_TRACKCOND

#REQ-UNISIG-SUB026-007932#REF# 7.5.1.78
M_VOLTAGE

UNISIG clarification: If the train isn't equipped with any traction system, the value 0 "line not fitted with any traction
system" is used for train too.
TEST APPROACH:
Values 0..5 will be verified for both receiving and sending situations.
#TEST-VAL-SUB026-7617#REF# ECT receiving: 0, 1 Indication of TC change of traction system M_VOLTAGE: 0, 1
#TEST-VAL-SUB026-7618#REF# ECT receiving: 2, 3 Indication of TC change of traction system M_VOLTAGE: 2, 3
#TEST-VAL-SUB026-7619#REF# ECT receiving: 4, 5, spare Indication of TC change of traction system M_VOLTAGE: 4, 5
#TEST-VAL-SUB026-7680#REF# ECT sending Varaibles M_VOLTAGE, NID_CTRACTION for sending case

#REQ-UNISIG-SUB026-007935#REF# 7.5.1.79
M_VERSION

realised by: #REQ-DESIGN-CR-0483:03#REF#

#REQ-DESIGN-CR-0483:03#REF# 7.5.1.79 #REQ-UNISIG-SUB026-007935#REF#
M_VERSION

UNISIG clarification:
the version 1.2 and higher is redefined to "Reserved for future use (this is a valid value)", because a later definition of these
versions is possible and some information (P2xx) are accepted from version 1.1 and higher now.
#TEST-VAL-SUB026-3205#REF# FCT 0x0X BG mit Version 0.0 wird ignoriert
#TEST-VAL-SUB026-3722#REF# FCT 0x10, 0x20 RBC1/RBC2 Handover; RBC1 version 0x10, RBC2 version 0x20
#TEST-VAL-SUB026-4B91#REF# FCT 0x11, 0x1F, 0x20, 0x21 Variable test M_VERSION
#TEST-VAL-SUB026-3206#REF# FCT 0x30 BG with unsupported M_VERSION: transition into TR
#TEST-VAL-SUB026-7611#REF# FCT max 0x7F (BG) Reception of M_VERSION=127 from BG
#TEST-VAL-SUB026-7592#REF# FCT max 0x7F (RBC) Check of M_VERSION=127 by radio

#REQ-UNISIG-SUB026-007938#REF# 7.5.1.79.1
N_AXLE

#TEST-VAL-SUB026-7949#REF# BVA 1 Variable test N_AXLE = 1
#TEST-VAL-SUB026-7950#REF# BVA 1022 Variable test N_AXLE = 1022
#TEST-VAL-SUB026-7951#REF# BVA 1023 Variable test N_AXLE = 1023
#TEST-VAL-SUB026-4A02#REF# BVA 0 Variable test N_AXLE = 0

#REQ-UNISIG-SUB026-007941#REF# 7.5.1.80
N_ITER

TEST APPROACH:
The parameter N_ITER is used in several pakets and defines the structure seize. Aim of the test is to verify the correct processing of
information for the minimal and maximum size. 
The following aspects have been identified:
1) Received information
1.1) P3 
1.1.1) N_ITER concerning NID_C
1.1.2) N_ITER concerning NV for BC:
1.1.2.1) N_ITER concerning number of Kv int sets
1.1.2.2) N_ITER concerning number of steps in a Kv int set
1.1.2.3) N_ITER concerning number of steps in a Kr int set
1.2) P5
1.3) P12
1.4) P13
1.5) P15
1.6) P21
1.7) P27
1.8) P41
1.9) P46
1.10) P49
1.11) P51
1.12) P52
1.13) P58
1.14) P63
1.15) P67
1.16) P68
1.17) P69
1.18) P70
1.19) P79
1.20) P80
2) Send information
2.1) P3
2.2) P11

Following aspects are omitted as the approapriated function is not part of R8
1.4) P13 feature 
1.17) (P69) feature awakening on loop refer #REQ-SRS-004560#REF#
#TEST-VAL-SUB026-8164#REF# BVA 1.1 Variable test N_ITER (Packet 3)
#TEST-VAL-SUB040-0024#REF# BVA 1.2 32 announced BGs
#TEST-VAL-SUB040-0015#REF# BVA basic function SSPs with 50 changes

#REQ-UNISIG-SUB026-007944#REF# 7.5.1.81
N_PIG

#TEST-VAL-SUB026-3000#REF# BVA basic function Fahrt ueber Single BG, Fahrt ueber 8er BG

#REQ-UNISIG-SUB026-007947#REF# 7.5.1.82
N_TOTAL

#TEST-VAL-SUB026-3000#REF# BVA basic function Fahrt ueber Single BG, Fahrt ueber 8er BG

#REQ-UNISIG-SUB026-007950#REF# 7.5.1.82.1
NC_CDDIFF

#TEST-VAL-SUB026-5876#REF# BVA basic function Variable test NC_CDDIFF

#REQ-UNISIG-SUB026-007953#REF# 7.5.1.82.2
NC_CDTRAIN

#TEST-VAL-SUB026-4H99#REF# ECT basic function Variable test NC_CDTRAIN

#REQ-UNISIG-SUB026-3471:01#REF# 7.5.1.83
NC_DIFF

#TEST-VAL-SUB026-5872#REF# BVA 0 (Specific SSP applicable to Freight train braked in 'P' position) Variable test Q_DIFF
#TEST-VAL-SUB026-5877#REF# BVA 1 (Specific SSP applicable to Freight train braked in 'G' position), 3 (spare) Variable test NC_DIFF
#TEST-VAL-SUB026-5871#REF# BVA 2 (Specific SSP applicable to Passenger train) Selection of the most restrictive SSP

#REQ-UNISIG-SUB026-3472:01#REF# 7.5.1.84
NC_TRAIN

UNISIG clarification: the value 0 can not be taken
TEST APPROACH:
The train data input on the ERA DMI ensures that the train belongs to one of the ' Other International' Train Category the sending of NC_TRAIN=0
(Train does not belong to any of the ' Other International' Train Category) can not be triggered.
#TEST-VAL-SUB026-3B64#REF# FCT basic function Variable test NC_TRAIN

#REQ-UNISIG-SUB026-3003#REF# 7.5.1.85
NID_BG (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7485#REF# BVA min, max Variablentest NID_BG
#TEST-VAL-SUB026-3656#REF# FCT special value (Linking info) lnk repo BG announced, pass BG with repo info valid but Q_LINK=0 and valid repo BG
#TEST-VAL-SUB026-7604#REF# FCT special value (balise header) Passage of BG with NID_BG=16383

#REQ-UNISIG-SUB026-3642#REF# to.7.5.1.85
If received a balisegroup with NID_BG=UNKNOWN, this defect shall be interpreted as a balise inconsistency for this balisegroup.
UNISIG clarification:
see description for special value. UNKNOWN cannot used in balise headers.
#TEST-VAL-SUB026-7604#REF# FCT basic function Passage of BG with NID_BG=16383

#REQ-UNISIG-SUB026-3402#REF# 7.5.1.86
NID_C (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7486#REF# ECT basic function Variablentest NID_C

#REQ-UNISIG-SUB026-008956#REF# 7.5.1.86.1
NID_CTRACTION (Values to be assigned according to 7.3.1.3)

TEST APPROACH:
Values will be verified for both receiving and sending situations.
#TEST-VAL-SUB026-7760#REF# BVA receiving Variable test NID_CTRACTION
#TEST-VAL-SUB026-7680#REF# BVA sending Varaibles M_VOLTAGE, NID_CTRACTION for sending case

#REQ-UNISIG-SUB026-008957#REF# 7.5.1.87
NID_EM

#TEST-VAL-SUB026-7487#REF# ECT basic function Variablentest NID_EM

#REQ-UNISIG-SUB026-008958#REF# 7.5.1.88
NID_ENGINE (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7502#REF# BVA maximal Variablentest Q_DANGERPOINT
#TEST-VAL-SUB026-7488#REF# BVA minimal Variable test NID_ENGINE

#REQ-UNISIG-SUB026-008959#REF# 7.5.1.89
NID_LOOP (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7489#REF# BVA basic function Variablentest NID_LOOP

#REQ-UNISIG-SUB026-008960#REF# 7.5.1.90
NID_LRBG

#TEST-VAL-SUB026-7490#REF# BVA basic function Variablentest NID_LRBG

#REQ-DESIGN-CR-0528#REF# 7.5.1.90.1
NID_LTRBG

#TEST-VAL-SUB026-5794#REF# FCT basic function Variable test NID_LTRBG

#REQ-UNISIG-SUB026-008961#REF# 7.5.1.90.2
NID_LX

UNISIG clarification: obu doesn't checked the keeping of the reserved ranges from the different transmission media
#TEST-VAL-SUB026-7655#REF# BVA basic function Variables NID_LX, L_LX, V_LX

#REQ-UNISIG-SUB026-008962#REF# 7.5.1.91
NID_MESSAGE

#TEST-VAL-SUB026-7491#REF# ECT basic function Variablentest NID_MESSAGE

#REQ-DESIGN-CR-0450#REF# 7.5.1.91.1
NID_MN (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7585#REF# FCT basic function Variablentest NID_MN

#REQ-UNISIG-SUB026-3406:01#REF# 7.5.1.92
NID_OPERATIONAL

TEST APPROACH:
Values will be verified for both receiving and sending situations.
#TEST-VAL-SUB026-7492#REF# BVA receiving Variable test NID_OPERATIONAL
#TEST-VAL-SUB026-8154#REF# BVA sending variable test NID_OPERATIONAL - sending side

#REQ-UNISIG-SUB026-008963#REF# 7.5.1.93
NID_PACKET

#TEST-VAL-SUB026-7493#REF# ECT basic function Variablentest NID_PACKET

#REQ-UNISIG-SUB026-3230#REF# 7.5.1.94
NID_PRVLRBG

#TEST-VAL-SUB026-7494#REF# ECT basic function Variablentest NID_PRVBG

#REQ-DESIGN-CR-0364#REF# 7.5.1.95
NID_RADIO (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7495#REF# ECT A-E, FFFFFFFFFFFFFFFF, min, max Variable test NID_RADIO
#TEST-VAL-SyAnfSpezCR-0061#REF# ECT F within number Variablentest NID_RADIO (CR)
#TEST-VAL-SyAnfSpezCR-0062#REF# ECT number terminated with F NID_RADIO 1122 3344 5566 77FF
#TEST-VAL-SUB026-7581#REF# ECT valid Onboard telephone numbers are sent to the RBC

#REQ-UNISIG-SUB026-3474#REF# 7.5.1.96
NID_RBC (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7496#REF# BVA basic function Variable test NID_RBC
#TEST-VAL-SUB026-7077#REF# EET error expectation Text message acknowledgment requested with RBC ETCS identity number = 16383

#REQ-UNISIG-SUB026-3475#REF# 7.5.1.97
NID_RIU (Values to be assigned according to 7.3.1.3)

Radio Infill isn't realized

variabel is used in P133 and 143 - both packets should be ignored

#REQ-UNISIG-SUB026-008013#REF# 7.5.1.98
NID_NTC (Values to be assigned according to 7.3.1.3)

replace NID_STM
TEST APPROACH:
Values will be verified for both receiving and sending situations.
#TEST-VAL-SUB026-7498#REF# BVA basic function Variable test NID_NTC

#REQ-UNISIG-SUB026-008964#REF# 7.5.1.98.1
NID_TEXTMESSAGE

TEST APPROACH:
Values will be verified for both receiving and sending situations.
#TEST-VAL-SUB026-7719#REF# BVA basic function Driver acknowledgement report together with the text message id is sent to the RBC when requested by trackside

#REQ-DESIGN-CR-0637#REF# 7.5.1.99
NID_TSR

UNISIG clarification: obu doesn't checked the reserved ranges from the different transmission media
#TEST-VAL-SUB026-7499#REF# BVA min, max Variablentest NID_TSR
#TEST-VAL-SUB026-3120#REF# BVA special value Non-revocable TSR

#REQ-UNISIG-SUB026-010588#REF# 7.5.1.99.1
NID_VBCMK

VBC function is not realized

=> P0/P200 is to be ignored without decoding

#REQ-UNISIG-SUB026-008965#REF# 7.5.1.100
NID_XUSER (Values to be assigned according to 7.3.1.3)

#TEST-VAL-SUB026-7500#REF# BVA basic function Variablentest NID_XUSER

#REQ-UNISIG-SUB026-008025#REF# 7.5.1.101
Q_ASPECT

#TEST-VAL-SUB026-4013#REF# FCT basic function Baliseninformation 'Stop if in Shunting'

#REQ-UNISIG-SUB026-008028#REF# 7.5.1.101.1
Q_CONFTEXTDISPLAY

#TEST-VAL-SUB026-7715#REF# ECT 0, 1 Driver acknowledgement taken into account for text message display end condition

#REQ-UNISIG-SUB026-008031#REF# 7.5.1.102
Q_DANGERPOINT

#TEST-VAL-SUB026-7502#REF# BVA basic function Variablentest Q_DANGERPOINT

#REQ-UNISIG-SUB026-008034#REF# 7.5.1.102.1
Q_DIFF

#TEST-VAL-SUB026-5878#REF# ECT 3 (spare) Reception of spare value for Q_DIFF
#TEST-VAL-SUB026-5872#REF# ECT 0, 1, 2 Variable test Q_DIFF

#REQ-UNISIG-SUB026-008037#REF# 7.5.1.103
Q_DIR

#TEST-VAL-SUB026-3037#REF# FCT 2 Q_DIR-Test single balise BG(mit Q_LINK=1)
#TEST-VAL-SUB026-3333#REF# FCT 3 , CFX00034882 Reaktion auf Q_DIR=3
#TEST-VAL-SUB026-3036#REF# FCT 0, 1 Processing information from different transmission sources in relation to Q_DIR
#TEST-VAL-SUB026-3112#REF# EET CFX00036350 Conditional emergency message, min safe front hasn't passed new stop location
#TEST-VAL-SUB026-5845#REF# EET CFX00036350 START/STOP TAF request

#REQ-UNISIG-SUB026-008040#REF# 7.5.1.104
Q_DIRLRBG

#TEST-VAL-SUB026-7504#REF# ECT basic function Variable test Q_DIRLRBG, Q_DIRTRAIN, Q_DLRBG

#REQ-UNISIG-SUB026-008043#REF# 7.5.1.105
Q_DIRTRAIN

#TEST-VAL-SUB026-7504#REF# ECT basic function Variable test Q_DIRLRBG, Q_DIRTRAIN, Q_DLRBG

#REQ-UNISIG-SUB026-008046#REF# 7.5.1.106
Q_DLRBG

#TEST-VAL-SUB026-7504#REF# ECT basic function Variable test Q_DIRLRBG, Q_DIRTRAIN, Q_DLRBG
#TEST-VAL-SUB026-7601#REF# EET error expectation PR (pkt0) - active cab A/B - one antenna for each cab configured
#TEST-VAL-SUB026-7602#REF# EET error expectation PR (pkt0) - one antenna for each cab configured - change cab above BG

#REQ-UNISIG-SUB026-008049#REF# 7.5.1.107 #ANA-UNISIG-EmergencyMessage-0007#REF#
Q_EMERGENCYSTOP

UNISIG clarification:
the case "UES is rejected"
cannot occur - see analysis
TEST APPROACH:
There is no condition which leads to the sending of Q_EMERGENCYSTOP=3 as response to a unconditional emergency stoop message.
The verification of Q_EMERGENCYSTOP=3 as response to a unconditional emergency stoop message is hence omitted.
#TEST-VAL-SUB026-3719#REF# BVA 2 Reception of several Unconditional Emergency Stop with same ID
#TEST-VAL-SUB026-3718#REF# BVA 0, 1, 3 Reception of several Conditional Emergency Stop with same ID

#REQ-UNISIG-SUB026-008052#REF# 7.5.1.108
Q_ENDTIMER

#TEST-VAL-SUB026-7508#REF# ECT basic function Variablentest Q_ENDTIMER

#REQ-DESIGN-CR-0619#REF# 7.5.1.109
Q_FRONT

#TEST-VAL-SUB026-3116#REF# ECT basic function Effect of Q_FRONT (P27, P51, P65)

#REQ-UNISIG-SUB026-008058#REF# 7.5.1.110
Q_GDIR

TEST APPROACH:
The following aspects were identified (Q_GDIR is a part of the following packets):
1) Packet 141: Default gradient for TSR
2) Packet 21: Gradient profile
3) Packet 52: Permitted braking distance
#TEST-VAL-SUB026-3122#REF# ECT 1 default gradient for TSR
#TEST-VAL-SUB026-7510#REF# ECT 2 Variable test Q_GDIR
#TEST-VAL-SUB026-3A66#REF# ECT 3 Q_GDIR in Packet 52 (PBD Information)

#REQ-UNISIG-SUB026-008966#REF# 7.5.1.111
Q_INFILL


#REQ-UNISIG-SUB026-008064#REF# 7.5.1.112
Q_LENGTH

TEST APPROACH:
The appropriated L3 feature train integrity is not supported in R8.0 so the value has to be set to 0.
#TEST-VAL-SUB026-5283#REF# FCT basic function Setting of Q_LENGTH in various situation

#REQ-UNISIG-SUB026-008070#REF# 7.5.1.113
Q_LGTLOC

#TEST-VAL-SUB026-7513#REF# ECT basic function Variable test Q_LGTLOC

#REQ-UNISIG-SUB026-008073#REF# 7.5.1.114
Q_LINK

#TEST-VAL-SUB026-3011#REF# ECT basic function mit Linking-Info werden unlinked und linked+in_Info BGs akzeptiert

#REQ-DESIGN-CR-0600#REF# 7.5.1.115
Q_LOCACC

#TEST-VAL-SUB026-7515#REF# BVA basic function Variablentest Q_LOCACC

#REQ-UNISIG-SUB026-008079#REF# 7.5.1.116
Q_LINKORIENTATION

#TEST-VAL-SUB026-7516#REF# ECT basic function Variablentest Q_LINKORIENTATION

#REQ-UNISIG-SUB026-008082#REF# 7.5.1.117
Q_LINKREACTION

TEST APPROACH:
The following aspects were identified:
0) Q_LINKREACTION = 0 (Train trip)
1) Q_LINKREACTION = 1 (apply SB)
2) Q_LINKREACTION = 2 (no reaction)
#TEST-VAL-SUB026-5907#REF# ECT 1 A3.4.1.2 h Track condition big metal masses
#TEST-VAL-SUB026-3441#REF# ECT 2 table of priority - unchanged A.3.4.1.2 h, l
#TEST-VAL-SUB026-4559#REF# ECT 0 Mode transition LS->TR[17]

#REQ-UNISIG-SUB026-008085#REF# 7.5.1.118
Q_LOOPDIR

#TEST-VAL-SUB026-7518#REF# ECT basic function Variable test Q_LOOPDIR

#REQ-UNISIG-SUB026-008088#REF# 7.5.1.118.1 #REQ-UNISIG-SUB026-002294#REF#
Q_LXSTATUS

#TEST-VAL-SUB026-7645#REF# BVA basic function LX supervision is stopped when LX becomes protected

#REQ-UNISIG-SUB026-008091#REF# 7.5.1.118.2
Q_MAMODE

#TEST-VAL-SUB026-5763#REF# FCT EoA != SvL Start of OS area supervision
#TEST-VAL-SUB026-5924#REF# FCT EoA = SvL Variable test Q_MAMODE
#TEST-VAL-SUB026-5925#REF# FCT LoA Variable test Q_MAMODE

#REQ-UNISIG-SUB026-008967#REF# 7.5.1.118.3
Q_MARQSTREASON

Rel. 8.0:
replaces Q_TRACKDEL
#TEST-VAL-SUB026-4E29#REF# FCT 1xxxx MA Request when passing BG with Track Ahead Free up to level 2/3 transition location
#TEST-VAL-SUB026-4E24#REF# FCT x1xxx MA request sent when RAMS supervision led to a service brake and train reaches standstill
#TEST-VAL-SUB026-4E30#REF# FCT xx1xx MA-Requests according to T_TIMEOUTRQST
#TEST-VAL-SUB026-4E28#REF# FCT xxx1x MA-Requests according to T_MAR
#TEST-VAL-SUB026-4E26#REF# FCT xxxx1 MA request sent when driver selects Start

#REQ-UNISIG-SUB026-008097#REF# 7.5.1.119
Q_MEDIA

#TEST-VAL-SUB026-3105#REF# ECT basic function Acceptance of the loop information after passing the EOLM

#REQ-DESIGN-CR-0164#REF# 7.5.1.120
Q_MPOSITION

#TEST-VAL-SUB026-3057#REF# FCT basic function Geographical position

#REQ-UNISIG-SUB026-008103#REF# 7.5.1.121
Q_NEWCOUNTRY

#TEST-VAL-SUB026-7521#REF# ECT basic function Variable test Q_NEWCOUNTRY

#REQ-UNISIG-SUB026-008106#REF# 7.5.1.122
Q_NVDRIVER_ADHES

#TEST-VAL-SUB026-3223#REF# BVA basic function Variablentest Q_NVDRIVER_ADHES

#REQ-UNISIG-SUB026-007592#REF# 7.5.1.123
Q_NVEMRRLS

#TEST-VAL-SUB026-3231#REF# ECT basic function Variable test Q_NVEMRRLS

#REQ-UNISIG-SUB026-007589#REF# 7.5.1.123.1 #REQ-UNISIG-SUB026-007049#REF#
Q_NVGUIPERM

#TEST-VAL-SUB026-5628#REF# FCT basic function Variable test Q_NVGUIPERM

#REQ-UNISIG-SUB026-008096#REF# 7.5.1.123.2
Q_NVINHSMICPERM

#TEST-VAL-SUB026-5630#REF# ECT basic function Variable test Q_NVINHSMICPERM

#REQ-UNISIG-SUB026-007580#REF# 7.5.1.123.3 #REQ-UNISIG-SUB026-007058#REF#
Q_NVKINT

#TEST-VAL-SUB026-5619#REF# BVA basic function P203 - valid packet structure

#REQ-UNISIG-SUB026-007581#REF# 7.5.1.123.4
Q_NVKVINTSET

#TEST-VAL-SUB026-5636#REF# FCT basic function Variable test Q_NVKVINTSET

#REQ-UNISIG-SUB026-008124#REF# 7.5.1.123.5
Q_NVLOCACC

#TEST-VAL-SUB026-5838#REF# FCT basic function Variable test Q_NVLOCACC

#REQ-UNISIG-SUB026-007590#REF# 7.5.1.123.6 #REQ-UNISIG-SUB026-007050#REF#
Q_NVSBFBPERM

#TEST-VAL-SUB026-5629#REF# ECT basic function Variable test Q_NVSBFBPERM

#REQ-UNISIG-SUB026-007593#REF# 7.5.1.124 #REQ-UNISIG-SUB026-007045#REF#
Q_NVSBTSMPERM

#TEST-VAL-SUB026-3230#REF# ECT basic function Variable test Q_NVSBTSMPERM

#REQ-UNISIG-SUB026-008133#REF# 7.5.1.125
Q_ORIENTATION

#TEST-VAL-SUB026-7525#REF# FCT basic function Variablentest Q_ORIENTATION

#REQ-UNISIG-SUB026-008136#REF# 7.5.1.126
Q_OVERLAP

#TEST-VAL-SUB026-7526#REF# ECT basic function Variablentest Q_OVERLAP

#REQ-UNISIG-SUB026-008139#REF# 7.5.1.126.1
Q_PBDSR

#TEST-VAL-SUB026-4B99#REF# ECT basic function test variable Q_PBDSR

#REQ-UNISIG-SUB026-008142#REF# 7.5.1.126.2
Q_PLATFORM

P69 is ignored without decoding, because TC Station Platform isn't realized. 
So this information doesn't needed.

#REQ-UNISIG-SUB026-008145#REF# 7.5.1.127
Q_RBC

#TEST-VAL-SUB026-7527#REF# ECT basic function Variable test Q_RBC

#REQ-UNISIG-SUB026-008148#REF# 7.5.1.128
Q_RIU

Radio Infill isn't realized

variable is used in P133 and 143 - both packets should be ignored
TEST APPROACH:
Packet 143 (Session Management with neighbouring Radio Infill Unit) has to be evaluated from RIU only. A
session to a RIU can not be established as Packet 133 (Radio-infill Area Information) is ignored.

#REQ-UNISIG-SUB026-008151#REF# 7.5.1.129
Q_SCALE

#TEST-VAL-SUB026-7529#REF# ECT basic function Variablentest Q_SCALE

#REQ-UNISIG-SUB026-008154#REF# 7.5.1.130
Q_SECTIONTIMER

#TEST-VAL-SUB026-7530#REF# ECT basic function Variablentest Q_SECTIONTIMER

#REQ-UNISIG-SUB026-3411#REF# 7.5.1.131
Q_SLEEPSESSION

TEST APPROACH:
The following aspects have been identified:
1) P42
1.1) Q_SLEEPSESSION = 0
1.2) Q_SLEEPSESSION = 1
2) P131
2.1) Q_SLEEPSESSION = 0
2.2) Q_SLEEPSESSION = 1
#TEST-VAL-SUB026-7531#REF# FCT 1.1, 1.2 Variable test Q_SLEEPSESSION
#TEST-VAL-SUB026-4158#REF# FCT 2.1 SL: two mobile RBC transition order with Q_SLEEPSESSION=0, without session
#TEST-VAL-SUB026-8230#REF# FCT 2.2 Reception of P131 with Q_SLEEPSESSION = 1

#REQ-UNISIG-SUB026-008160#REF# 7.5.1.132
Q_SRSTOP

#TEST-VAL-SUB026-7532#REF# ECT basic function Variablentest Q_SRSTOP

#REQ-UNISIG-SUB026-008163#REF# 7.5.1.133
Q_SSCODE

#TEST-VAL-SUB026-7533#REF# BVA basic function Variable test Q_SSCODE

#REQ-UNISIG-SUB026-008166#REF# 7.5.1.134
Q_STATUS

#TEST-VAL-SUB026-7534#REF# ECT 1, 2 Variablentest Q_STATUS
#TEST-VAL-SUB026-4210#REF# EET 0 SoM Stored position not confirmed by RBC -> data deleted

#REQ-UNISIG-SUB026-008169#REF# 7.5.1.134.1
Q_STOPLX

#TEST-VAL-SUB026-7146#REF# ECT basic function Supervision of the LX start location (Q_STOPLX=0)

#REQ-UNISIG-SUB026-008172#REF# 7.5.1.135
Q_SUITABILITY

#TEST-VAL-SUB026-7535#REF# BVA basic function Variablentest Q_SUITABILITY

#REQ-UNISIG-SUB026-008175#REF# 7.5.1.136 #ANA-UNISIG-TextMessages-0002:01#REF#
Q_TEXT

UNISIG clarification:
The restriction to the 2 special values is not clear, especially the spare definition. 
Realization: EVC transmits the Q_TEXT ID to DMI. There is defined the text string.
--- FINALISED ---
EVC accepts all values of the variable Q_TEXT and transmits this value to DMI (see REQ-FFFIS_MMI-006056).
The special values for Q_TEXT are defined in #DSC-FFFIS_MMI-006101#REF# as a part of REQ-FFFIS_MMI-006056.
realised by: #REQ-UNISIG-SUB026-010301#REF#

#REQ-UNISIG-SUB026-010301#REF# 7.5.1.136 #REQ-UNISIG-SUB026-008175#REF#
Q_TEXT

EVC transmits the Q_TEXT ID to DMI. There is defined the text string.
#TEST-VAL-SUB026-7536#REF# ECT basic function Variablentest Q_TEXT

#REQ-UNISIG-SUB026-008178#REF# 7.5.1.137
Q_TEXTCLASS

#TEST-VAL-SUB026-7537#REF# ECT basic function Variable test Q_TEXTCLASS

#REQ-UNISIG-SUB026-3345#REF# 7.5.1.138
Q_TEXTCONFIRM

#TEST-VAL-SUB026-3761#REF# FCT 2, 3 P72/76 Q_TEXTCONFIRM 3/2
#TEST-VAL-SUB026-4379#REF# FCT 0, 1 text message SR->FS

#REQ-UNISIG-SUB026-008184#REF# 7.5.1.139
Q_TEXTDISPLAY

#TEST-VAL-SUB026-7612#REF# ECT 1 Evaluation of start/stop condition for plain text message with Q_TEXTDISPLAY = 1
#TEST-VAL-SUB026-8301#REF# ECT 0 Q_TEXTDISPLAY = 0

#REQ-UNISIG-SUB026-008187#REF# 7.5.1.140
Q_TEXTREPORT

#TEST-VAL-SUB026-7791#REF# ECT basic function Driver acknowledgement report together with the text message id is sent to the RBC when requested by trackside

#REQ-UNISIG-SUB026-008190#REF# 7.5.1.141
Q_TRACKINIT

#TEST-VAL-SUB026-7788#REF# ECT basic function Q_TRACKINIT =1, D_TRACKINIT the same as D_TRACKCOND of former TC

#REQ-UNISIG-SUB026-008193#REF# 7.5.1.142
Q_UPDOWN

#TEST-VAL-SUB026-7542#REF# ECT basic function Variablentest Q_UPDOWN

#REQ-UNISIG-SUB026-008194#REF# 7.5.1.142.1
Q_VBCO

VBC function is not realized

=> P0/P200 is to be ignored without decoding

#REQ-UNISIG-SUB026-008196#REF# 7.5.1.143
T_CYCLOC

#TEST-VAL-SUB026-7543#REF# BVA basic function Variable test T_CYCLOC

#REQ-DESIGN-CR-0580:01#REF# to.7.5.1.143 #ANA-UNISIG-ETCSLanguage-0006#REF#
T_CYCLOC
If received a value less then 2 seconds, the value 2 seconds shall be used.
#TEST-VAL-SUB026-7543#REF# FCT basic function Variable test T_CYCLOC

#REQ-UNISIG-SUB026-008199#REF# 7.5.1.144
T_CYCRQST

#TEST-VAL-SUB026-7544#REF# BVA basic function Variablentest T_CYCRQST

#REQ-DESIGN-CR-0582:01#REF# to.7.5.1.144 #ANA-UNISIG-ETCSLanguage-0006#REF#
T_CYCRQST
If received a value less then 2 seconds, the value 2 seconds shall be used.
#TEST-VAL-SUB026-7544#REF# FCT basic function Variablentest T_CYCRQST

#REQ-UNISIG-SUB026-008202#REF# 7.5.1.145
T_ENDTIMER

#TEST-VAL-SUB026-7545#REF# BVA basic function , CFX00040095 Variable test T_ENDTIMER

#REQ-UNISIG-SUB026-008205#REF# 7.5.1.146
T_LOA

#TEST-VAL-SUB026-7546#REF# ECT basic function Variablentest T_LOA

#REQ-UNISIG-SUB026-3081#REF# 7.5.1.147
T_MAR

#TEST-VAL-SUB026-7547#REF# BVA basic function Variablentest T_MAR

#REQ-UNISIG-SUB026-008211#REF# 7.5.1.148
T_NVCONTACT

#TEST-VAL-SUB026-5258#REF# BVA basic function Variable test T_NVCONTACT

#REQ-UNISIG-SUB026-006960#REF# to.7.5.1.148 #ANA-UNISIG-ETCSLanguage-0006#REF#
T_NVCONTACT
If received a value less then 2 seconds, the value 2 seconds shall be used.
#TEST-VAL-SUB026-5258#REF# FCT basic function Variable test T_NVCONTACT

#REQ-UNISIG-SUB026-008214#REF# 7.5.1.149
T_NVOVTRP

#TEST-VAL-SUB026-3235#REF# BVA basic function Variablentest T_NVOVTRP

#REQ-UNISIG-SUB026-008217#REF# 7.5.1.150
T_OL

#TEST-VAL-SUB026-7550#REF# ECT basic function Variablentest T_OL

#REQ-UNISIG-SUB026-008220#REF# 7.5.1.151
T_SECTIONTIMER

#TEST-VAL-SUB026-7551#REF# ECT basic function Variablentest T_SECTIONTIMER

#REQ-UNISIG-SUB026-008223#REF# 7.5.1.152
T_TEXTDISPLAY

#TEST-VAL-SUB026-7552#REF# ECT basic function Variablentest T_TEXTDISPLAY

#REQ-UNISIG-SUB026-3082#REF# 7.5.1.153
T_TIMEOUTRQST

#TEST-VAL-SUB026-7553#REF# BVA basic function Variablentest T_TIMEOUTRQST

#REQ-UNISIG-SUB026-008229#REF# 7.5.1.154
T_TRAIN

#TEST-VAL-SUB026-3913#REF# BVA min Usage of message timeStamp sent as normal/priority radio data
#TEST-VAL-SUB026-3775#REF# BVA unknown (accepted) T_NVCONTACT supervision M_NVCONTAC=1
#TEST-VAL-SUB026-7554#REF# BVA valid, max, unknown (rejected) Variable test T_TRAIN

#REQ-UNISIG-SUB026-008230#REF# 7.5.1.154.1
T_VBC

VBC function is not realized

=> P0/P200 is to be ignored without decoding

#REQ-UNISIG-SUB026-008231#REF# to.7.5.1.154.1
clarification to the resolution of T_VBC:
1 day shall be interpreted with 24 hours after receipt of information.
0 day shall be interpreted as Virtual Balise Cover is immediately invalid.
UNISIG clarification: a clarification of the use of the day resolution is necessary

VBC function is not realized

#REQ-UNISIG-SUB026-008232#REF# 7.5.1.155
V_AXLELOAD

#TEST-VAL-SUB026-7555#REF# BVA basic function Variable test V_AXLELOAD

#REQ-UNISIG-SUB026-008235#REF# 7.5.1.156
V_DIFF

#TEST-VAL-SUB026-7556#REF# ECT basic function Variable test V_DIFF

#REQ-UNISIG-SUB026-008238#REF# 7.5.1.157
V_LOA

#TEST-VAL-SUB026-7557#REF# BVA basic function Variable test V_LOA

#REQ-UNISIG-SUB026-008241#REF# 7.5.1.157.1
V_LX

#TEST-VAL-SUB026-7655#REF# BVA basic function Variables NID_LX, L_LX, V_LX

#REQ-UNISIG-SUB026-008244#REF# 7.5.1.158
V_MAIN

#TEST-VAL-SUB026-7558#REF# ECT basic function Variable test V_MAIN

#REQ-UNISIG-SUB026-008247#REF# 7.5.1.159
V_MAMODE

#TEST-VAL-SUB026-7559#REF# ECT basic function Variable test V_MAMODE

#REQ-UNISIG-SUB026-3231#REF# 7.5.1.160
V_MAXTRAIN

#TEST-VAL-SUB026-7560#REF# BVA basic function Variablentest V_MAXTRAIN

#REQ-UNISIG-SUB026-3232#REF# 7.5.1.161
V_NVALLOWOVTRP

#TEST-VAL-SUB026-3232#REF# BVA basic function Variablentest V_NVALLOWOVTRP

#REQ-UNISIG-SUB026-007583#REF# 7.5.1.161.1 #REQ-UNISIG-SUB026-007058#REF#
V_NVKVINT

#TEST-VAL-SUB026-5638#REF# BVA basic function Variable test V_NVKVINT

#REQ-UNISIG-SUB026-3346#REF# 7.5.1.161.2
V_NVLIMSUPERV

#TEST-VAL-SUB026-5868#REF# BVA basic function Variable test V_NVLIMSUPERV

#REQ-UNISIG-SUB026-3357#REF# 7.5.1.162
V_NVONSIGHT

#TEST-VAL-SUB026-3226#REF# BVA basic function Variablentest V_NVONSIGHT

#REQ-UNISIG-SUB026-3233#REF# 7.5.1.163
V_NVSUPOVTRP

#TEST-VAL-SUB026-3233#REF# BVA basic function Variablentest V_NVSUPOVTRP

#REQ-UNISIG-SUB026-3234#REF# 7.5.1.164 #REQ-UNISIG-SUB026-007057#REF#
V_NVREL

#TEST-VAL-SUB026-3228#REF# BVA basic function Variable test V_NVREL

#REQ-UNISIG-SUB026-3235#REF# 7.5.1.165
V_NVSHUNT

#TEST-VAL-SUB026-3224#REF# BVA basic function Variablentest V_NVSHUNT

#REQ-UNISIG-SUB026-3236#REF# 7.5.1.166
V_NVSTFF

#TEST-VAL-SUB026-3225#REF# BVA basic function Variablentest V_NVSTFF

#REQ-UNISIG-SUB026-3237#REF# 7.5.1.167
V_NVUNFIT

#TEST-VAL-SUB026-3227#REF# BVA basic function Variablentest V_NVUNFIT

#REQ-UNISIG-SUB026-008280#REF# 7.5.1.168
V_RELEASEDP

#TEST-VAL-SUB026-7568#REF# BVA basic function Variable test V_RELEASEDP

#REQ-UNISIG-SUB026-008283#REF# 7.5.1.169
V_RELEASEOL

#TEST-VAL-SUB026-7569#REF# BVA basic function Variable test V_RELEASEOL

#REQ-UNISIG-SUB026-3238#REF# 7.5.1.170
V_REVERSE

#TEST-VAL-SUB026-7570#REF# BVA basic function Variable test V_REVERSE

#REQ-UNISIG-SUB026-008289#REF# 7.5.1.171
V_STATIC

#TEST-VAL-SUB026-7571#REF# BVA basic function Variable test V_STATIC

#REQ-DESIGN-CR-0146#REF# 7.5.1.172
V_TRAIN

#TEST-VAL-SUB026-7572#REF# BVA basic function Variablentest V_TRAIN

#REQ-UNISIG-SUB026-008295#REF# 7.5.1.173
V_TSR

#TEST-VAL-SUB026-7573#REF# BVA basic function Variable test V_TSR

#REQ-UNISIG-SUB026-008298#REF# 7.5.1.174
X_TEXT

#TEST-VAL-SUB026-7574#REF# BVA basic function Variablentest X_TEXT

Chapter 8

TEST APPROACH:
Note: The track description is verified via a mode independent test interface if not stated otherwise.
		

Chapter 8.4

TEST APPROACH:
The acceptance of information according to the defined rules is realized centrally by the software module packet handler (PH). 
The requirements are thoroughly tested by PH module verification.
The quality of the module tests is ensured by review of the module test specification and test implementation as part of the module review. The
result of the review is documented in /ESBO_UUE/ --> reference ID ESBO_VerBer.

The scope of the integration test is to verify the processing of the information by the OBU and the verification of error reactions.
		
#REQ-UNISIG-SUB026-0366#REF# 8.4.1.3.1
Exception for Infill information: The locations given in the packets following packet 136 (Infill Location Reference) shall be referred to the
balise group indicated in such packet.
is the same definition as 3.6.2.3.1
realised by: #REQ-UNISIG-SUB026-0015#REF#

#REQ-UNISIG-SUB026-3125:02#REF# to.8.4.1.3.1 #ANA-UNISIG-Chapter8-0001:01#REF#
Infill information without a location reference shall be used with the location at the time of the evaluation.
TEST APPROACH:
The following aspects have been identified, taking into account the rules related to information which can be transmitted as infill information
(see #REQ-UNISIG-SUB040-001202:01#REF#):
1) P44 - Data used by applications outside the ERTMS/ETCS system
2) P66 - Temporary Speed Restriction Revocation
3) P49 - List of balises for SH Area
#TEST-VAL-SUB026-8057#REF# FCT 1 In-fill P44 is used immediately
#TEST-VAL-SUB026-8053#REF# FCT 2 In-fill TSR revocation is applied immediately
#TEST-VAL-SUB026-7858#REF# FCT 3 Infill 'List of balises for SH area' is applied immediately

#REQ-UNISIG-SUB026-2164#REF# 8.4.1.4
It shall be forbidden to send more instances of the same packet type for the same direction in the same message.
#TEST-VAL-SUB026-8009#REF# ECT basic function same packets type for the same direction in the same message

#REQ-UNISIG-SUB026-0367#REF# 8.4.1.4.1
Exception 1: A message can contain several packets 44 (Data used by applications outside the ERTMS/ETCS system).
realised by: #REQ-UNISIG-SUB026-3126#REF#

#REQ-UNISIG-SUB026-3026#REF# 8.4.1.4.2 #ANA-UNISIG-TSR-0001#REF#
Exception 2: A message can contain several packets 65 (Temporary Speed Restriction). In case of revocable TSRs, the identities of the
corresponding temporary speed restrictions (variable NID_TSR) transmitted in the same message shall be different.
The second part is only relevant for trackside
realised by: #REQ-UNISIG-SUB026-3126#REF#

#REQ-UNISIG-SUB026-3027#REF# 8.4.1.4.3 #ANA-UNISIG-TSR-0001#REF#
Exception 3: A message can contain several packets 66 (TSR Revocation). The identities of the corresponding temporary speed restrictions
(variable NID_TSR) transmitted in the same message shall be different.
The second part is only relevant for trackside
realised by: #REQ-UNISIG-SUB026-3126#REF#

#REQ-UNISIG-SUB026-3126#REF# to.8.4.1.4 #REQ-UNISIG-SUB026-0367#REF#
#REQ-UNISIG-SUB026-3026#REF#
#REQ-UNISIG-SUB026-3027#REF#
#ANA-UNISIG-TSR-0001#REF#
#ANA-UNISIG-Chapter8-0002:01#REF#
Exception to 8.4.1.4.1-3:
A message can contain several
- packets 44 (Data used by applications outside the ERTMS/ETCS system)
- packets 65 (Temporary Speed Restriction)
- packets 66 (TSR Revocation).

remark: This applies both to non infill and infill information.
TEST APPROACH:
The following aspects have been identified:
1) packets transmitted as non-infill information
1.1) P44
1.2) P65
1.3) P66
2) packets transmitted as infill information
For each case, the following aspects are identified:
2.1) P44
2.2) P65
2.3) P66
#TEST-VAL-SUB026-8060#REF# FCT 1.1 , CFX00039445 Several P44 in one BG message
#TEST-VAL-SUB026-3471#REF# FCT 1.2 RBC sends several non-revocable speed restriction in one message
#TEST-VAL-SUB026-8043#REF# FCT 1.3 Multiple TSR Revocations in a message
#TEST-VAL-SUB026-7977#REF# FCT 2.1 Several P44 in one BG message (infill)
#TEST-VAL-SUB026-8051#REF# FCT 2.3 Temporary Speed Restriction Revocation and Infill location reference
#TEST-VAL-SUB026-8050#REF# EET CFX00038337 , 2.2 TSR and Infill location reference
#TEST-VAL-SUB026-3472#REF# EET error expectation RBC sends several revocable speed restriction with same id in one message

#REQ-UNISIG-SUB026-3114#REF# to.8.4.1.4 #ANA-UNISIG-TSR-0002#REF#
Maximum number of packet 65 or 66 in one message: 30
ergibt sich aus der Anzahl der zu speichernden TSR aus Subset 40.
#TEST-VAL-SUB026-8052#REF# FCT basic function Message with 30 TSR and messge with 30 Revocation of TSR

#REQ-UNISIG-SUB026-3115#REF# to.8.4.1.4 #ANA-UNISIG-TSR-0002#REF#
If received more than the maximum number of packet 65 or 66 in one message, obu shall assess it as a data inconsistency.
#TEST-VAL-SUB026-8055#REF# FCT P65 More than the max number of packet 65 in one message is assessed as data inconsistency
#TEST-VAL-SUB026-8056#REF# FCT P66 More than the max number of packet 66 in one message is assessed as data inconsistency

#REQ-DESIGN-CR-0105#REF# 8.4.1.4.4
Exception 4: A message transmitted by a balise group can contain one packet 136 per balise telegram per direction. Each packet 136 indicates
which part of that telegram is to be considered as part of the infill information. Multiple packets 136 in balises of a balise group shall have
identical content per direction.
TEST APPROACH:
The following aspects have been identified:
1) Multiple P136 in one BG
1.1) All with same infill location reference
1.2) With different infill location reference
2) Multiple P136 in one balise 
2.1) different direction
2.2) same direction
#TEST-VAL-SyAnfSpezCR-0014#REF# FCT 1.1 Infill Location Reference
#TEST-VAL-SUB026-8045#REF# FCT 1.2, 2.2 Multiple Infill location reference (pkt 136) in a message with same direction
#TEST-VAL-SUB026-8044#REF# FCT 2.1 Multiple Infill location reference (pkt 136) in a message
#TEST-VAL-SUB026-7101#REF# EET CFX00032279 Infillpacket 136 Defensivemaßnahme gegen Streckenprojektierungsfehler

#REQ-UNISIG-SUB026-008415#REF# 8.4.1.4.5
Exception 5: A message can contain several packets 88 (Level Crossing information). The identities of the corresponding Level Crossings
(variable NID_LX) transmitted in the same message shall be different.
UNISIG clarification:
The second part is an requirement for trackside. OBU realizes 3.12.5.3
realised by: #REQ-UNISIG-SUB026-010143#REF#

#REQ-UNISIG-SUB026-010143#REF# 8.4.1.4.5 #REQ-UNISIG-SUB026-008415#REF#
#ANA-UNISIG-Chapter8-0002:01#REF#
Exception 5: A message can contain several packets 88 (Level Crossing information).

remark: This applies both to non infill and infill information.
TEST APPROACH:
The following aspects have been identified:
1) packets transmitted as non-infill information 
2) packets transmitted as infill information
#TEST-VAL-SUB026-7655#REF# FCT 1 Variables NID_LX, L_LX, V_LX
#TEST-VAL-SUB026-7978#REF# FCT 2 Several P88 in one BG message (infill)

#REQ-DESIGN-CR-0485#REF# 8.4.1.4.6
Exception 6: A message transmitted by a balise group can contain several packets 254 (default balise, loop or RIU information).
#TEST-VAL-SUB026-8042#REF# FCT basic function Repetition of packet 254 in a balise group message

#REQ-UNISIG-SUB026-008419#REF# 8.4.1.4.7
Exception 7: A message transmitted by a balise group can contain several packets 145 (Inhibition of balise group message consistency reaction).
#TEST-VAL-SUB026-5863#REF# FCT basic function Balise group containing several packets 145

#REQ-UNISIG-SUB026-010563#REF# 8.4.1.4.8
Exception 8: A message transmitted by a balise group can contain several packets 0 (Virtual Balise Cover marker).
realised by: #REQ-UNISIG-SUB026-010565#REF#

#REQ-UNISIG-SUB026-010565#REF# to.8.4.1.4.8 #REQ-UNISIG-SUB026-007262#REF#
#REQ-UNISIG-SUB026-010363#REF#
#REQ-UNISIG-SUB026-010563#REF#
A message transmitted by a balise group can contain several information "Virtual Balise Cover marker" (packets 0 or 200).
The extension arises from 6.6.3.1.1 and 6.5.1.6.2

VBC function is not realized
=>P0/200 are ignored
TEST APPROACH:
The following aspects have been identified:
1) P0
1.1) multiple P0 with all vbcIDs stored on-board
1.2) multiple P0 with all vbcIDs not stored on-board
1.3) multiple P0 with vbcIDs stored and not stored on-board
2) P200
2.1) multiple P200 with all vbcIDs stored on-board
2.2) multiple P200 with all vbcIDs not stored on-board
2.3) multiple P200 with vbcIDs stored and not stored on-board

#REQ-UNISIG-SUB026-010564#REF# 8.4.1.4.9
Exception 9: A message transmitted by a balise group can contain several packets 6 (Virtual Balise Cover order). The identities (pairs of
variables NID_VBCMK and NID_C) of the corresponding VBC transmitted in the same message shall be different.
UNISIG clarification:
The second part is an requirement for trackside. OBU realizes 3.15.9.4
realised by: #REQ-UNISIG-SUB026-008420#REF#

#REQ-UNISIG-SUB026-008420#REF# to.8.4.1.4.9 #REQ-UNISIG-SUB026-010564#REF#
#ANA-UNISIG-Chapter8-0002:01#REF#
Exception 9: A message transmitted by a balise group can contain several packets 6 (Virtual Balise Cover order).
VBC function is not realized
=>P6 is ignored

#REQ-UNISIG-SUB026-008422#REF# to.8.4.1
rule on rounding for information to trackside
The information, which to be sent to trackside, shall be rounded to the safe side.

This affects the length, distance and speed information.

exception: This rule is not valid for P44 information.
UNISIG clarification: a clarification is necessary, especially for the speed information (resolution 5 km/h)
TEST APPROACH:
The requirement is valid for D_LRBG,  L_DOUBTOVER, L_DOUBTUNDER, L_TRININT, V_TRAIN part of  Position Report and L_TRAIN, V_MAXTRAIN part of
Validated train data.
The resolution of the parameterized train length and max train speed agree with the resolution of L_TRAIN and V_MAXTRAIN.  The feature Train
Integrity is not part of R8 L_TRINT is hence not relevant. 
The P44 content is transparent to the OBU as far as UNISIG is concered no verification takes palce here.
The verification is limited to D_LRBG,	L_DOUBTOVER, L_DOUBTUNDER and V_TRAIN.
Rounding to the safe side implies to a higher value for these parameter. 
1) D_LRBG 
2) L_DOUBTOVER 
3) L_DOUBTUNDER
4) V_TRAIN
#TEST-VAL-SUB026-7857#REF# FCT 1, 2, 3 Rule on rounding for information to trackside
#TEST-VAL-SUB026-3666#REF# FCT 4 Train Location Information - list of LRBGs (N_TOTAL !=0)

#REQ-UNISIG-SUB026-0368:02#REF# 8.4.2.1
The format of the telegram to be transmitted by each balise is as follows:


Number of bits in balise header: 50
Rel. 8.0:
packet 255 is now a component of the general balise telegram format
#ANALYSE-VALUNISIG-4769#REF# FCT The telegram coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-8038#REF# EET CFX00039813 Inconsistency in BG-Header (Q_UPDOWN, M_VERSION, Q_MEDIA, Q_LINK)
#TEST-VAL-SUB026-8000#REF# EET error expectation Inconsistency in BG header (N_TOTAL, N_PIG, NID_C, NID_BG)
#TEST-VAL-SUB026-8011#REF# EET error expectation Paket 255 fehlt / an falscher Stelle in Balise

#REQ-UNISIG-SUB026-3733#REF# to.8.4.2.1 #ANA-UNISIG-Baliseheader-0001#REF#
A balise group shall be defined as unlinked when the value Q_LINK is different in the separate balise headers.
#TEST-VAL-SUB026-3826#REF# FCT basic function BG defined as unlinked when the value Q_LINK is different in the separate balise headers

#REQ-UNISIG-SUB026-0369#REF# 8.4.2.2
The user information transmitted by a balise shall contain complete packets, i.e. splitting a packet between two balises is forbidden.
#TEST-VAL-SUB026-8010#REF# FCT basic function BG mit gesplittetem Paket

#REQ-UNISIG-SUB026-010570#REF# to.8.4.2.3 #REQ-UNISIG-SUB026-007262#REF#
If a received packet 0 or 200 is not transmitted as first packet of a balise telegram, a data consistency error shall be applied.
VBC function is not realized

therefore the following clarification is not relevant


UNISIG clarification: This is derived from 6.6.3.1.1 for packet 200. 
the same reaction for packet 0 is useful.
TEST APPROACH:
The following aspects have been identified:
1) P0 is not the first packet
2) P200 is not the first packet

#REQ-UNISIG-SUB026-0370:01#REF# 8.4.3.1
The format of the message to be transmitted by each loop is as follows:


Number of bits in loop header: 33
Rel. 8.0:
packet 255 is now a component of the general loop message format
#ANALYSE-VALUNISIG-4770#REF# FCT The message coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-8012#REF# EET error expectation Packets after 'end of information' in loop

#REQ-UNISIG-SUB026-0373#REF# 8.4.4.2.1
If the computed length of the message is not equal to the length given by L_MESSAGE, the entire message shall be rejected.
#TEST-VAL-SUB026-8013#REF# FCT basic function L_MESSAGE != Laenge der Message

#REQ-UNISIG-SUB026-008454#REF# 8.4.4.4.1

realised by: #REQ-UNISIG-SUB026-0911:02#REF#

#REQ-UNISIG-SUB026-0911:02#REF# 8.4.4.4.1 #REQ-UNISIG-SUB026-008454#REF#
#ANA-UNISIG-SUB040-0013#REF#
.
UNISIG clarification:
UCR1155 is taken over
realised by: #REQ-UNISIG-SUB026-010571#REF#
realised by: #REQ-UNISIG-SUB026-010572#REF#
realised by: #REQ-UNISIG-SUB026-010573#REF#
realised by: #REQ-UNISIG-SUB026-010574#REF#
realised by: #REQ-UNISIG-SUB026-010575#REF#
realised by: #REQ-UNISIG-SUB026-010576#REF#
realised by: #REQ-UNISIG-SUB026-010577#REF#
realised by: #REQ-UNISIG-SUB026-010578#REF#

#REQ-UNISIG-SUB026-010571#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-007191#REF#
#REQ-UNISIG-SUB026-0911:02#REF#
If a Message "SR Authorisation" is received from RBC, obu shall accept only packet 63 as optional packets.
#ANALYSE-VALUNISIG-5337#REF# FCT The message coding and acceptance of packets is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010572#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-007191#REF#
#REQ-UNISIG-SUB026-0911:02#REF#
If a Message "Movement Authority" is received from RBC, obu shall accept only packets 21, 27, 49, 80 and packets, which are defined in
the list of common optional packets, as optional packets.
#ANALYSE-VALUNISIG-5338#REF# FCT The message coding and acceptance of packets is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010573#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-0911:02#REF#
If a Message "Request To Shorten MA" is received from RBC, obu shall accept only packets 49 and 80 as optional packets.
#ANALYSE-VALUNISIG-5339#REF# FCT The message coding and acceptance of packets is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010574#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-007191#REF#
#REQ-UNISIG-SUB026-0911:02#REF#
If a general message is received from RBC, obu shall accept only packets 21, 27 and packets, which are defined in the list of common optional
packets, as optional packets.
#ANALYSE-VALUNISIG-5340#REF# FCT The message coding and acceptance of packets is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010575#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-0911:02#REF#
If a general message is received from RIU, obu shall accept only packets 44, 45, 143, 254 as optional packets.
Radio infill isn't realized

#REQ-UNISIG-SUB026-010576#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-0911:02#REF#
If a Message "SH authorised" is received from RBC, obu shall accept only packets 3, 44, 49 as optional packets.
#ANALYSE-VALUNISIG-5341#REF# FCT The message coding and acceptance of packets is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-3618:01#REF# to.8.4.4.4.1 #ANA-UNISIG-EvaluateMessage-0009:01#REF#
clarification to Message "SH authorised"
A list a of SH balises (packet 49), which is received together with a message 28 "SH authorised", shall be used only, if the
underlying message is accepted (filter criteria 4.8, time stamp).
remark: The other optional packets are evaluated independent of the acceptance of the message "SH authorised".
UNISIG clarification:
see analysis
TEST APPROACH:
According to 8.4.4.4.1, the optional packets for M28 are P3, P44 and P49.
#TEST-VAL-SUB026-4D65#REF# FCT P3 Evaluation of P3 received with not accepted SH Authorized
#TEST-VAL-SUB026-7025#REF# ECT P44 Evaluation of P44 received with not accepted SH Authorized
#TEST-VAL-SUB026-5995#REF# ECT P49 Evaluation of P49 received with not accepted SH Authorized

#REQ-UNISIG-SUB026-010577#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-0911:02#REF#
If a Message "MA with Shifted Location Reference" is received from RBC, obu shall accept only packets 21, 27, 49, 80 and packets,
which are defined in the list of common optional packets, as optional packets.
#ANALYSE-VALUNISIG-5342#REF# FCT The message coding and acceptance of packets is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010578#REF# to.8.4.4.4.1 #REQ-UNISIG-SUB026-0911:02#REF#
If a Message "Infill MA" is received from RIU, obu shall accept only packets 5, 21, 27, 39, 40, 41, 44, 49, 51, 65, 66, 68, 69, 70,
71, 80, 88, 138, 139 as optional packets.
Radio infill isn't realized

#REQ-UNISIG-SUB026-008458#REF# 8.4.4.4.1.1
.
realised by: #REQ-DESIGN-CR-0451:01#REF#

#REQ-DESIGN-CR-0451:01#REF# 8.4.4.4.1.1 #REQ-UNISIG-SUB026-008458#REF#
The following packets shall be accepted as common optional packets:
3, 5, 39, 40, 51, 41, 42, 44, 45, 52, 57, 58, 64, 65, 66, 68, 69, 70, 71, 72, 76, 79, 88, 131, 138, 139, 140
#ANALYSE-VALUNISIG-5343#REF# FCT The message coding and acceptance of packets is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0375:01#REF# 8.4.4.4.2
The train to track message 136 (Train Position Report) and 157 (SoM Position Report) may optionally include the following packets:
a)	Packet 4 (Error Reporting),
b)	Packet 5 (Train running number),
c)	Packet 44 (Data used by applications outside the ERTMS/ETCS system).
P5 is only relevant from ETCS Language version 2; 
for version 1.x 6.6.3.4.2 is valid
TEST APPROACH:
The following aspects have been identified:
1) Packet 4 (Error Reporting)
1.1) M136
1.2) M157
2) Packet 5 (Train running number)
2.1) M136
2.2) M157
3) Packet 44 (Data used by applications outside the ERTMS/ETCS system)
3.1) M136
3.2) M157
#TEST-VAL-SUB026-8028#REF# FCT 1.1 M136 with P4 (Error Report)
#TEST-VAL-SUB026-8029#REF# FCT 1.2 Error Report mit SoM Position Report
#TEST-VAL-SUB026-3B59#REF# FCT 2.1 Change Train Running Number from different sources when comm session is available
#TEST-VAL-SUB026-3B53#REF# FCT 2.2 Train Running Number from other ERTMS/ETCS external source during SOM
#TEST-VAL-SUB026-7844#REF# FCT 3.1 P44 to RBC in M136
#TEST-VAL-SUB026-7845#REF# FCT 3.2 P44 to RBC in M157

#REQ-UNISIG-SUB026-0913#REF# 8.4.4.4.3
The train to track message 159 (Session Established) may optionally include the following packets:
a)	Packet 3 (Onboard Telephone Numbers)
#TEST-VAL-SUB026-7581#REF# FCT basic function Onboard telephone numbers are sent to the RBC

#REQ-DESIGN-CR-0529#REF# 8.4.4.4.4
The train to track message 132 (MA request) may optionally include the following packet:
a)	Packet 9 (Level 2/3 transition information)
#TEST-VAL-SUB026-4954#REF# FCT basic function Track Ahead Free up to level 2/3 transition location (pkt 90)

#REQ-UNISIG-SUB026-0376#REF# 8.4.4.5
If needed to obtain an integer number of bytes, padding shall be added at the end of the message.
#ANALYSE-VALUNISIG-4768#REF# FCT The message/parameter coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-8036#REF# FCT basic function Radio Messages mit 0 bzw. 7 bit padding

#REQ-UNISIG-SUB026-0915#REF# 8.4.4.7.2
Exception:  The position report (packet 0 or packet 1) shall not be included in the following messages:
a)	Message 146 (Acknowledgement),
b)	Message 154 (No compatible version supported),
c)	Message 155 (Initiation of a communication session),
d)	Message 156 (Termination of a communication session),
e)	Intentionally deleted
f)	Message 159 (Session Established).

--- FINALISED ---
For every train to track message is defined, whether a position report is included or not. Other options for sending a position report are
excluded, because the packet 0 and 1 are not defined as optional packets.
#ANALYSE-VALUNISIG-7528#REF# FCT The requirement is not relevant refer column FINALISED.

#REQ-UNISIG-SUB026-008495#REF# to.8.4.4 #ANA-UNISIG-EvaluateMessage-0013#REF#
If the orientation of the reference balise group is unknown in the messages
- Conditional Emrgency Stop
- MA with Shifted Location Reference   and
- TAF Request,
the message shall be handled as data inconsistent.
Addiitional the optional packets of the message "MA with Shifted Location Reference" shall be rejected.
TEST APPROACH:
Following aspects have been identified:
1) Conditional Emrgency Stop
2) MA with Shifted Location Reference
3) TAF Request
#TEST-VAL-SUB026-5849#REF# FCT 1, 2, 3 Rejection of location depending messages with an LRBG set to 'unknown'

Chapter 8.5

#REQ-UNISIG-SUB026-3677:01#REF# 8.5.2
Train to Track radio messages

realised by: #REQ-UNISIG-SUB026-3680#REF#
realised by: #REQ-UNISIG-SUB026-008508#REF#

#REQ-UNISIG-SUB026-3680#REF# zu.8.5.2 #REQ-UNISIG-SUB026-3679#REF#
#REQ-UNISIG-SUB026-3677:01#REF#
All radio messages to trackside shall be sent as normal priority data.
#ANALYSE-VALUNISIG-4132#REF# FCT The requirement is validated with every test case - the appropriate check is realised via assert in the test environment.

#REQ-UNISIG-SUB026-008507#REF# 8.5.3
Track to Train radio messages

RIU is not realized, therefore the new column is not relevant
realised by: #REQ-UNISIG-SUB026-008508#REF#

#REQ-UNISIG-SUB026-008508#REF# to.8.5.3 #REQ-UNISIG-SUB026-3677:01#REF#
#REQ-UNISIG-SUB026-008507#REF#
The following messages shall be evaluated as invariant messages:
- Initiation of a communication session (msg. 38)
- RBC/RIU System Version (msg. 32)
- Acknowledgement of termination of a communication session (msg. 39)
- No compatible version supported (msg. 154)
- Initiation of a communication session (msg. 155)
- Termination of a communication session (msg. 156)
- Acknolwedgement (msg. 146)
UNISIG clarification:
Msg 146 is invariant too
#ANALYSE-VALUNISIG-7535#REF# FCT The coding and acceptance depending on (or not depending) on version is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

Chapter 8.6

TEST APPROACH:
The coding of messages according to the requirements outlined hereafter is realized centrally by the software module packet handler (PH). The
requirements are thoroughly tested by PH module verification.
The quality of the module tests is ensured by review of the module test specification and test implementation as part of the module review. The
result of the review is documented in /ESBO_UUE/ --> reference ID ESBO_VerBer.

The provisioning of the correct values to the packet handler is verified by the parameter verification (refer to verification of SUBSET-026
chapter 7.5).
Hence no additional test is needed here.
		
#REQ-UNISIG-SUB026-0381#REF# 8.6.1
Message 129: Validated Train Data

#ANALYSE-VALUNISIG-4727#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0916#REF# 8.6.2
Message 130: Request for Shunting

#ANALYSE-VALUNISIG-4728#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0917:01#REF# 8.6.3
Message 132: MA Request

Rel. 8.0: 
Q_MARQSTREASON replaces Q_TRACKDEL
#ANALYSE-VALUNISIG-4729#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0918#REF# 8.6.4
Message 136: Train Position Report

#ANALYSE-VALUNISIG-4730#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0919#REF# 8.6.5
Message 137: Request to Shorten MA is granted

#ANALYSE-VALUNISIG-4731#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0920#REF# 8.6.6
Message 138: Request to Shorten MA is rejected

#ANALYSE-VALUNISIG-4732#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0921#REF# 8.6.7
Message 146: Acknowledgement

#ANALYSE-VALUNISIG-4733#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0922#REF# 8.6.8
Message 147: Acknowledgement of Emergency Stop

#ANALYSE-VALUNISIG-4734#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0923#REF# 8.6.9
Message 149: Track Ahead Free Granted

#ANALYSE-VALUNISIG-4735#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0924#REF# 8.6.10
Message 150: End of Mission

#ANALYSE-VALUNISIG-4736#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0925#REF# 8.6.11
Message 153: Radio infill request

function RIU is not realized

#REQ-UNISIG-SUB026-0926#REF# 8.6.12
Message 154: No compatible version supported

#ANALYSE-VALUNISIG-4738#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0927#REF# 8.6.13
Message 155: Initiation of a communication session

#ANALYSE-VALUNISIG-4739#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0928#REF# 8.6.14
Message 156: Termination of a communication session

#ANALYSE-VALUNISIG-4740#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0929#REF# 8.6.15
Message 157: SoM Position Report

#ANALYSE-VALUNISIG-4741#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-008557#REF# 8.6.16
Message 158: Text Message Acknowledged by Driver

#ANALYSE-VALUNISIG-4742#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0931#REF# 8.6.17
Message 159: Session established

#ANALYSE-VALUNISIG-4743#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

Chapter 8.7

TEST APPROACH:
The coding of messages according to the requirements outlined hereafter is realized centrally by the software module packet handler (PH). The
requirements are thoroughly tested by PH module verification.
Hence no additional test is needed here.
		
#REQ-UNISIG-SUB026-0382#REF# 8.7.1
Message 2: SR Authorisation

#ANALYSE-VALUNISIG-4744#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.
#TEST-VAL-SUB026-5665#REF# EET error expectation Format of radio messages

#REQ-UNISIG-SUB026-008568#REF# 8.7.2
Message 3: Movement Authority

#ANALYSE-VALUNISIG-4745#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0384#REF# 8.7.3
Message 6: Recognition of exit from TRIP mode

#ANALYSE-VALUNISIG-4746#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0385#REF# 8.7.4
Message 8: Acknowledgement of Train Data

#ANALYSE-VALUNISIG-4747#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0932#REF# 8.7.5
Message 9: Request to Shorten MA

#ANALYSE-VALUNISIG-4748#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0933:01#REF# 8.7.6
Message 15: Conditional Emergency Stop

Rel. 8.0
D_REF is new
#ANALYSE-VALUNISIG-4749#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0934#REF# 8.7.7
Message 16: Unconditional Emergency Stop

#ANALYSE-VALUNISIG-4750#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0935#REF# 8.7.8
Message 18: Revocation of Emergency Stop

#ANALYSE-VALUNISIG-4751#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0386#REF# 8.7.9
Message 24: General message

#ANALYSE-VALUNISIG-4752#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0387#REF# 8.7.10
Message 27: SH Refused

#ANALYSE-VALUNISIG-4753#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010483#REF# to.8.7.10 #ANA-UNISIG-ETCSLanguage-0007#REF#
The OBU shall reject SH Refused from RBC (message 27)with a time stamp of shunting request lower than the initially send SH Request.

note: Repeating of SH Request messages shall not affect this check.
UNISIG clarification: see analysis 

an error reaction (error report) is not necessary
#TEST-VAL-SUB026-7642#REF# FCT basic function SH refused with lower refernce time stamp

#REQ-UNISIG-SUB026-0936#REF# 8.7.11
Message 28: SH Authorised

#ANALYSE-VALUNISIG-4754#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-010484#REF# to.8.7.11 #ANA-UNISIG-ETCSLanguage-0007#REF#
The OBU shall reject SH Authorised from RBC (message 28)with a time stamp of shunting request lower than the initially send SH Request.

note: Repeating of SH Request messages shall not affect this check.
UNISIG clarification: see analysis 

an error reaction (error report) is not necessary
#TEST-VAL-SUB026-7641#REF# FCT basic function SH authorized with lower refernce time stamp

#REQ-UNISIG-SUB026-0937#REF# 8.7.12
Message 32: RBC/RIU System Version

#ANALYSE-VALUNISIG-4755#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0388#REF# 8.7.13
Message 33: MA with Shifted Location Reference

#ANALYSE-VALUNISIG-4756#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0389:01#REF# 8.7.14
Message 34: Track Ahead Free Request

Rel. 8.0
D_REF is new
#ANALYSE-VALUNISIG-4757#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0390#REF# 8.7.15 #REQ-UNISIG-SUB026-0039#REF#
Message 37: Infill MA

#ANALYSE-VALUNISIG-4758#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0391#REF# 8.7.16
Message 38: Initiation of a communication session

#ANALYSE-VALUNISIG-4759#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0938#REF# 8.7.17
Message 39: Acknowledgement of termination of a communication session

#ANALYSE-VALUNISIG-4760#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0939#REF# 8.7.18
Message 40: Train Rejected

#ANALYSE-VALUNISIG-4761#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0940#REF# 8.7.19
Message 41: Train Accepted

#ANALYSE-VALUNISIG-4762#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-UNISIG-SUB026-0393#REF# 8.7.21
Message 43: SoM position report confirmed by RBC

#ANALYSE-VALUNISIG-4763#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

#REQ-DESIGN-CR-0389#REF# 8.7.22
Message 45: Assignment of coordinate system

#ANALYSE-VALUNISIG-4764#REF# FCT The message structure/coding is realized centrally by the software module packethandler (PH). Verification takes place via PH module test.

SUB040

Chapter 4

TEST APPROACH:
Note: The track description is verified via a mode independent test interface if not stated otherwise.
		

Chapter 4.1

#REQ-DESIGN-CR-0755#REF# to.4.1.1.2 #ANA-UNISIG-SUB040-BGRules-0001#REF#
Detection of the next balise inside a balise group shall be supervised. After a distance of 12 meters in addition to a detection inaccuracy it
shall be watched for the next balise in this balise group.
#TEST-VAL-SUB040-0004#REF# FCT basic function Maximum distance between two consecutive balises

#REQ-DESIGN-CR-0756#REF# to.4.1.1.2 #ANA-UNISIG-SUB040-BGRules-0001#REF#
If a balise inside the balise group has been read with a distance to the previous balise greater than a defined maximum supervision distance,
this balise shall be accepted nevertheless.
#TEST-VAL-SUB040-0054#REF# FCT basic function balise inside BG read with a distance to the previous balise greater than a defined maximum supervision distance

#REQ-DESIGN-CR-0757#REF# to.4.1.1.2 #ANA-UNISIG-SUB040-BGRules-0001#REF#
If no balise could be read inside the defined maximum supervision distance, no special error reaction shall be executed.
#TEST-VAL-SUB040-0054#REF# FCT basic function balise inside BG read with a distance to the previous balise greater than a defined maximum supervision distance

#REQ-DESIGN-CR-0758#REF# to.4.1.1.2 #ANA-UNISIG-SUB040-BGRules-0001#REF#
While watching for the last balise inside a balise group, watching shall be stopped after the defined maximum supervision distance.
#TEST-VAL-SUB040-0004#REF# FCT basic function , CFX00031546 Maximum distance between two consecutive balises

#REQ-UNISIG-SUB040-000342#REF# 4.1.2.2
Minimum / maximum distance between the front of the engine / 1st axle of the engine and the Eurobalise antenna


--- FINALISED ---
Die Vorgaben für den minimalen, maximalen Abstand der Balisenantenne zur Zugspitze/1. Achse sind bereits durch
#REQ-SAD-HWSS-ELBE5A-ANT-0001#REF# aus SyArchSub  abgedeckt.
#ANALYSE-VALUNISIG-5323#REF# FCT Validation of the requirement takes place in [ESBO_SyValBer]

Chapter 4.2

#REQ-UNISIG-SUB040-0011#REF# 4.2.2.1
Maximum length per message – to allow for the dimensioning of radio input buffers

A maximum number of bytes is not relevant for high priority data as only fixed size messages are used.
TEST APPROACH:
The limitation has to be ensured by track side. The OBU SW accepts the maximal possible message length.
The OBU in on the whole has to be able to process messages up to 500 bytes (verification via SW-HW intigration test)
The following aspects have been identified:
1) application software does not limit the maximum length per message
2) the system can properly process messages with the maximum length
#TEST-VAL-SUB026-7448#REF# BVA 1 Test of variable L_MESSAGE
#TEST-SWHWINT-SWVAL-FKT-0009#REF# FCT 2 Maximale Länge radio message (radio input buffer)

#REQ-UNISIG-SUB040-001092#REF# to.4.2.4.3
If the on-board receives the information "List of of Balises for SH area" (P49) without a mode profile (P80) with the variable
M_MAMODE = “Shunting", obu shall assess it as a data inconsistency.

Exception: the information "List of of Balises for SH area" is received together with the Message "SH authorised".
TEST APPROACH:
The following aspects have been identified:
1) rejection of P49 without MP-SH
1.1) reception of P49 without MP
1.1.1) radio message (either M3, M9 or	M33) 
1.1.2) balise
1.1.3) loop
1.2) reception of P49 with MP for other mode than SH
2) acceptance of P49 without MP in M28
#TEST-VAL-SUB026-5740#REF# FCT 1.1.1, 1.2 Reception of P49 without MP-SH from RBC
#TEST-VAL-SUB026-5741#REF# FCT 1.1.2 Reception of P49 without MP-SH from BG
#TEST-VAL-SUB026-7045#REF# FCT 2 List of balises for SH Area replaced by new P49 from M28

#REQ-UNISIG-SUB040-001094#REF# to.4.2.4.4 #ANA-UNISIG-SUB040-0013#REF#
Only the following non-infill information shall be accepted from a loop:
  Packet 13 (SR distance information from loop)
  Packet 44 ((data to be used by applications outside ERTMS/ETCS)
  Packet 254 (Default Balise/Loop/RIU information)

All other non Infill Information shall be ignored without an error reaction.
A basic diagnostic event shall be issued.
UNISIG clarification:
an OBU requirement is necessary for a reaction, if the RBC sends other non infill information.

UCR1155 is taken over

Rel. 8.0
this requirement replaces REQ-UNISIG-SUB026-3127
TEST APPROACH:
The following aspects have been identified:
1) P13
2) P44
3) P254
4) different than P13, P44 or P254
#TEST-VAL-SUB026-7672#REF# FCT 1 Non in-fill pkt 13 from LOOP
#TEST-VAL-SUB040-0060#REF# FCT 2 Acceptance of non in-fill P44 from LOOP
#TEST-VAL-SUB026-3607#REF# FCT 3 non in-fill information from LOOP apart from pkt 254 neglected
#TEST-VAL-SUB026-3606#REF# FCT 4 non in-fill information from LOOP neglected

#REQ-UNISIG-SUB040-001194#REF# to.4.2.4.4
The obu shall accepts from RIU only the following messages:
  Message 24 (general message)
  Message 32 (RBC/RIU System Version)
  Message 33 (Infill MA)
  Message 39 (Acknowledgement of session termination)

All other received messages from a RIU shall be ignored without an error reaction.
A basic diagnostic event shall be issued.
UNISIG clarification: message 24 is possible too (see Subset 26, 8.4.4.4.1) Otherwise the above-named packets cannot received.

the exclusion of the above-named packets is ensured through Subset 26, 8.4.4.4.1.

#REQ-UNISIG-SUB040-001202:01#REF# to.4.2.4.5.1 #ANA-UNISIG-SUB040-0010:02#REF#
The telegram/message shall be interpreted as data inconsistency, if another information as the following is contained in the infill information:
  Packet 136 (infill location reference)
  Packet 12, 80, 49 (MA, Mode Profile, List of Balises for SH area)
  Packet 21 (Gradient Profile)
  Packet 27, 51, 65/66, 70 (SSP, ASP, TSR, Route Suitability)
  Packet 5 (Linking)
  Packet 41 (Level transition)
  Packet 44 (data used outside ERTMS)
  Packet 39, 40, 67, 68, 69 (Track condition)
  Packet 71 (adhesion factor)
  Packet 133 (Radio in-fill area information)
  Packet 138, 139 (Reversing area information)
  Packet 52 (Permitted Braking Distance Information)
  Packet 88 (Level Crossing Information)
#TEST-VAL-SUB026-7145#REF# EET error expectation P2 as infill information
#TEST-VAL-SUB040-0053#REF# FCT unexpected infill information Reception of infill conditional level transition order

#REQ-UNISIG-SUB040-3002:01#REF# to.4.2.4.5.2 #ANA-UNISIG-SUB040-0002:01#REF#
If a level transition order with D_LEVELTR=now is contained in Infill information, obu shall interpret this as D_LEVELTR=0.
#TEST-VAL-SUB040-0032#REF# FCT basic function Infill information contains a level transition order with D_LEVELTR=now

#REQ-UNISIG-SUB040-3040:01#REF# to.4.2.4.6.1 #ANA-UNISIG-SUB040-0009:01#REF#
The train reaction, which is defined in #DSC-TBL-ModeProfile-0002#REF#, shall be executed, when
- the train receives a new mode profile information with more than one mode profile
AND
- the second mode profile overlaps the first mode profile.
TEST APPROACH:
Following aspects have been identified:
1) overlapping mode profiles of different kind 
2) overlapping SH mode profiles
3) overlapping mode profile, apart from SH, of same kind with different V_MAMODE
4) overlapping mode profile, apart from SH, of same kind with same V_MAMODE 
#TEST-VAL-SUB026-4812#REF# FCT 1 mode change FS->SF[13] due to reception of overlapping MP OS/SH
#TEST-VAL-SUB026-3314#REF# EET 2 Processing of P80 with two MP-SH with same location but different V_MAMODE
#TEST-VAL-SUB026-5546#REF# FCT 3 two overlapping MP-OS area (different V_MAMODE)
#TEST-VAL-SUB026-5952#REF# FCT 4 Overlapping mode profile, of same kind with same V_MAMODE
#TEST-VAL-SUB026-5774#REF# EET error expectation Two overlapping MP-LS area (different V_MAMODE)
#TEST-VAL-SUB026-5951#REF# EET error expectation Overlapping MP-SH

#REQ-UNISIG-SUB040-3044:01#REF# to.4.2.4.6.2
If a L1 MA packet with V_MAIN=0 is received with a mode profile and the mode profile is started at a further location, the mode profile shall be
ignored and a basic diagnostic event shall be issued.
remark: 
A obu reaction is necessary when the trackside sends a trip ma with a mode profile with start distance > 0.
#TEST-VAL-SUB026-4E21#REF# FCT basic function Reception of trip order and MP with D_MAMODE> 0, override active

#REQ-UNISIG-SUB040-3041:01#REF# 4.2.4.7.1 #ANA-UNISIG-SUB040-0011#REF#



see analysis - line speed (SSP) is contrary to calculate with current speed, defined  in Subset 26, ch. 5.18. The definition in 5.18 is used
realised by: #REQ-UNISIG-SUB026-010346#REF#
realised by: #REQ-UNISIG-SUB026-010342#REF#
realised by: #REQ-UNISIG-SUB026-010343#REF#
realised by: #REQ-UNISIG-SUB026-010348#REF#

#REQ-UNISIG-SUB040-3043:01#REF# 4.2.4.7.2 #ANA-UNISIG-SUB040-0011#REF#

see analysis - line speed (SSP) is contrary to calculate with current speed, defined  in Subset 26, ch. 5.18. The definition in 5.18 is used
realised by: #REQ-UNISIG-SUB026-010346#REF#
realised by: #REQ-UNISIG-SUB026-3446#REF#
realised by: #REQ-UNISIG-SUB026-010344#REF#
realised by: #REQ-UNISIG-SUB026-3456#REF#
realised by: #REQ-UNISIG-SUB026-010345#REF#

#REQ-UNISIG-SUB040-3001#REF# to.4.2.4.8.2 #ANA-UNISIG-SUB040-0001:01#REF#
If a balise group with balise group qualifier “unlinked” transmits linking information, obu shall handle this as a data inconsistency.

Exception:the linking information is a part of infill informations
#TEST-VAL-SUB040-0031#REF# FCT infill informations Processing of infill linking information from unlinked BG
#TEST-VAL-SUB026-4324#REF# FCT non infill informations Processing of linking information from unlinked BG

#REQ-UNISIG-SUB040-3000#REF# 4.2.4.11 #ANA-UNISIG-CR0771-0001#REF#
Packet 131 (RBC Transition Order)

siehe Analyse 
=> Die Einhaltung dieser Anforderung obliegt der Strecke
=> Fahrzeug muss nur 
Fehlerreaktion "Dateninkonsistenz" ausführen
realised by: #REQ-UNISIG-SUB040-0030:01#REF#

#REQ-UNISIG-SUB040-0030:01#REF# to.4.2.4.11 #REQ-UNISIG-SUB040-3000#REF#
#ANA-UNISIG-CR0771-0001#REF#
If obu received a RBC transition order with NID_RBC=“Contact the last known RBC”, this shall be handled as a data inconsistency.
#TEST-VAL-SUB040-0034#REF# FCT basic function RBC transition order with NID_RBC=CONTACT LAST KNOWN RBC shall be handled as a data inconsistency.

Chapter 4.3

#REQ-UNISIG-SUB040-3005:01#REF# to.4.3.2.1
a) Number of MA sections (excluding the End Section


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-UNISIG-SUB040-0014:02#REF#

#REQ-UNISIG-SUB040-0014:02#REF# to.4.3.2.1.a) #REQ-UNISIG-SUB040-3005:01#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of MA sections including end section
Memorised on board: 14
TEST APPROACH:
The following aspects have been identified:
1) MA for current location
1.1) P12
1.2) P15
2) infill MA
#TEST-VAL-SUB040-0051#REF# FCT 1.1 Overlaping MA sections + In-Fill MA sections = Max number of MA sections
#TEST-VAL-SUB040-0047#REF# FCT 1.2 Max number of MA sections from RBC
#TEST-VAL-SUB040-0011#REF# FCT 2 Max number of in-fill MA sections
#TEST-VAL-SUB040-0009#REF# EET error expectation Max number of MA sections from BG
#TEST-VAL-SUB040-0052#REF# EET error expectation Max number of MA sections (normal + infill) out of level transition buffer

#REQ-UNISIG-SUB040-3006#REF# to.4.3.2.1.a) #ANA-UNISIG-SUB040-0006:01#REF#
Wird bei Erhalt einer neuen MA die maximal auf dem Fahrzeug beherrschte Anzahl von MA sections überschritten, ist diese MA zu ignorieren und
eine Diagnosemeldung mit dem Grund des Ignorierens auszugeben.
TEST APPROACH:
The following aspects have been identified:
1) first MA
2) MA update
#TEST-VAL-SUB040-0010#REF# FCT 1 MA (from BG) with exceeding amount of section ignored
#TEST-VAL-SUB040-0048#REF# FCT 2 MA (from RBC) with exceeding amount of section ignored

#REQ-UNISIG-SUB040-0015:01#REF# to.4.3.2.1
b) Number of balise IDs in balise list for SR authority or for shunting mode

UNISIG clarification: 
obu permits the maximum N_ITER value
--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
TEST APPROACH:
The OBU does not check the limit hence N_ITER=31 has to be verified.
The following aspects have been identified:
1) balise IDs in balise list for SR authority
2) balise IDs in balise list for SH area
#TEST-VAL-SUB040-0012#REF# FCT 1 SR authorisation with maximum number of BGs
#TEST-VAL-SUB040-0050#REF# FCT 2 List of balises for SH mode with maximum number of BGs

#REQ-UNISIG-SUB040-3007:01#REF# to.4.3.2.1
c) Number of mode profile sections


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-UNISIG-SUB040-0016:01#REF#

#REQ-UNISIG-SUB040-0016:01#REF# to.4.3.2.1.c) #REQ-UNISIG-SUB040-3007:01#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of mode profile sections
Memorised on board: 6
#TEST-VAL-SUB026-3795#REF# FCT basic function Acceptance and storage of 2*3MP

#REQ-UNISIG-SUB040-3008#REF# to.4.3.2.1.c) #ANA-UNISIG-SUB040-0006:01#REF#
Wird bei Erhalt eines neuen Modeprofils die maximal auf dem Fahrzeug beherrschte Anzahl von Modeprofilen überschritten, ist ein Systemfehler
auszulösen.
#TEST-VAL-SUB026-3797#REF# FCT basic function Amount of received MP exceeds OBU capacity

#REQ-UNISIG-SUB040-3009#REF# to.4.3.2.1
d) Number of locations with changes of SSP


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-UNISIG-SUB040-0017:01#REF#

#REQ-UNISIG-SUB040-0017:01#REF# to.4.3.2.1.d) #REQ-UNISIG-SUB040-3009#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
#ANA-UNISIG-SUB040-0012#REF#
Number of locations of changes of SSP
minimum memorised on board: 50
#TEST-VAL-SUB040-0036#REF# FCT basic function Min number of stored locations with changes of SSP is exceeded
#TEST-VAL-SUB026-3A09#REF# EET error expectation Max number SSP/GP/TSR/ASP

#REQ-UNISIG-SUB040-3011#REF# to.4.3.2.1
e) Number of TSR

realised by: #REQ-UNISIG-SUB040-0018:01#REF#
realised by: #REQ-UNISIG-SUB040-3012#REF#

#REQ-UNISIG-SUB040-0018:01#REF# to.4.3.2.1.e) #REQ-UNISIG-SUB040-3011#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of TSR
Memorised on board: 30
#TEST-VAL-SUB040-0018#REF# FCT basic function More than 30 TSRs
#TEST-VAL-SUB026-3A09#REF# EET error expectation Max number SSP/GP/TSR/ASP

#REQ-UNISIG-SUB040-3012#REF# to.4.3.2.1.e) #REQ-UNISIG-SUB040-3011#REF#
#ANA-UNISIG-SUB040-0006:01#REF#
Wird bei Erhalt einer neuen TSR die maximal auf dem Fahrzeug beherrschte Anzahl von TSRs überschritten, ist ein Systemfehler auszulösen.
#TEST-VAL-SUB040-0018#REF# FCT basic function More than 30 TSRs

#REQ-UNISIG-SUB040-001089#REF# to.4.3.2.1.e) #ANA-UNISIG-SUB040-0008#REF#
If the on board received TSR and TSR Revocations in the same message, the TSR revocations shall be evaluated as first.
TEST APPROACH:
Following aspects have been identified:
1)TSR and TSR Revocation with different IDs in the same message
2)TSR and TSR Revocation with the same IDs in the same message
#TEST-VAL-SUB026-5605#REF# FCT 1 TSR and TSR Revocations in the same message (max number of TSRs stored on-board)
#TEST-VAL-SUB026-5606#REF# FCT 2 TSR and TSR Revocations with same ID in the same message

#REQ-UNISIG-SUB040-3013#REF# to.4.3.2.1
f) Number of changes of gradient


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-UNISIG-SUB040-0019:01#REF#

#REQ-UNISIG-SUB040-0019:01#REF# to.4.3.2.1.f) #REQ-UNISIG-SUB040-3013#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
#ANA-UNISIG-SUB040-0012#REF#
Number of changes of gradient
minimum memorised on board: 50
#TEST-VAL-SUB040-0040#REF# FCT basic function Min number of stored locations with changes of GP is exceeded
#TEST-VAL-SUB026-3A09#REF# EET error expectation Max number SSP/GP/TSR/ASP

#REQ-UNISIG-SUB040-0020#REF# to.4.3.2.1
g) Number of locations for position reports

UNISIG clarification: 
obu permits the maximum N_ITER value
--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
TEST APPROACH:
The OBU does not check the limit hence N_ITER=31 has to be verified.
#TEST-VAL-SUB040-0022#REF# FCT basic function Number of locations for position reports

#REQ-UNISIG-SUB040-3038#REF# to.4.3.2.1
h) Number of text messages

In den Paketen 72 und 76 existiert kein N_ITER. Damit ist die Einschränkung für diesen Teil nicht relevant.
realised by: #REQ-UNISIG-SUB040-0021#REF#

#REQ-UNISIG-SUB040-0021#REF# to.4.3.2.1.h) #REQ-UNISIG-SUB040-3038#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of text messages
Memorised on board: 5 plain text + 5 fixed text
#TEST-VAL-SUB040-0049#REF# FCT basic function FIFO-Prinzip for plain and fixed texts queues on DMI

#REQ-UNISIG-SUB040-3015#REF# to.4.3.2.1.h) #ANA-UNISIG-SUB040-0006:01#REF#
If a plain text message is received while the maximum number of plain text messages is stored onboard, the oldest plain text message shall be
deleted and the new one stored.
#TEST-VAL-SUB040-0049#REF# FCT basic function FIFO-Prinzip for plain and fixed texts queues on DMI

#REQ-UNISIG-SUB040-3016#REF# to.4.3.2.1.h) #ANA-UNISIG-SUB040-0006:01#REF#
If a fixed text message is received while the maximum number of fixed text messages is stored onboard, the oldest fixed text message shall be
deleted and the new one stored.
#TEST-VAL-SUB040-0049#REF# FCT basic function FIFO-Prinzip for plain and fixed texts queues on DMI

#REQ-UNISIG-SUB040-3017#REF# to.4.3.2.1
i) Number of linked balise groups


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-DESIGN-CR-0001:01#REF#

#REQ-DESIGN-CR-0001:01#REF# to.4.3.2.1.i) #REQ-UNISIG-SUB040-3017#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of linked balise groups
Memorised on board: 32
obu realized the limit of N_ITER in one P5
#TEST-VAL-SUB040-0024#REF# FCT basic function 32 announced BGs

#REQ-UNISIG-SUB040-3018#REF# to.4.3.2.1.i) #ANA-UNISIG-SUB040-0006:01#REF#
Wird die maximal auf dem Fahrzeug beherrschte Anzahl von Linking Informationen überschritten, ist ein Systemfehler auszulösen.
#TEST-VAL-SUB040-0046#REF# FCT basic function A system failure occurs when the max number of stored Linking Informations is exceeded

#REQ-UNISIG-SUB040-3019:01#REF# to.4.3.2.1
j) Number of Track Conditions Change of traction system

maximum one Traction System is possible
- see 3.7.3.1 e
realised by: #REQ-UNISIG-SUB026-010257#REF#

#REQ-UNISIG-SUB040-3023#REF# to.4.3.2.1
k) Number of Track Conditions Big Metal masses


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-DESIGN-CR-0314#REF#

#REQ-DESIGN-CR-0314#REF# to.4.3.2.1.k) #REQ-UNISIG-SUB040-3023#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of Track Conditions Big Metal masses (Packet 67)
Memorised on board: 10
#TEST-VAL-SUB040-0038#REF# FCT basic function A system failure occurs when the max number of Track Conditions Big Metal Masses stored on board is exceeded

#REQ-UNISIG-SUB040-3024#REF# to.4.3.2.1.k) #ANA-UNISIG-SUB040-0006:01#REF#
Wird die maximal auf dem Fahrzeug beherrschte Anzahl der TC "big metal masses" überschritten,ist ein Systemfehler auszulösen.
#TEST-VAL-SUB040-0038#REF# FCT basic function A system failure occurs when the max number of Track Conditions Big Metal Masses stored on board is exceeded

#REQ-UNISIG-SUB040-3025#REF# to.4.3.2.1
l) Number of Track Conditions


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-DESIGN-CR-0315#REF#

#REQ-DESIGN-CR-0315#REF# to.4.3.2.1.l) #REQ-UNISIG-SUB040-3025#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of Track Conditions (Packet 68)
Memorised on board: 32
#TEST-VAL-SUB040-0039#REF# FCT basic function A system failure occurs when the max number of Track Conditions (pkt 68) stored on board is exceeded

#REQ-UNISIG-SUB040-3026#REF# to.4.3.2.1.l) #ANA-UNISIG-SUB040-0006:01#REF#
Wird die maximal auf dem Fahrzeug beherrschte Anzahl der Track conditions aus Paket 68 überschritten,ist ein Systemfehler auszulösen.
#TEST-VAL-SUB040-0039#REF# FCT basic function A system failure occurs when the max number of Track Conditions (pkt 68) stored on board is exceeded

#REQ-UNISIG-SUB040-3027:01#REF# to.4.3.2.1
m) Number of Route suitability data

UNISIG
--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-DESIGN-CR-0313:01#REF#
realised by: #REQ-UNISIG-SUB040-001190#REF#

#REQ-DESIGN-CR-0313:01#REF# to.4.3.2.1.m) #REQ-UNISIG-SUB040-3027:01#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of Route suitability data (Packet 70)
Memorised on board:
3 loading gauges
3 value of axle load
3 value of traction system type
UNISIG clarification: see analysis
TEST APPROACH:
Only the most restrictive route unsuitability of the same type is functional relevance.
The verification is hence limited to one route unsuitability of each type and acceptance of P70 with 3 unsuitability of same type. 
#TEST-VAL-SUB026-7091#REF# FCT basic function Number of Route suitability data memorized on board

#REQ-UNISIG-SUB040-001190#REF# to.4.3.2.1.m) #REQ-UNISIG-SUB040-3027:01#REF#
#ANA-UNISIG-SUB040-0004:01#REF#
If N_ITER in the received information "Route Suitability Data" greater than 2, it shall be interpreted as a data inconsistency and the
information shall ignored.
UNISIG clarification: see analysis
#TEST-VAL-SUB026-7090#REF# FCT basic function N_ITER in the received information 'Route Suitability Data' greater than 2

#REQ-UNISIG-SUB040-3030#REF# to.4.3.2.1
o) Number of Axle load speed profile segments


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-UNISIG-SUB040-3031#REF#

#REQ-UNISIG-SUB040-3031#REF# to.4.3.2.1.o) #REQ-UNISIG-SUB040-3030#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
Number of Axle load speed profile segments (Packet 51)
Memorised on board: 30
#TEST-VAL-SUB040-0041#REF# FCT basic function A system failure occurs when the max number of stored Axle Load SP exceeded
#TEST-VAL-SUB026-3A09#REF# EET error expectation Max number SSP/GP/TSR/ASP

#REQ-UNISIG-SUB040-3032#REF# to.4.3.2.1.o) #ANA-UNISIG-SUB040-0006:01#REF#
Wird die maximal auf dem Fahrzeug beherrschte Anzahl der Axle load speed profile segments überschritten, ist ein Systemfehler auszulösen.
Dies gilt sowohl bei Empfang eines Paketes mit insgesamt mehr als 30 Profilen als auch für den Fall, dass nach mehrmaligen Empfang eines
ASP-Paketes insgesamt die maximal zu speichernde Anzahl der Profilelemente überschritten wird.
#TEST-VAL-SUB040-0041#REF# FCT basic function A system failure occurs when the max number of stored Axle Load SP exceeded

#REQ-UNISIG-SUB040-3033#REF# to.4.3.2.1
p) Number of Axle load speed restriction values per ASP segment

UNISIG clarification: 
obu permits the maximum N_ITER value
--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
TEST APPROACH:
The OBU does not check the limit hence N_ITER=31 has to be verified.
#TEST-VAL-SUB040-0043#REF# FCT basic function Max number of Axle load speed restriction values per ASP segment

#REQ-UNISIG-SUB040-3034#REF# to.4.3.2.1
q) Number of adhesion profiles


--- FINALISED ---
The adherence to the maximum number of iterations in one packet is a trackside requirement. A check for correctness by obu is not necessary.
realised by: #REQ-UNISIG-SUB040-3035#REF#

#REQ-UNISIG-SUB040-3035#REF# to.4.3.2.1.q) #REQ-UNISIG-SUB040-3034#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
#ANA-UNISIG-SUB040-0012#REF#
Number of adhesion profiles
minimum memorised on board: 10
#TEST-VAL-SUB040-0042#REF# FCT basic function Max number of stored location with Adhesion Factor changes

#REQ-UNISIG-SUB040-3037#REF# to.4.3.2.1
r) Number of reversing area

The minimum memorized on board is realized with the requirement, that a new RV-Area replaces the current in Subset 26, 3.7.3.1 k) and
3.15.4.1.1.
realised by: #REQ-UNISIG-SUB026-3113#REF#

#REQ-UNISIG-SUB040-001097#REF# to.4.3.2.1
s) Number of Permitted Braking Distance Speed Restrictions

realised by: #REQ-UNISIG-SUB040-001098#REF#
realised by: #REQ-UNISIG-SUB040-001191#REF#

#REQ-UNISIG-SUB040-001098#REF# to.4.3.2.1.s) #REQ-UNISIG-SUB040-001097#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
The obu shall memorize maximum 5 permitted braking distance speed restrictions.
#TEST-VAL-SUB040-0057#REF# FCT basic function Maximum PBD informations memorized on board

#REQ-UNISIG-SUB040-001186#REF# to.4.3.2.1.s) #ANA-UNISIG-SUB040-0006:01#REF#
If the limit of maximum number of  permitted braking distance speed restrictions is exceeded, a system failure shall be applied.
#TEST-VAL-SUB040-0057#REF# FCT basic function Maximum PBD informations memorized on board

#REQ-UNISIG-SUB040-001191#REF# to.4.3.2.1.s) #REQ-UNISIG-SUB040-001097#REF#
#ANA-UNISIG-SUB040-0004:01#REF#
If N_ITER in the received information "Permitted Brake Distance" is greater than 2, it shall be interpreted as a data inconsistency
and the information shall ignored.
#TEST-VAL-SUB040-0057#REF# FCT basic function Maximum PBD informations memorized on board

#REQ-UNISIG-SUB040-001192#REF# to.4.3.2.1.t) #ANA-UNISIG-SUB040-0004:01#REF#
If N_ITER in the received Track Condition "Station Platforms" is greater than 4, it shall be interpreted as a data inconsistency and
the information shall ignored.
Track Condition "Station Platforms" doesn't realized

#REQ-UNISIG-SUB040-001109#REF# to.4.3.2.1
v) Number of Level Crossings

realised by: #REQ-UNISIG-SUB040-001184#REF#

#REQ-UNISIG-SUB040-001184#REF# to.4.3.2.1.v) #REQ-UNISIG-SUB040-001109#REF#
#ANA-UNISIG-SUB040-0005:02#REF#
The obu shall memorize maximum 10 Level Crossing information.
TEST APPROACH:
The following aspects have been identified:
1) Maximum number of packets in 1 message
2) Minimum memorised on board
#TEST-VAL-SUB040-0056#REF# FCT 1, 2 Maximum Level Crossing informations memorized on board

#REQ-UNISIG-SUB040-001185#REF# to.4.3.2.1.v) #ANA-UNISIG-SUB040-0006:01#REF#
If the limit of maximum number of Level Crossing Information is exceeded, a system failure shall be applied.
#TEST-VAL-SUB040-0056#REF# FCT basic function Maximum Level Crossing informations memorized on board

#REQ-UNISIG-SUB040-001110#REF# to.4.3.2.1
w) Number of Virtual Balise Covers set by trackside

realised by: #REQ-UNISIG-SUB040-001022#REF#
realised by: #REQ-UNISIG-SUB040-001023#REF#

#REQ-UNISIG-SUB040-001022#REF# to.4.3.2.1.w) #REQ-UNISIG-SUB040-001110#REF#
The obu shall memorize maximum 10 Virtual Balise Cover information from trackside.
VBC function should not have to  realize

#REQ-UNISIG-SUB040-001023#REF# to.4.3.2.1.w) #REQ-UNISIG-SUB040-001110#REF#
If the limit of maximum number of Virtual Balise Cover information from trackside is exceeded, a system failure shall be applied.
UNISIG clarification:
SF is ok

VBC function should not have to  realize

#REQ-UNISIG-SUB040-001111#REF# to.4.3.2.1
x) Size of packet 44 with NID_XUSER = 102

feature should not be implemented with the current release

Chapter 4.4

#REQ-UNISIG-SUB040-001127#REF# 4.4.1.2.1.1
The nominal emergency brake deceleration shall be based on the following environmental conditions: for conventional trains according to appendix
F1.1 of UIC Leaflet 544-1, for high speed trains according to case A of 2008/232/EC.
#ANALYSE-VALUNISIG-7564#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001129#REF# 4.4.1.2.2.1
The emergency brake deceleration shall be based on dry friction elements.
#ANALYSE-VALUNISIG-7565#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001131#REF# 4.4.1.2.3.1
If field tests are carried out to define the nominal emergency brake deceleration, they shall be performed on straight and as level as possible
track. The deceleration shall be corrected to level track.
#ANALYSE-VALUNISIG-7566#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001134#REF# 4.4.1.2.4.1.1
The nominal emergency brake deceleration shall be valid for normally loaded vehicles (see clause 4.2.3.2 of 2008/232/EC and clause 4.2.2.10 of
2011/291/EU).
is valid for Passenger trains without automatic loading device
#ANALYSE-VALUNISIG-7567#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001136#REF# 4.4.1.2.4.2.1
For vehicles with automatic loading device the nominal emergency brake deceleration shall be defined as the lowest deceleration from the whole
loading range (from empty to exceptional load) and if the lowest deceleration is obtained by several loads then the greatest load shall be taken
into account as the nominal loaded condition
#ANALYSE-VALUNISIG-7568#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001139#REF# 4.4.1.2.5.2
In case special brake system(s) (regenerative brake, magnetic shoe brake or eddy current brake) is/are considered in the nominal emergency brake
deceleration and if the train is running on lines where a certain special brake system is not permitted or must be inhibited at certain
locations (through the track condition “Inhibition of special brakes”), further nominal deceleration profiles without the contribution of the
concerned special brake system shall be defined.
#ANALYSE-VALUNISIG-7569#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001140#REF# 4.4.1.2.5.3
In case the dynamic brake not independent from the presence of voltage in the catenary (i.e. regenerative brake not backed up by a rheostatic
brake) is included in the nominal emergency brake deceleration, further nominal deceleration profile(s) without the contribution of this brake
shall be defined. Justification: the train will always encounter a powerless section (through the track condition “powerless section”) wherever
it will operate.
#ANALYSE-VALUNISIG-7570#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001142#REF# 4.4.1.2.6.1
The nominal deceleration shall be based on new wheel diameter.
#ANALYSE-VALUNISIG-7571#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001144#REF# 4.4.1.3.1
The nominal brake build up time shall be the equivalent brake build-up time as specified in section 3.13.2.2.3.2 of SUBSET-026.
#ANALYSE-VALUNISIG-7572#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001146#REF# 4.4.1.4.1
Kdry_rst(V,EBCL) shall be established for each confidence level that can be required by trackside (refer to sections 3.13.2.2.9.1.2,
3.13.2.2.9.1.3, 3.13.2.2.9.1.4 and variable M_NVEBCL in SUBSET-026). For the dry rail reference conditions, see section 4.4.1.2.1.
#ANALYSE-VALUNISIG-7573#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001150#REF# 4.4.1.5.1.1
In order to determine the correction factor Kwet_rst(V), field tests shall be made according to the provisions laid down in the following
sections of EN15595:
  6.1.2 (ambient temperature condition);
  6.2.3 table 5 tests 1 & 3 and 2 & 4 (test programme for initial speed 120 km/h and maximum train speed, respectively);
  6.4.2.1 (generation of reduced adhesion);
  6.4.3.5 (spraying conditions for tests at speed higher than 200 km/h);
  6.4.4.1 (correction of the measured stopping distance);
  6.4.4.2 (number and validity of tests on dry rails);
  6.4.4.3 (evaluation of validity of tests on wet rails).
is only valid for Trains fitted with wheel slide protection system
#ANALYSE-VALUNISIG-7574#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001151#REF# 4.4.1.5.1.2
For each pair of deceleration distances (on dry rail and with reduced adhesion) obtained from the tests 1 & 3 and 2 & 4, the increase of
deceleration distance (in %) obtained from the tests shall be used as follows to determine the correction factor: Kwet_rst = 100/(100+ increase
of deceleration distance (in %)), with the deceleration distance resulting from tests 3 & 4 being the mean of the valid tests.
is only valid for Trains fitted with wheel slide protection system
#ANALYSE-VALUNISIG-7575#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001152#REF# 4.4.1.5.1.3
The deceleration distance is defined as the total distance travelled from the triggering of brake command to the train stop, minus the distance
travelled from this triggering to the elapsing of the equivalent brake build up time.
is only valid for Trains fitted with wheel slide protection system
#ANALYSE-VALUNISIG-7576#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001153#REF# 4.4.1.5.1.4
In case a unique Kwet_rst (i.e. valid for all speeds) is defined, the maximum increase of deceleration distance between the tests 1 & 3 and
2 & 4 shall be retained.
is only valid for Trains fitted with wheel slide protection system
#ANALYSE-VALUNISIG-7577#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001156#REF# 4.4.1.5.2.1
For trains where the first four braked wheelsets are not fitted with a WSP system (without which the reference wheel/rail adhesion condition
cannot be validated) the field tests specified in EN15595 cannot be used and the rules of §4.4.1.5.1 shall not be applied.
#ANALYSE-VALUNISIG-7578#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001157#REF# 4.4.1.5.2.2
Note: For such trains, any value lower than or equal to 1 for the rolling stock correction factor Kwet_rst may be used.
#ANALYSE-VALUNISIG-7579#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

#REQ-UNISIG-SUB040-001159#REF# to.4.4.2

#ANALYSE-VALUNISIG-7580#REF# FCT The configuration rule has to be outlined in ESBO_FzgKonfDat.

Chapter 4.5

#REQ-UNISIG-SUB040-001161#REF# 4.5.1.1
STM related dimensioning rules


--- FINALISED ---
New Subset 35 for baseline 3 is not realized (see #REQ-FCT-UNISIG-0035:03#REF#). /FFFIS_DMI/ defines own limitations for STM input and display,
which are greater than the defined in chapter 15 in the new Subset 35 for baseline 3.
#ANALYSE-VALUNISIG-7581#REF# FCT No additional functional requirement refer column FINALISED.

#REQ-UNISIG-SUB040-001162#REF# 4.5.1.2
Storage of Virtual Balise Covers set by driver

realised by: #REQ-UNISIG-SUB040-001183#REF#
realised by: #REQ-UNISIG-SUB040-001048#REF#

#REQ-UNISIG-SUB040-001183#REF# to.4.5.1.2 #REQ-UNISIG-SUB040-001162#REF#
The obu shall memorize maximum 20 Virtual Balise Cover information from the driver.
VBC function should not have to  realize

#REQ-UNISIG-SUB040-001048#REF# to.4.5.1.2 #REQ-UNISIG-SUB040-001162#REF#
The obu shall restrict the driver input of maximum 20 Virtual Balise Cover information.
VBC function should not have to  realize